docs: update README and QuotaCheck documentation with supported Azure regions and deployment details; refine region descriptions in main.bicep and main.json; adjust default regions in quota_check_params.sh

Author: Pavan-Microsoft

README.md

@@ -205,6 +205,23 @@ locations support this version. If you're deploying to a location that doesn't s
 switch to a lower version. To find out which versions are supported in different regions, visit the
 [GPT-4.1 Model Availability](https://learn.microsoft.com/en-us/azure/ai-services/openai/concepts/models?tabs=global-standard%2Cstandard-chat-completions#global-standard-model-availability) page.
 
+
+### Supported Azure Regions
+
+The solution has been tested and is compatible with the following Azure regions:
+- **Australia East**
+- **East US 2**
+- **Japan East**
+- **UK South**
+
+These regions are specifically configured in the deployment template to guarantee compatibility with paired regions and data redundancy. This restriction ensures reliable failover scenarios based on Azure's region availability and the requirements of services like Azure Database for PostgreSQL Flexible Server.
+
+When deploying the solution using the "Deploy to Azure" button, you'll see two fields in the Azure portal:
+- **Region**: This refers to the Azure region where the deployment metadata is stored
+- **Location**: This corresponds to the "location" parameter in the bicep template and determines where all your solution resources will be deployed
+
+**Important**: For this solution, you must select one of the supported regions listed above in the "Location" field. The "Region" field can be set to any available region since it only affects deployment metadata storage.
+
 ### Testing the deployment
 1. Navigate to the admin site, where you can upload documents. It will be located at:
 

docs/QuotaCheck.md

@@ -16,7 +16,7 @@ gpt4.1:30, text-embedding-ada-002:30
 ```
 ### 📌 Default Regions:
 ```
-francecentral, australiaeast, uksouth, eastus2, northcentralus, swedencentral, westus, westus2, southcentralus
+australiaeast, eastus2, japaneast, uksouth
 ```
 ### Usage Scenarios:
 - No parameters passed → Default models and capacities will be checked in default regions.
@@ -41,17 +41,17 @@ francecentral, australiaeast, uksouth, eastus2, northcentralus, swedencentral, w
   ./quota_check_params.sh --models gpt4.1:30,text-embedding-ada-002:30
   ```
 ✔️ Check default models in specific region(s):
-  ```
-./quota_check_params.sh --regions eastus2,westus
-  ```
-✔️ Passing Both models and regions:
-  ```
-  ./quota_check_params.sh --models gpt4.1:30 --regions eastus2,westus
-  ```
+```
+./quota_check_params.sh --regions eastus2,japaneast
+```
+✔️ Passing both models and regions:
+```
+./quota_check_params.sh --models gpt4.1:30 --regions eastus2,japaneast
+```
 ✔️ All parameters combined:
-  ```
- ./quota_check_params.sh --models gpt4.1:30,text-embedding-ada-002:30 --regions eastus2,westus --verbose
-  ```
+```
+./quota_check_params.sh --models gpt4.1:30,text-embedding-ada-002:30 --regions eastus2,japaneast --verbose
+```
 
 ### **Sample Output**
 The final table lists regions with available quota. You can select any of these regions for deployment.
@@ -99,3 +99,5 @@ The final table lists regions with available quota. You can select any of these
     az login
     ```
 6. Rerun the script after installing Azure CLI.
+
+> **Note:** The solution is restricted to these specific regions to ensure compatibility with paired regions and data redundancy requirements: australiaeast, eastus2, japaneast, uksouth.

infra/main.bicep

@@ -16,7 +16,7 @@ param solutionUniqueText string = take(uniqueString(subscription().id, resourceG
   'uksouth'
 ])
 @metadata({ azd: { type: 'location' } })
-@description('Required. Azure region for all services. Regions are restricted to guarantee compatibility with paired regions and replica locations for data redundancy and failover scenarios based on articles [Azure regions list](https://learn.microsoft.com/azure/reliability/regions-list) and [Azure Database for MySQL Flexible Server - Azure Regions](https://learn.microsoft.com/azure/mysql/flexible-server/overview#azure-regions).')
+@description('Required. Azure region for all services. Regions are restricted to guarantee compatibility with paired regions and replica locations for data redundancy and failover scenarios based on articles [Azure regions list](https://learn.microsoft.com/azure/reliability/regions-list) and [Azure Database for PostgreSQL Flexible Server - Azure Regions](https://learn.microsoft.com/azure/postgresql/flexible-server/overview#azure-regions). Note: In the "Deploy to Azure" interface, you will see both "Region" and "Location" fields - "Region" is only for deployment metadata while "Location" (this parameter) determines where your actual resources are deployed.')
 param location string
 
 @description('Optional. Existing Log Analytics Workspace Resource ID.')

infra/main.json

@@ -6,7 +6,7 @@
     "_generator": {
       "name": "bicep",
       "version": "0.37.4.10188",
-      "templateHash": "5895320887545019006"
+      "templateHash": "8315389814354571577"
     }
   },
   "parameters": {
@@ -39,7 +39,7 @@
         "azd": {
           "type": "location"
         },
-        "description": "Required. Azure region for all services. Regions are restricted to guarantee compatibility with paired regions and replica locations for data redundancy and failover scenarios based on articles [Azure regions list](https://learn.microsoft.com/azure/reliability/regions-list) and [Azure Database for MySQL Flexible Server - Azure Regions](https://learn.microsoft.com/azure/mysql/flexible-server/overview#azure-regions)."
+        "description": "Required. Azure region for all services. Regions are restricted to guarantee compatibility with paired regions and replica locations for data redundancy and failover scenarios based on articles [Azure regions list](https://learn.microsoft.com/azure/reliability/regions-list) and [Azure Database for PostgreSQL Flexible Server - Azure Regions](https://learn.microsoft.com/azure/postgresql/flexible-server/overview#azure-regions). Note: In the \"Deploy to Azure\" interface, you will see both \"Region\" and \"Location\" fields - \"Region\" is only for deployment metadata while \"Location\" (this parameter) determines where your actual resources are deployed."
       }
     },
     "existingLogAnalyticsWorkspaceId": {

scripts/quota_check_params.sh

@@ -93,7 +93,7 @@ az account set --subscription "$AZURE_SUBSCRIPTION_ID"
 echo "🎯 Active Subscription: $(az account show --query '[name, id]' --output tsv)"
 
 # Default Regions to check (Comma-separated, now configurable)
-DEFAULT_REGIONS="francecentral,australiaeast,uksouth,eastus2,northcentralus,swedencentral,westus,westus2,southcentralus"
+DEFAULT_REGIONS="australiaeast,eastus2,japaneast,uksouth"
 IFS=',' read -r -a DEFAULT_REGION_ARRAY <<< "$DEFAULT_REGIONS"
 
 # Read parameters (if any)
@@ -166,7 +166,7 @@ for REGION in "${REGIONS[@]}"; do
         INSUFFICIENT_QUOTA=false
 
         MODEL_TYPES=("openai.standard.$MODEL_NAME" "openai.globalstandard.$MODEL_NAME")
-      
+
         for MODEL_TYPE in "${MODEL_TYPES[@]}"; do
             FOUND=false
             INSUFFICIENT_QUOTA=false