docs: Added the new issues to troubleshooting guide #615
+398
−15
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
Prekshith-Microsoft
requested review from
Avijit-Microsoft,
Fr4nc3,
Prajwal-Microsoft,
Roopan-Microsoft,
Vinay-Microsoft,
aniaroramsft and
marktayl1
as code owners
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.
The troubleshooting guide has been extensively updated with new issues, detailed investigation notes, and structured troubleshooting steps to improve clarity and efficiency in diagnosing Azure deployment-related errors.
This update includes newly identified and validated issues. Each issue entry now follows a standardized documentation format that highlights the cause, reproduction steps, and recommended resolution. This structure ensures uniformity and makes it easier for teams to quickly identify the root cause and apply the correct fix during deployment troubleshooting.
The new additions cover a diverse range of scenarios including invalid template configurations, SKU limitations, diagnostic setting conflicts, and provisioning timeouts. For each case, practical steps and corresponding CLI commands have been added to help engineers validate configurations and implement corrective actions efficiently.