Update request-limits-and-throttling.md

Put updated throttling limits at the top, update FAQ

Author: juliamwang6

articles/azure-resource-manager/management/request-limits-and-throttling.md

@@ -10,46 +10,15 @@ ms.custom: devx-track-arm-template
 
 This article describes how Azure Resource Manager throttles requests. It shows you how to track the number of requests that remain before reaching the limit, and how to respond when you reach the limit.
 
-Throttling happens at two levels. Azure Resource Manager throttles requests for the subscription and tenant. If the request is under the throttling limits for the subscription and tenant, Resource Manager routes the request to the resource provider. The resource provider applies throttling limits that are tailored to its operations.
-
-Requests are initially throttled per principal ID and per Azure Resource Manager instance in the region of the user sending the request. Requests to the Azure Resource Manger instance in the region are also throttled per principal user ID and per hour. When the request is forwarded to the resource provider, requests are throttled per region of the resource rather than per Azure Resource Manager instance in region of the user. 
-
-> [!NOTE]
-> The limits of a resource provider can differ from the limits of the Azure Resource Manager instance in the region of the user.
-
-The following image shows how throttling is applied as a request goes from the user to Azure Resource Manager and the resource provider. 
-
-:::image type="content" source="./media/request-limits-and-throttling/request-throttling.svg" alt-text="Diagram that shows how throttling is applied as a request goes from the user to Azure Resource Manager and the resource provider.":::
-
-## Subscription and tenant limits
-
-Every subscription-level and tenant-level operation is subject to throttling limits. Subscription requests are ones that involve passing your subscription ID, such as retrieving the resource groups in your subscription. For example, sending a request to `https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups?api-version=2022-01-01` is a subscription-level operation. Tenant requests don't include your subscription ID, such as retrieving valid Azure locations. For example, sending a request to `https://management.azure.com/tenants?api-version=2022-01-01` is a tenant-level operation.
-
-The default throttling limits per hour are shown in the following table.
-
-| Scope | Operations | Limit |
-| ----- | ---------- | ------- |
-| Subscription | reads | 12,000 |
-| Subscription | deletes | 15,000 |
-| Subscription | writes | 1,200 |
-| Tenant | reads | 12,000 |
-| Tenant | writes | 1,200 |
-
-These limits are scoped to the security principal (user or application) making the requests and the subscription ID or tenant ID. If your requests come from more than one security principal, your limit across the subscription or tenant is greater than 12,000 and 1,200 per hour.
-
-These limits apply to each Azure Resource Manager instance. There are multiple instances in every Azure region, and Azure Resource Manager is deployed to all Azure regions. So, in practice, the limits are higher than these limits. Different instances of Azure Resource Manager usually handle the user's requests.
-
-The remaining requests are returned in the [response header values](#remaining-requests).
-
-## Migrating to regional throttling and token bucket algorithm
+## Regional throttling and token bucket algorithm
 
-Starting in 2024, Microsoft is migrating Azure subscriptions to a new throttling architecture. With this change, you experience new throttling limits. The new throttling limits are applied per region rather than per instance of Azure Resource Manager. The new architecture uses a [token bucket algorithm](https://en.wikipedia.org/wiki/Token_bucket) to manage API throttling.
+Microsoft has migrated Azure subscriptions to an updated throttling architecture as of 2024. Throttling limits are now applied per region rather than per instance of Azure Resource Manager. This new architecture uses a [token bucket algorithm](https://en.wikipedia.org/wiki/Token_bucket) to manage API throttling.
 
 The token bucket represents the maximum number of requests that you can send for each second. When you reach the maximum number of requests, the refill rate determines how quickly tokens become available in the bucket.
 
 These updated limits make it easier for you to refresh and manage your quota.
 
-The new limits are:
+The updated limits are:
 
 | Scope | Operations | Bucket size | Refill rate per sec |
 | ----- | ---------- | ----------- | ------------------- |
@@ -68,21 +37,50 @@ For example, suppose you have a bucket size of 250 tokens for read requests and
 
 Reading metrics using the `*/providers/microsoft.insights/metrics` API contributes significantly to overall Azure Resource Manager traffic and is a common cause of subscription throttling events. If you use this API heavily, we recommend that you switch to the `getBatch` API. You can query multiple resources in a single REST request, which improves performance and reduces throttling. For more information about converting your operations, see [How to migrate from the metrics API to the getBatch API](/azure/azure-monitor/essentials/migrate-to-batch-api).
 
-### How do I know if my subscription uses the new throttling experience?
+### How can I view my throttled requests?
 
-After your subscription is migrated to the new throttling experience, the response header shows the remaining requests per minute instead of per hour. Also, your `Retry-After` value shows one minute or less, instead of five minutes. For more information, see [Error code](#error-code).
+To view your throttled requests and other Resource Manager metrics, see [Accessing Azure Resource Manager metrics](/azure/azure-resource-manager/management/monitor-resource-manager#accessing-azure-resource-manager-metrics).
 
-### Why is throttling changing to per region rather than per instance?
+### Why is throttling per region rather than per instance?
 
 Since different regions have a different number of Resource Manager instances, throttling per instance causes inconsistent throttling performance. Throttling per region makes throttling consistent and predictable.
 
-### How does the new throttling experience affect my limits?
+### How does the updated throttling experience affect my limits?
 
 You can send more requests. Write requests increase by 30 times. Delete requests increase by 2.4 times. Read requests increase by 7.5 times.
 
-### Can I prevent my subscription from migrating to the new throttling experience?
+# Throttling for non-public clouds
 
-No, all subscriptions will eventually be migrated.
+Throttling happens at two levels. Azure Resource Manager throttles requests for the subscription and tenant. If the request is under the throttling limits for the subscription and tenant, Resource Manager routes the request to the resource provider. The resource provider applies throttling limits that are tailored to its operations.
+
+Requests are initially throttled per principal ID and per Azure Resource Manager instance in the region of the user sending the request. Requests to the Azure Resource Manager instance in the region are also throttled per principal user ID and per hour. When the request is forwarded to the resource provider, requests are throttled per region of the resource rather than per Azure Resource Manager instance in region of the user. 
+
+> [!NOTE]
+> The limits of a resource provider can differ from the limits of the Azure Resource Manager instance in the region of the user.
+
+The following image shows how throttling is applied as a request goes from the user to Azure Resource Manager and the resource provider. 
+
+:::image type="content" source="./media/request-limits-and-throttling/request-throttling.svg" alt-text="Diagram that shows how throttling is applied as a request goes from the user to Azure Resource Manager and the resource provider.":::
+
+## Subscription and tenant limits
+
+Every subscription-level and tenant-level operation is subject to throttling limits. Subscription requests are ones that involve passing your subscription ID, such as retrieving the resource groups in your subscription. For example, sending a request to `https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups?api-version=2022-01-01` is a subscription-level operation. Tenant requests don't include your subscription ID, such as retrieving valid Azure locations. For example, sending a request to `https://management.azure.com/tenants?api-version=2022-01-01` is a tenant-level operation.
+
+The default throttling limits per hour are shown in the following table.
+
+| Scope | Operations | Limit |
+| ----- | ---------- | ------- |
+| Subscription | reads | 12,000 |
+| Subscription | deletes | 15,000 |
+| Subscription | writes | 1,200 |
+| Tenant | reads | 12,000 |
+| Tenant | writes | 1,200 |
+
+These limits are scoped to the security principal (user or application) making the requests and the subscription ID or tenant ID. If your requests come from more than one security principal, your limit across the subscription or tenant is greater than 12,000 and 1,200 per hour.
+
+These limits apply to each Azure Resource Manager instance. There are multiple instances in every Azure region, and Azure Resource Manager is deployed to all Azure regions. So, in practice, the limits are higher than these limits. Different instances of Azure Resource Manager usually handle the user's requests.
+
+The remaining requests are returned in the [response header values](#remaining-requests).
 
 ## Resource provider limits
 
@@ -246,4 +244,4 @@ msrest.http_logger :     'x-ms-ratelimit-remaining-subscription-writes': '1199'
 ## Next steps
 
 * For more information about limits and quotas, see [Azure subscription and service limits, quotas, and constraints](../../azure-resource-manager/management/azure-subscription-service-limits.md).
-* To learn about handling asynchronous REST requests, see [Track asynchronous Azure operations](async-operations.md).
+* To learn about handling asynchronous REST requests, see [Track asynchronous Azure operations](async-operations.md).