docs: Add documentation for deploying with limited Azure OpenAI quota #687
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 introduces several improvements and additions to deployment documentation, error troubleshooting, and Azure resource tagging. The most significant changes include expanded troubleshooting steps for Azure deployments, new guides for building and pushing container images, and enhancements to resource tagging and deployment metadata for improved traceability and compliance.
Documentation Improvements
docs/ACRBuildAndPushGuide.mdfor building and pushing Docker images to Azure Container Registry, including step-by-step instructions for both WebApp and Backend services.docs/DeployWithLimitedQuota.mdto help users deploy with limited Azure OpenAI quota, including instructions for bypassing or lowering quota validation in the Bicep template.Troubleshooting Enhancements
docs/TroubleShootingSteps.mdwith many new error scenarios, resolutions, and links to official Microsoft documentation, including errors likeInvalidRequestContent,ReadOnlyDisabledSubscription,SkuNotAvailable,CrossTenantDeploymentNotPermitted,SpecialFeatureOrQuotaIdRequired, and more.Deployment & Tagging Improvements
infra/main.bicepby adding aTypetag to distinguish between WAF and Non-WAF deployments, and improved logic for theCreatedBytag to use either the username or object ID..github/workflows/CAdeploy.yml, added automatic timestamp tagging for deployments, improving auditability and resource lifecycle management.Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information