Skip to content

Conversation

@NirajC-Microsoft
Copy link
Contributor

Purpose

This pull request updates the troubleshooting documentation to cover additional Azure deployment errors, providing more detailed guidance and resolution steps for common issues. The changes expand coverage for quotas, networking, authentication, and resource provisioning failures, making it easier to diagnose and resolve deployment blockers.

New and Expanded Error Troubleshooting Coverage:

Quota and API Version Errors:

  • Added guidance for resolving the ServiceQuotaExceeded error when exceeding the free tier quota for Azure AI Search, including steps to identify, delete, or upgrade services, and links to official documentation.
  • Documented the NoRegisteredProviderFound error for unsupported API versions, with instructions on updating API versions in templates and checking supported versions.

Networking and Subnet Configuration:

  • Added troubleshooting for VMSizeIsNotPermittedToEnableAcceleratedNetworking, including how to check supported VM sizes and alternatives.
  • Documented errors related to Azure Bastion subnet configuration:
    • NetworkSecurityGroupNotCompliantForAzureBastionSubnet and SecurityRuleParameterContainsUnsupportedValue for NSG rules blocking required ports.
    • RouteTableCannotBeAttachedForAzureBastionSubnet for attempts to attach route tables to Bastion subnets, with clear remediation steps.

Authentication and Immutable Properties:

  • Added troubleshooting for the Conflict - Local authentication is disabled error in Azure App Configuration, including how to use Managed Identity and re-enable local auth if necessary.
  • Documented the PropertyChangeNotAllowed error for immutable VM properties, explaining the cause and necessary redeployment steps.

Resource Provisioning and Parent/Child Dependencies:

  • Added guidance for FailedIdentityOperation / ManagedEnvironmentScheduledForDelete errors in Azure Container Apps, including how to handle pending deletes and resource conflicts.
  • Documented the BadRequest - Parent account does not provision correctly error for Cognitive Services, with steps to check, delete, or restore parent accounts and resolve soft-delete issues.

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