Merge pull request #101276 from Karishma-Tiwari-MSFT/patch-137

(ForumsTeam) fixes MicrosoftDocs/azure-docs#46227

Author: PRMerger8

articles/virtual-machines/troubleshooting/troubleshooting-throttling-errors.md

@@ -23,7 +23,7 @@ Azure Compute requests may be throttled at a subscription and on a per-region ba
 
 ## Throttling by Azure Resource Manager vs Resource Providers  
 
-As the front door to Azure, Azure Resource Manager does the authentication and first-order validation and throttling of all incoming API requests. Azure Resource Manager call rate limits and related diagnostic response HTTP headers are described [here](https://docs.microsoft.com/azure/azure-resource-manager/resource-manager-request-limits).
+As the front door to Azure, Azure Resource Manager does the authentication and first-order validation and throttling of all incoming API requests. Azure Resource Manager call rate limits and related diagnostic response HTTP headers are described [here](https://docs.microsoft.com/azure/azure-resource-manager/management/request-limits-and-throttling).
 
 When an Azure API client gets a throttling error, the HTTP status is 429 Too Many Requests. To understand if the request throttling is done by Azure Resource Manager or an underlying resource provider like CRP, inspect the `x-ms-ratelimit-remaining-subscription-reads` for GET requests and `x-ms-ratelimit-remaining-subscription-writes` response headers for non-GET requests. If the remaining call count is approaching 0, the subscription’s general call limit defined by Azure Resource Manager has been reached. Activities by all subscription clients are counted together. Otherwise, the throttling is coming from the target resource provider (the one addressed by the `/providers/<RP>` segment of the request URL).