docs: Azure Region Restrictions, Model Capacity Enhancements, and Documentation Alignment

[Pavan-Microsoft]

Purpose

This pull request updates the supported Azure regions and increases the default model capacities for the solution. The changes ensure that deployments are restricted to specific regions for compatibility and data redundancy, and that resource quotas are set higher for both GPT-4.1 and embedding models. Documentation, deployment templates, and scripts have all been updated for consistency.

Azure Region Restrictions and Documentation Updates:

• The solution now only supports deployment in four Azure regions: Australia East, East US 2, Japan East, and UK South. Documentation in README.md and docs/QuotaCheck.md has been updated to reflect this restriction and clarify the difference between "Region" (deployment metadata) and "Location" (resource deployment). [1] [2] [3]

Model Capacity Increases:

• Default model capacities have been increased to gpt4.1:150 and text-embedding-ada-002:100 in documentation, deployment parameter files (main.parameters.json, main.waf.parameters.json), and scripts. [1] [2] [3] [4] [5] [6] [7]

Deployment Template Updates:

• The Bicep and generated JSON templates (main.bicep, main.json) now restrict the location parameter to the supported regions and update descriptions to clarify the distinction between "Region" and "Location" fields in the Azure portal. References to Azure Database for MySQL have been corrected to PostgreSQL. [1] [2]

Script and Sample Updates:

• The quota_check_params.sh script and sample usage in documentation now use the updated regions and model capacities, ensuring users interact with the correct configuration. [1] [2] [3]

Consistency and Clarification:

• All related documentation, parameters, and scripts are now consistent in their references to supported regions and model capacities, reducing confusion for users and aligning with best practices for Azure failover and redundancy. [1] [2] [3]

Let me know if you want to dive deeper into any specific change or need help understanding how these updates affect deployment or usage!

Does this introduce a breaking change?

• Yes
• No

What to Check

Verify the documentation