-
Notifications
You must be signed in to change notification settings - Fork 371
docs: Additional troubleshooting steps #460
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
Removed duplicate lines explaining the DeploymentNotFound issue and its avoidance.
Suicynic
reviewed
Sep 9, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
multi-agent
Co-authored-by: Copilot <[email protected]>
Added guidance for resolving BadRequest errors related to failed provisioning of Azure Cosmos DB accounts.
Updated the summary of troubleshooting steps to include 'SpecialFeatureOrQuotaIdRequired'.
Roopan-Microsoft
approved these changes
Sep 19, 2025
🎉 This PR is included in version 2.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
This pull request significantly expands and improves the troubleshooting documentation for Azure deployment errors in
docs/TroubleShootingSteps.md
. It adds detailed guidance for many new error scenarios, clarifies existing sections, and provides links to relevant Microsoft documentation for easier self-service resolution.Expanded error coverage and improved guidance:
Added troubleshooting steps for several new errors, including
Unauthorized - Operation cannot be completed without additional quota
,ParentResourceNotfound
,ResourceProviderError
,Conflict - Cannot use the SKU Basic with File Change Audit
,AccountPropertyCannotBeUpdated
,InvalidRequestContent
,ReadOnlyDisabledSubscription
,SkuNotAvailable
,CrossTenantDeploymentNotPermitted
,RequestDisallowedByPolicy
,FlagMustBeSetForRestore/NameUnavailable/CustomDomainInUse
,PrincipalNotFound
,RedundancyConfigurationNotAvailableInRegion
, andDeploymentNotFound
. Each new section includes practical steps and links to official documentation.Expanded existing error summary groups to cover additional related error codes, such as combining
DeploymentModelNotSupported
,ServiceModelDeprecated
, andInvalidResourceProperties
, and addingThe language expression property array index is out of bounds
to the group with resource ID errors.Clarifications for resource ID errors:
The language expression property array index '8' is out of bounds
, clarifying that it is caused by incomplete resource IDs and providing guidance on correct formatting.Links and references for further troubleshooting:
These changes make the troubleshooting guide much more comprehensive and user-friendly, helping users resolve a broader range of deployment issues more efficiently.
Does this introduce a breaking change?
How to Test
What to Check
Verify that the following are valid
Other Information