Skip to content

Commit 7a70ebd

Browse files
NirajC-MicrosoftNirajC-Microsoft
committed
Update Troubleshoot doc - 1
1 parent 17fc1a5 commit 7a70ebd

1 file changed

Lines changed: 9 additions & 61 deletions

File tree

‎docs/TroubleShootingSteps.md‎

Lines changed: 9 additions & 61 deletions
Original file line numberDiff line numberDiff line change
@@ -45,71 +45,19 @@ Use these as quick reference guides to unblock your deployments.
4545

4646
--------------------------------
4747

48-
### Regional & Location Issues
48+
### Regional & Location Issues
4949

50-
<details>
51-
<summary><b>LocationNotAvailableForResourceType</b></summary>
52-
53-
- You may encounter a LocationNotAvailableForResourceType error if you set the secondary location to 'Australia Central' in the main.bicep file.
54-
- This happens because 'Australia Central' is not a supported region for that resource type.
55-
- Always refer to the README file or Azure documentation to check the list of supported regions.
56-
- Update the deployment with a valid supported region to resolve the issue.
57-
58-
</details>
59-
60-
<details>
61-
<summary><b>InvalidResourceLocation</b></summary>
62-
63-
- You may encounter an InvalidResourceLocation error if you change the region for Cosmos DB or the Storage Account (secondary location) multiple times in the main.bicep file and redeploy.
64-
- Azure resources like Cosmos DB and Storage Accounts do not support changing regions after deployment.
65-
- If you need to change the region again, first delete the existing deployment.
66-
- Then redeploy the resources with the updated region configuration.
67-
68-
</details>
69-
70-
<details>
71-
<summary><b>ServiceUnavailable/ResourceNotFound</b></summary>
72-
73-
- 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/en-us/azure/reliability/regions-list) and [Azure Database for MySQL Flexible Server - Azure Regions](https://learn.microsoft.com/azure/mysql/flexible-server/overview#azure-regions).
74-
75-
- You can request more quota, refer [Quota Request](https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/create-support-request-quota-increase) Documentation
76-
77-
78-
</details>
79-
80-
<details>
81-
<summary><b>ResourceOperationFailure/ProvisioningDisabled</b></summary>
82-
83-
- This error occurs when provisioning of a resource is restricted in the selected region.
84-
It usually happens because the service is not available in that region or provisioning has been temporarily disabled.
85-
86-
- 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/en-us/azure/reliability/regions-list) and [Azure Database for MySQL Flexible Server - Azure Regions](https://learn.microsoft.com/azure/mysql/flexible-server/overview#azure-regions).
87-
88-
- If you need to use the same region, you can request a quota or provisioning exception.
89-
Refer [Quota Request](https://docs.microsoft.com/en-us/azure/sql-database/quota-increase-request) for more details.
90-
91-
</details>
92-
93-
<details>
94-
<summary><b>RedundancyConfigurationNotAvailableInRegion</b></summary>
95-
96-
- This issue happens when you try to create a **Storage Account** with a redundancy configuration (e.g., `Standard_GRS`) that is **not supported in the selected Azure region**.
97-
- Example: Creating a storage account with **GRS** in **italynorth** will fail with this error.
98-
```bash
99-
az storage account create -n mystorageacct123 -g myResourceGroup -l italynorth --sku Standard_GRS --kind StorageV2
100-
```
101-
- To check supported SKUs for your region:
102-
```bash
103-
az storage account list-skus -l italynorth -o table
104-
```
105-
Use a supported redundancy option (e.g., Standard_LRS) in the same region
106-
Or deploy the Storage Account in a region that supports your chosen redundancy.
107-
For more details, refer to [Azure Storage redundancy documentation](https://learn.microsoft.com/en-us/azure/storage/common/storage-redundancy?utm_source=chatgpt.com).
108-
</details>
50+
| Issue/Error Code | Description | Steps to Resolve |
51+
|-----------------|-------------|------------------|
52+
| **LocationNotAvailableForResourceType** | | - You may encounter a LocationNotAvailableForResourceType error if you set the secondary location to 'Australia Central' in the main.bicep file<br>- This happens because 'Australia Central' is not a supported region for that resource type<br>- Always refer to the README file or Azure documentation to check the list of supported regions<br>- Update the deployment with a valid supported region to resolve the issue |
53+
| **InvalidResourceLocation** | | - You may encounter an InvalidResourceLocation error if you change the region for Cosmos DB or the Storage Account (secondary location) multiple times in the main.bicep file and redeploy<br>- Azure resources like Cosmos DB and Storage Accounts do not support changing regions after deployment<br>- If you need to change the region again, first delete the existing deployment<br>- Then redeploy the resources with the updated region configuration |
54+
| **ServiceUnavailable/ResourceNotFound** | | - 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/en-us/azure/reliability/regions-list) and [Azure Database for MySQL Flexible Server - Azure Regions](https://learn.microsoft.com/azure/mysql/flexible-server/overview#azure-regions)<br>- You can request more quota, refer [Quota Request](https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/create-support-request-quota-increase) Documentation |
55+
| **ResourceOperationFailure/ProvisioningDisabled** | | - This error occurs when provisioning of a resource is restricted in the selected region. It usually happens because the service is not available in that region or provisioning has been temporarily disabled<br>- 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/en-us/azure/reliability/regions-list) and [Azure Database for MySQL Flexible Server - Azure Regions](https://learn.microsoft.com/azure/mysql/flexible-server/overview#azure-regions)<br>- If you need to use the same region, you can request a quota or provisioning exception. Refer [Quota Request](https://docs.microsoft.com/en-us/azure/sql-database/quota-increase-request) for more details |
56+
| **RedundancyConfigurationNotAvailableInRegion** | | - This issue happens when you try to create a **Storage Account** with a redundancy configuration (e.g., `Standard_GRS`) that is **not supported in the selected Azure region**<br>- Example: Creating a storage account with **GRS** in **italynorth** will fail with this error<br>- To check supported SKUs for your region:<br>`az storage account list-skus -l italynorth -o table`<br>- Use a supported redundancy option (e.g., Standard_LRS) in the same region or deploy the Storage Account in a region that supports your chosen redundancy<br>- For more details, refer to [Azure Storage redundancy documentation](https://learn.microsoft.com/en-us/azure/storage/common/storage-redundancy?utm_source=chatgpt.com) |
10957

11058
--------------------------------
11159

112-
Resource Naming & Validation
60+
### Resource Naming & Validation
11361

11462
<details>
11563
<summary><b>ResourceNameInvalid</b></summary>

0 commit comments

Comments
 (0)