Skip to content

Conversation

@NirajC-Microsoft
Copy link
Contributor

Purpose

This pull request expands the Azure deployment troubleshooting documentation by adding several new error scenarios and their resolutions. The additions cover quota errors, API version mismatches, VM and networking restrictions, authentication conflicts, and resource provisioning issues. These updates provide more comprehensive guidance for resolving common deployment blockers.

Quota and API Version Errors

  • Added troubleshooting steps for the ServiceQuotaExceeded error, detailing causes and resolutions when the free tier quota for Azure AI Search is exceeded, including how to delete existing services, upgrade SKUs, or request quota increases.
  • Documented the NoRegisteredProviderFound error, explaining how to resolve unsupported API version issues for Azure resources by updating templates and checking supported versions.

Networking and VM Restrictions

  • Added guidance for the VMSizeIsNotPermittedToEnableAcceleratedNetworking error, clarifying which VM sizes support accelerated networking and how to resolve configuration issues.
  • Provided troubleshooting for NetworkSecurityGroupNotCompliantForAzureBastionSubnet and SecurityRuleParameterContainsUnsupportedValue, explaining NSG rule requirements for Azure Bastion and how to resolve port blocking issues.
  • Explained the RouteTableCannotBeAttachedForAzureBastionSubnet error, describing Azure Bastion subnet restrictions and how to avoid attaching route tables.

Authentication and Immutable Properties

  • Added resolution steps for the Conflict - Local authentication is disabled error in Azure App Configuration, including how to switch to Managed Identity authentication or re-enable local auth.
  • Documented the PropertyChangeNotAllowed error for immutable VM properties, detailing how to handle changes to properties like osProfile.adminUsername.

Resource Provisioning and Parent Account Issues

  • Provided guidance for FailedIdentityOperation and ManagedEnvironmentScheduledForDelete errors, explaining how to handle pending delete operations and resource conflicts in Azure Container Apps environments.
  • Added troubleshooting steps for BadRequest - Parent account does not provision correctly, clarifying how to address parent AI/Cognitive Services account provisioning failures and soft-delete scenarios.

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