Azure Resource Graph throttlingĪzure Resource Graph limits the number of requests to its operations. For example, use the Virtual Machine Scale Set VMs - List with parameters to check the power state of virtual machine instances. Compute throttlingįor information about throttling limits for compute operations, see Troubleshooting API throttling errors - Compute.įor checking virtual machine instances within a Virtual Machine Scale Set, use the Virtual Machine Scale Sets operations. The Microsoft.Network resource provider applies the following throttle limits: OperationĪzure DNS and Azure Private DNS have a throttle limit of 500 read (GET) operations per 5 minutes. Storage account management operations (list) Storage account management operations (write) Storage account management operations (read) The limits apply per region of the resource in the request. The following limits apply only when you perform management operations by using Azure Resource Manager with Azure Storage. This section discusses the throttling limits of some widely used resource providers. Because Resource Manager throttles by instance of Resource Manager, and there are several instances of Resource Manager in each region, the resource provider might receive more requests than the default limits in the previous section. Within each subscription, the resource provider throttles per region of the resource in the request. Resource providers apply their own throttling limits. The remaining requests are returned in the response header values. The requests from a user are usually handled by different instances of Azure Resource Manager. So, in practice, the limits are higher than these limits. There are multiple instances in every Azure region, and Azure Resource Manager is deployed to all Azure regions. These limits apply to each Azure Resource Manager instance.
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 are scoped to the security principal (user or application) making the requests and the subscription ID or tenant ID. The default throttling limits per hour are shown in the following table. Tenant requests don't include your subscription ID, such as retrieving valid Azure locations. Subscription requests are ones that involve passing your subscription ID, such as retrieving the resource groups in your subscription. The resource provider requests are also throttled per principal user ID and per hour.Įvery subscription-level and tenant-level operation is subject to throttling limits. 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. The image shows that requests are initially throttled per principal ID and per Azure Resource Manager instance in the region of the user sending the request. The following image shows how throttling is applied as a request goes from the user to Azure Resource Manager and the resource provider. The resource provider applies throttling limits that are tailored to its operations. If the request is under the throttling limits for the subscription and tenant, Resource Manager routes the request to the resource provider.
Azure Resource Manager throttles requests for the subscription and tenant.
#Throttled data how to#
It shows you how to track the number of requests that remain before reaching the limit, and how to respond when you've reached the limit. This article describes how Azure Resource Manager throttles requests.
0 kommentar(er)
