Skip to content

Commit 67c03a2

Browse files
committed
implementing feedback 5-23
1 parent c5227e7 commit 67c03a2

File tree

2 files changed

+7
-4
lines changed

2 files changed

+7
-4
lines changed

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -113,6 +113,9 @@ Microsoft Compute implements throttling to provide an optimal experience for Vir
113113

114114
[Azure Resource Graph](../../governance/resource-graph/overview.md) limits the number of requests to its operations. The steps in this article to determine the remaining requests and how to respond when the limit is reached also apply to Resource Graph. However, Resource Graph sets its own limit and reset rate. For more information, see [Resource Graph throttling headers](../../governance/resource-graph/concepts/guidance-for-throttled-requests.md#understand-throttling-headers).
115115

116+
Azure Resource Graph also has a solution that enables an additional mechanism for getting resource data when you have reached resource provider throttling limits by seamlessly integrating with existing Azure Resource Manager control plane GET and LIST APIs—offering a powerful, scalable solution for resource data access. For more information, see [ARG GET/LIST API](./arg-get-list-api.md).
117+
118+
116119
### Other resource providers
117120

118121
For information about throttling in other resource providers, see:

articles/governance/resource-graph/concepts/arg-get-list-api.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,16 +10,16 @@ ms.custom: devx-track-csharp
1010

1111
ARG GET/LIST API significantly reduces READ throttling by serving all incoming GET and LIST calls against ARG platform with smart routing controls in control plane. The API aligns with the existing request and response contracts of Azure control plane APIs while addressing throttling issues for customers.
1212

13-
ARG GET/LIST provides a default quota of 4k /min /user / subscription on a moving window. This is not a hard limit; we can support more than this based on scenario requirement. The API provides a response header “x-ms-user-quota-remaining" indicating remaining quota and "x-ms-user-quota-resets-after" indicating the time for a full quota reset based on which you can understand your quota consumption.
13+
ARG GET/LIST provides a default quota of 4k /min /user /subscription on a moving window. This is not a hard limit; we can support more than this based on scenario requirement. The API provides a response header “x-ms-user-quota-remaining" indicating remaining quota and "x-ms-user-quota-resets-after" indicating the time for a full quota reset based on which you can understand your quota consumption.
1414

1515
> [!NOTE]
1616
> Please keep in mind that the Azure Resource Manager (ARM) quota applies to these calls. Read about the ARM limits here : Understand how Azure Resource Manager throttles requests - Azure Resource Manager | Microsoft Learn. Refer to section "Migrating to regional throttling and token bucket algorithm" , these are the new limits which ARM follows for Azure Public cloud. 
1717
1818
## Using the ARG GET/LIST API
1919

20-
Using ARG GET/LIST API is very straightforward. If you feel your scenario matches the conditions mentioned [here](./guidance-for-throttled-requests.md#arg-getlist-api), you can simply append the flag &useResourceGraph=true to your control plane API calls, and the request will be routed to the ARG GET/LIST API backend.
20+
Using the ARG GET/LIST API is very straightforward. If you feel your scenario matches the conditions mentioned [here](./guidance-for-throttled-requests.md#arg-getlist-api), you can simply append the flag `&useResourceGraph=true` to your control plane API calls, and the request will be routed to the ARG GET/LIST API backend.
2121

22-
Contact the ARG Product group by sending an email to Azure Resource Graph team sharing a brief overview of your scenario and the ARG team will reach out to you with next steps. Callers must also design appropriate retry logic and implement fallback mechanisms to ensure smooth and reliable experience. This opt-in model has been deliberately chosen to allow the Azure Resource Graph team to better understand customer usage patterns and make improvements as needed.
22+
Contact the ARG product group by sending an email to Azure Resource Graph team sharing a brief overview of your scenario and the ARG team will reach out to you with next steps. Callers must also design appropriate retry logic and implement fallback mechanisms to ensure smooth and reliable experience. This opt-in model has been deliberately chosen to allow the Azure Resource Graph team to better understand customer usage patterns and make improvements as needed.
2323

2424
Refer to some known limitations [here](#known-limitations) and [frequently asked questions](#frequently-asked-questions).
2525

@@ -246,7 +246,7 @@ No special permissions are required for ARG GET/LIST APIs; ARG GET/LIST APIs are
246246

247247
5. What is the rollback strategy, if we find issues while using ARG GET/LIST APIs?  
248248

249-
If onboarded through the flag useResourceGraph=true, the caller may choose to remove the flag (or) useResourceGraph =false and the call will be automatically routed to be Resource Provider. 
249+
If onboarded through the flag `useResourceGraph=true`, the caller may choose to remove the flag (or) `useResourceGraph=false` and the call will be automatically routed to be Resource Provider. 
250250

251251
6. What if you're getting a 404 Not Found when trying to get a resource from ARG GET/LIST that was recently created?
252252

0 commit comments

Comments
 (0)