Merge pull request #228032 from davidsmatlak/ds-ghi-105248

Adds error code to ARM deployments troubleshooting doc

Author: prmerger-automator[bot]

articles/azure-resource-manager/troubleshooting/common-deployment-errors.md

@@ -3,7 +3,7 @@ title: Troubleshoot common Azure deployment errors
 description: Troubleshoot common Azure deployment errors for resources that are deployed with Bicep files or Azure Resource Manager templates (ARM templates).
 tags: top-support-issue
 ms.topic: troubleshooting
-ms.date: 01/03/2023
+ms.date: 02/21/2023
 ms.custom: devx-track-azurepowershell
 ---
 
@@ -80,6 +80,7 @@ If your error code isn't listed, submit a GitHub issue. On the right side of the
 | SubnetIsFull | There aren't enough available addresses in the subnet to deploy resources. You can release addresses from the subnet, use a different subnet, or create a new subnet. | [Manage subnets](../../virtual-network/virtual-network-manage-subnet.md) and [Virtual network FAQ](../../virtual-network/virtual-networks-faq.md#are-there-any-restrictions-on-using-ip-addresses-within-these-subnets) <br><br> [Private IP addresses](../../virtual-network/ip-services/private-ip-addresses.md) |
 | SubscriptionNotFound | A specified subscription for deployment can't be accessed. It could be the subscription ID is wrong, the user deploying the template doesn't have adequate permissions to deploy to the subscription, or the subscription ID is in the wrong format. When using ARM template nested deployments to deploy across scopes, provide the subscription's GUID. | [ARM template deploy across scopes](../templates/deploy-to-resource-group.md) <br><br> [Bicep file deploy across scopes](../bicep/deploy-to-resource-group.md) |
 | SubscriptionNotRegistered | When a resource is deployed, the resource provider must be registered for your subscription. When you use an Azure Resource Manager template for deployment, the resource provider is automatically registered in the subscription. Sometimes, the automatic registration doesn't complete in time. To avoid this intermittent error, register the resource provider before deployment. | [Resolve registration](error-register-resource-provider.md) |
+| SubscriptionRequestsThrottled | Azure Resource Manager throttles requests at the subscription level or tenant level. Resource providers like `Microsoft.Compute` also throttle requests specific to its operations. <br><br> When a limit is reached, you get a message and a value with the amount of time you should wait before sending a new request. For example: `Number of requests for subscription '<subscription-id-guid>' and operation '<resource provider>' exceeded the backend storage limit. Please try again after '6' seconds.` <br><br> An HTTP response returns a message like `HTTP status code 429 Too Many Requests` with a `Retry-After` value that specifies the number of seconds to wait before you send another request. | [Throttling Resource Manager requests](../management/request-limits-and-throttling.md) <br><br> [Troubleshooting API throttling errors - virtual machines](/troubleshoot/azure/virtual-machines/troubleshooting-throttling-errors) <br><br> [Azure Kubernetes Service throttling](/troubleshoot/azure/azure-kubernetes/error-code-subscriptionrequeststhrottled) |
 | TemplateResourceCircularDependency | Remove unnecessary dependencies. | [Resolve circular dependencies](error-invalid-template.md#circular-dependency) |
 | TooManyTargetResourceGroups | Reduce number of resource groups for a single deployment. | [ARM template deploy across scopes](../templates/deploy-to-resource-group.md) <br><br> [Bicep file deploy across scopes](../bicep/deploy-to-resource-group.md) |