Update TroubleShootingSteps.md

Author: Roopan-Microsoft

docs/TroubleShootingSteps.md

@@ -9,7 +9,7 @@ Use these as quick reference guides to unblock your deployments.
 | Issue/Error Code | Description | Steps to Resolve |
 |-----------|-------------|------------------|
 | **ReadOnlyDisabledSubscription** | Subscription is disabled or in read-only state | - Check if you have an active subscription before starting the deployment<br>- Depending on the type of the Azure Subscription, the expiration date might have been reached<br>- You have to activate the Azure Subscription before creating any Azure resource<br>- Refer to [Reactivate a disabled Azure subscription](https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/subscription-disabled) documentation |
-| **MissingSubscriptionRegistration/AllowBringYourOwnPublicIpAddress** | Required feature not registered in subscription | **Enable `AllowBringYourOwnPublicIpAddress` Feature**<br><br>Before deploying the resources, you may need to enable the **Bring Your Own Public IP Address** feature in Azure. This is required only once per subscription.<br><br>**Steps:**<br>1. Run the following command to register the feature:<br>`az feature register --namespace Microsoft.Network --name AllowBringYourOwnPublicIpAddress`<br><br>2. Wait for the registration to complete. Check the status using:<br>`az feature show --namespace Microsoft.Network --name AllowBringYourOwnPublicIpAddress --query properties.state`<br><br>3. The output should show: "Registered"<br><br>4. Once the feature is registered, refresh the provider:<br>`az provider register --namespace Microsoft.Network`<br><br>💡 Note: Feature registration may take several minutes to complete. This needs to be done only once per Azure subscription. |
+| **MissingSubscriptionRegistration/<br>AllowBringYourOwnPublicIpAddress** | Required feature not registered in subscription | **Enable `AllowBringYourOwnPublicIpAddress` Feature**<br><br>Before deploying the resources, you may need to enable the **Bring Your Own Public IP Address** feature in Azure. This is required only once per subscription.<br><br>**Steps:**<br>1. Run the following command to register the feature:<br>`az feature register --namespace Microsoft.Network --name AllowBringYourOwnPublicIpAddress`<br><br>2. Wait for the registration to complete. Check the status using:<br>`az feature show --namespace Microsoft.Network --name AllowBringYourOwnPublicIpAddress --query properties.state`<br><br>3. The output should show: "Registered"<br><br>4. Once the feature is registered, refresh the provider:<br>`az provider register --namespace Microsoft.Network`<br><br>💡 Note: Feature registration may take several minutes to complete. This needs to be done only once per Azure subscription. |
 | **Unauthorized - Operation cannot be completed without additional quota** | Insufficient quota for requested operation | - Check your quota usage using:<br>`az vm list-usage --location "<Location>" -o table`<br>- To request more quota refer to [VM Quota Request](https://techcommunity.microsoft.com/blog/startupsatmicrosoftblog/how-to-increase-quota-for-specific-types-of-azure-virtual-machines/3792394) |
 | **CrossTenantDeploymentNotPermitted** | Deployment across different Azure AD tenants not allowed | - **Check tenant match:** Ensure your deployment identity (user/SP) and the target resource group are in the same tenant:<br>`az account show`<br>`az group show --name <RG_NAME>`<br>- **Verify pipeline/service principal:** If using CI/CD, confirm the service principal belongs to the same tenant and has permissions on the resource group<br>- **Avoid cross-tenant references:** Make sure your Bicep doesn't reference subscriptions, resource groups, or resources in another tenant<br>- **Test minimal deployment:** Deploy a simple resource to the same resource group to confirm identity and tenant are correct<br>- **Guest/external accounts:** Avoid using guest users from other tenants; use native accounts or SPs in the tenant |
 | **RequestDisallowedByPolicy** | Azure Policy blocking the requested operation | - This typically indicates that an Azure Policy is preventing the requested action due to policy restrictions in your subscription<br>- For more details and guidance on resolving this issue, refer to: [RequestDisallowedByPolicy](https://learn.microsoft.com/en-us/troubleshoot/azure/azure-kubernetes/create-upgrade-delete/error-code-requestdisallowedbypolicy) |
@@ -22,7 +22,7 @@ Use these as quick reference guides to unblock your deployments.
 
 | Issue/Error Code | Description | Steps to Resolve |
 |-----------------|-------------|------------------|
-| **InternalSubscriptionIsOverQuotaForSku/ManagedEnvironmentProvisioningError** | Subscription quota exceeded for the requested SKU | Quotas are applied per resource group, subscriptions, accounts, and other scopes. For example, your subscription might be configured to limit the number of vCPUs for a region. If you attempt to deploy a virtual machine with more vCPUs than the permitted amount, you receive an error that the quota was exceeded.<br><br>For PowerShell, use the `Get-AzVMUsage` cmdlet to find virtual machine quotas:<br>`Get-AzVMUsage -Location "West US"`<br><br>Based on available quota you can deploy application otherwise, you can request for more quota |
+| **InternalSubscriptionIsOverQuotaForSku/<br>ManagedEnvironmentProvisioningError** | Subscription quota exceeded for the requested SKU | Quotas are applied per resource group, subscriptions, accounts, and other scopes. For example, your subscription might be configured to limit the number of vCPUs for a region. If you attempt to deploy a virtual machine with more vCPUs than the permitted amount, you receive an error that the quota was exceeded.<br><br>For PowerShell, use the `Get-AzVMUsage` cmdlet to find virtual machine quotas:<br>`Get-AzVMUsage -Location "West US"`<br><br>Based on available quota you can deploy application otherwise, you can request for more quota |
 | **InsufficientQuota** | Not enough quota available in subscription | - Check if you have sufficient quota available in your subscription before deployment<br>- To verify, refer to the [quota_check](../docs/quota_check.md) file for details |
 | **MaxNumberOfRegionalEnvironmentsInSubExceeded** | Maximum Container App Environments limit reached for region | - This error occurs when you try to create more than the allowed number of **Azure Container App Environments (ACA Environments)** in the same region for a subscription<br>- For example, in **Sweden Central**, only **1 Container App Environment** is allowed per subscription<br>- The subscription 'xxxx-xxxx' cannot have more than 1 Container App Environments in Sweden Central<br><br>**To fix this, you can:**<br>- Deploy the Container App Environment in a **different region**, OR<br>- Request a quota increase via Azure Support → [Quota Increase Request](https://go.microsoft.com/fwlink/?linkid=2208872) |
 | **SkuNotAvailable** | Requested SKU not available in selected location or zone | - You receive this error in the following scenarios:<br>  - When the resource SKU you've selected, such as VM size, isn't available for a location or zone<br>  - If you're deploying an Azure Spot VM or Spot scale set instance, and there isn't any capacity for Azure Spot in this location. For more information, see Spot error messages |
@@ -50,7 +50,7 @@ Use these as quick reference guides to unblock your deployments.
 | **LocationNotAvailableForResourceType** | Resource type not supported in selected region | - 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 |
 | **InvalidResourceLocation** | Cannot change region for already deployed resources | - 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 |
 | **ServiceUnavailable/ResourceNotFound** | Service unavailable or restricted in selected region | - 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 |
-| **ResourceOperationFailure/ProvisioningDisabled** | Resource provisioning restricted or disabled in region | - 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 |
+| **ResourceOperationFailure/<br>ProvisioningDisabled** | Resource provisioning restricted or disabled in region | - 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 |
 | **RedundancyConfigurationNotAvailableInRegion** | Redundancy configuration not supported in selected region | - 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 error `az storage account create -n mystorageacct123 -g myResourceGroup -l italynorth --sku Standard_GRS --kind StorageV2` <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) |
 
 --------------------------------