You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -205,6 +205,23 @@ locations support this version. If you're deploying to a location that doesn't s
205
205
switch to a lower version. To find out which versions are supported in different regions, visit the
206
206
[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.
207
207
208
+
209
+
### Supported Azure Regions
210
+
211
+
The solution has been tested and is compatible with the following Azure regions:
212
+
-**Australia East**
213
+
-**East US 2**
214
+
-**Japan East**
215
+
-**UK South**
216
+
217
+
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.
218
+
219
+
When deploying the solution using the "Deploy to Azure" button, you'll see two fields in the Azure portal:
220
+
-**Region**: This refers to the Azure region where the deployment metadata is stored
221
+
-**Location**: This corresponds to the "location" parameter in the bicep template and determines where all your solution resources will be deployed
222
+
223
+
**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.
224
+
208
225
### Testing the deployment
209
226
1. Navigate to the admin site, where you can upload documents. It will be located at:
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
99
99
az login
100
100
```
101
101
6. Rerun the script after installing Azure CLI.
102
+
103
+
> **Note:** The solution is restricted to these specific regions to ensure compatibility with paired regions and data redundancy requirements: australiaeast, eastus2, japaneast, uksouth.
@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).')
19
+
@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.')
Copy file name to clipboardExpand all lines: infra/main.json
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@
6
6
"_generator": {
7
7
"name": "bicep",
8
8
"version": "0.37.4.10188",
9
-
"templateHash": "9518149285531278918"
9
+
"templateHash": "5346639491059147931"
10
10
}
11
11
},
12
12
"parameters": {
@@ -39,7 +39,7 @@
39
39
"azd": {
40
40
"type": "location"
41
41
},
42
-
"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)."
42
+
"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."
0 commit comments