Skip to content

Conversation

@NirajC-Microsoft
Copy link
Contributor

Purpose

This pull request expands and updates the troubleshooting documentation in docs/TroubleShootingSteps.md by adding several new Azure deployment error scenarios, their causes, and detailed resolution steps. The new entries cover quota limits, unsupported configurations, API version issues, authentication problems, and deployment conflicts, providing actionable guidance and references for each case.

Major additions and updates:

Quota and API Version Errors:

  • Added guidance for resolving ServiceQuotaExceeded when hitting the free tier limit for Azure AI Search, including how to list, delete, or upgrade services, and how to request a quota increase.
  • Documented the NoRegisteredProviderFound error, explaining causes related to unsupported API versions and providing steps to update templates and check supported versions.

Networking and Bastion Subnet Issues:

  • Added troubleshooting for VMSizeIsNotPermittedToEnableAcceleratedNetworking, with instructions to select supported VM sizes or disable the feature.
  • Included new entries for NetworkSecurityGroupNotCompliantForAzureBastionSubnet and SecurityRuleParameterContainsUnsupportedValue, detailing required NSG rules for Azure Bastion.
  • Added resolution steps for RouteTableCannotBeAttachedForAzureBastionSubnet, clarifying that route tables cannot be associated with the Bastion subnet.

Authentication and Resource Immutability:

  • Added documentation for the error Conflict - Local authentication is disabled in Azure App Configuration, explaining how to switch to Managed Identity or re-enable local authentication.
  • Added PropertyChangeNotAllowed to explain immutable VM properties (like admin username) and how to redeploy with new credentials.

Deployment and Provisioning Conflicts:

  • Added troubleshooting for FailedIdentityOperation / ManagedEnvironmentScheduledForDelete in Azure Container Apps, with steps to handle pending deletes and naming conflicts.
  • Added a new section for BadRequest - Parent account does not provision correctly, covering issues with Cognitive Services parent/child resource provisioning and soft-delete restores.

Does this introduce a breaking change?

  • Yes
  • No

Golden Path Validation

  • I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

  • I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

  • ...

Other Information

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant