Azure subscription and service limits, quotas, and constraints

This document lists some of the most common Microsoft Azure limits, which are also sometimes called quotas. This document doesn't currently cover all Azure services. Over time, the list will be expanded and updated to cover more services.

To learn more about Azure pricing, see Azure pricing overview. There, you can estimate your costs by using the pricing calculator. You also can go to the pricing details page for a particular service, for example, Windows VMs. For tips to help manage your costs, see Prevent unexpected costs with Azure billing and cost management.

Note

If you want to raise the limit or quota above the default limit, open an online customer support request at no charge. The limits can't be raised above the maximum limit value shown in the following tables. If there's no maximum limit column, the resource doesn't have adjustable limits.

Free Trial subscriptions aren't eligible for limit or quota increases. If you have a Free Trial subscription, you can upgrade to a Pay-As-You-Go subscription. For more information, see Upgrade your Azure Free Trial subscription to a Pay-As-You-Go subscription and the Free Trial subscription FAQ.

Limits and Azure Resource Manager

It's now possible to combine multiple Azure resources into a single Azure resource group. When you use resource groups, limits that once were global become managed at a regional level with Azure Resource Manager. For more information about Azure resource groups, see Azure Resource Manager overview.

In the following list of limits, a new table reflects any differences in limits when you use Azure Resource Manager. For example, there's a Subscription limits table and a Subscription limits - Azure Resource Manager table. When a limit applies to both scenarios, it's only shown in the first table. Unless otherwise indicated, limits are global across all regions.

Note

Quotas for resources in Azure resource groups are per-region accessible by your subscription, not per-subscription as the service management quotas are. Let's use vCPU quotas as an example. To request a quota increase with support for vCPUs, you must decide how many vCPUs you want to use in which regions. You then make a specific request for Azure resource group vCPU quotas for the amounts and regions that you want. If you need to use 30 vCPUs in West Europe to run your application there, you specifically request 30 vCPUs in West Europe. Your vCPU quota isn't increased in any other region--only West Europe has the 30-vCPU quota.

As a result, decide what your Azure resource group quotas must be for your workload in any one region. Then request that amount in each region into which you want to deploy. For help in how to determine your current quotas for specific regions, see Troubleshoot deployment issues.

Service-specific limits

Subscription limits

Subscription limits - Azure Service Management (classic deployment model)

Resource Default limit Maximum limit
vCPUs per subscription1 20 10,000
Coadministrators per subscription 200 200
Storage accounts per subscription2 100 100
Cloud services per subscription 20 200
Local networks per subscription 10 500
DNS servers per subscription 9 100
Reserved IPs per subscription 20 100
Affinity groups per subscription 256 256
Subscription name length (characters) 64 64

1Extra small instances count as one vCPU toward the vCPU limit despite using a partial CPU core.

2The storage account limit includes both Standard and Premium storage accounts.

Subscription limits - Azure Resource Manager

The following limits apply when you use Azure Resource Manager and Azure resource groups. Limits that haven't changed with Azure Resource Manager aren't listed. See the previous table for those limits.

For information about Resource Manager API read and write limits, see Throttling Resource Manager requests.

Resource Default limit Maximum limit
VMs per subscription 25,0001 per region. 25,000 per region.
VM total cores per subscription 201 per region. Contact support.
VM per series, such as Dv2 and F, cores per subscription 201 per region. Contact support.
Coadministrators per subscription Unlimited. Unlimited.
Storage accounts per region per subscription 250 250
Resource groups per subscription 980 980
Availability sets per subscription 2,000 per region. 2,000 per region.
Azure Resource Manager API request size 4,194,304 bytes. 4,194,304 bytes.
Tags per subscription2 Unlimited. Unlimited.
Unique tag calculations per subscription2 10,000 10,000
Cloud services per subscription N/A3 N/A3
Affinity groups per subscription N/A3 N/A3
Subscription-level deployments per location 8004 800

1Default limits vary by offer category type, such as Free Trial and Pay-As-You-Go, and by series, such as Dv2, F, and G. For example, the default for Enterprise Agreement subscriptions is 350.

2You can apply an unlimited number of tags per subscription. The number of tags per resource or resource group is limited to 50. Resource Manager returns a list of unique tag name and values in the subscription only when the number of tags is 10,000 or less. You still can find a resource by tag when the number exceeds 10,000.

3These features are no longer required with Azure resource groups and Resource Manager.

4If you reach the limit of 800 deployments, delete deployments from the history that are no longer needed. To delete subscription level deployments, use Remove-AzDeployment or az deployment delete.

Note

Virtual machine cores have a regional total limit. They also have a limit for regional per-size series, such as Dv2 and F. These limits are separately enforced. For example, consider a subscription with a US East total VM core limit of 30, an A series core limit of 30, and a D series core limit of 30. This subscription can deploy 30 A1 VMs, or 30 D1 VMs, or a combination of the two not to exceed a total of 30 cores. An example of a combination is 10 A1 VMs and 20 D1 VMs.

Resource group limits

Resource Default limit Maximum limit
Resources per resource group, per resource type 800 Some resource types can exceed the 800 limit. See Resources not limited to 800 instances per resource group.
Deployments per resource group in the deployment history 8001 800
Resources per deployment 800 800
Management locks per unique scope 20 20
Number of tags per resource or resource group 50 50
Tag key length 512 512
Tag value length 256 256

1If you reach the limit of 800 deployments per resource group, delete deployments from the history that are no longer needed. Deleting an entry from the deployment history doesn't affect the deployed resources. You can delete entries from the history with az group deployment delete for Azure CLI, or Remove-AzResourceGroupDeployment in PowerShell. For a PowerShell script that automates deleting deployments in a continuous integration and continuous delivery (CI/CD) scenario, see remove-deployments.ps1.

Template limits

Value Default limit Maximum limit
Parameters 256 256
Variables 256 256
Resources (including copy count) 800 800
Outputs 64 64
Template expression 24,576 chars 24,576 chars
Resources in exported templates 200 200
Template size 4 MB 4 MB
Parameter file size 64 KB 64 KB

You can exceed some template limits by using a nested template. For more information, see Use linked templates when you deploy Azure resources. To reduce the number of parameters, variables, or outputs, you can combine several values into an object. For more information, see Objects as parameters.

Virtual Machines limits

Virtual Machines limits

Resource Default limit Maximum limit
Virtual machines per cloud service1 50 50
Input endpoints per cloud service2 150 150

1Virtual machines created by using the classic deployment model instead of Azure Resource Manager are automatically stored in a cloud service. You can add more virtual machines to that cloud service for load balancing and availability.

2Input endpoints allow communications to a virtual machine from outside the virtual machine's cloud service. Virtual machines in the same cloud service or virtual network can automatically communicate with each other. For more information, see How to set up endpoints to a virtual machine.

Virtual Machines limits - Azure Resource Manager

The following limits apply when you use Azure Resource Manager and Azure resource groups. Limits that haven't changed with Azure Resource Manager aren't listed. See the previous table for those limits.

Resource Default limit
Virtual machines per availability set 200
Certificates per subscription Unlimited1

1With Azure Resource Manager, certificates are stored in the Azure Key Vault. The number of certificates is unlimited for a subscription. There's a 1-MB limit of certificates per deployment, which consists of either a single VM or an availability set.

There are limits, per subscription, for deploying resources using Shared Image Galleries:

  • 100 shared image galleries, per subscription, per region
  • 1,000 image definitions, per subscription, per region
  • 10,000 image versions, per subscription, per region

Virtual machine scale sets limits

Resource Default limit Maximum limit
Maximum number of VMs in a scale set 1,000 1,000
Maximum number of VMs based on a custom VM image in a scale set 600 600
Maximum number of scale sets in a region 2,000 2,000

Container Instances limits

Resource Default limit
Container groups per subscription 1001
Number of containers per container group 60
Number of volumes per container group 20
Ports per IP 5
Container instance log size - running instance 4 MB
Container instance log size - stopped instance 16 KB or 1,000 lines
Container creates per hour 3001
Container creates per 5 minutes 1001
Container deletes per hour 3001
Container deletes per 5 minutes 1001

1To request a limit increase, create an Azure Support request.

Container Registry limits

The following table details the features and limits of the Basic, Standard, and Premium service tiers.

Resource Basic Standard Premium
Storage1 10 GiB 100 GiB 500 GiB
Maximum image layer size 200 GiB 200 GiB 200 GiB
ReadOps per minute2, 3 1,000 3,000 10,000
WriteOps per minute2, 4 100 500 2,000
Download bandwidth MBps2 30 60 100
Upload bandwidth MBps2 10 20 50
Webhooks 2 10 100
Geo-replication N/A N/A Supported
Content trust N/A N/A Supported

1The specified storage limits are the amount of included storage for each tier. You're charged an additional daily rate per GiB for image storage above these limits. For rate information, see Azure Container Registry pricing.

2ReadOps, WriteOps, and Bandwidth are minimum estimates. Azure Container Registry strives to improve performance as usage requires.

3A docker pull translates to multiple read operations based on the number of layers in the image, plus the manifest retrieval.

4A docker push translates to multiple write operations, based on the number of layers that must be pushed. A docker push includes ReadOps to retrieve a manifest for an existing image.

Azure Kubernetes Service limits

Resource Default limit
Maximum clusters per subscription 100
Maximum nodes per cluster 100
Maximum pods per node: Basic networking with Kubenet 110
Maximum pods per node: Advanced networking with Azure Container Networking Interface Azure CLI deployment: 301
Azure Resource Manager template: 301
Portal deployment: 30

1When you deploy an Azure Kubernetes Service (AKS) cluster with the Azure CLI or a Resource Manager template, this value is configurable up to 250 pods per node. You can't configure maximum pods per node after you've already deployed an AKS cluster, or if you deploy a cluster by using the Azure portal.

Azure Machine Learning Service limits

The latest values for Azure Machine Learning Compute quotas can be found in the Azure Machine Learning quota page

Networking limits

Networking limits - Azure Resource Manager The following limits apply only for networking resources managed through Azure Resource Manager per region per subscription. Learn how to view your current resource usage against your subscription limits.

Note

We recently increased all default limits to their maximum limits. If there's no maximum limit column, the resource doesn't have adjustable limits. If you had these limits increased by support in the past and don't see updated limits in the following tables, open an online customer support request at no charge

Resource Default/maximum limit
Virtual networks 1,000
Subnets per virtual network 3,000
Virtual network peerings per virtual network 500
DNS servers per virtual network 20
Private IP addresses per virtual network 65,536
Private IP addresses per network interface 256
Private IP addresses per virtual machine 256
Public IP addresses per network interface 256
Public IP addresses per virtual machine 256
Concurrent TCP or UDP flows per NIC of a virtual machine or role instance 500,000
Network interface cards 65,536
Network Security Groups 5,000
NSG rules per NSG 1,000
IP addresses and ranges specified for source or destination in a security group 4,000
Application security groups 3,000
Application security groups per IP configuration, per NIC 20
IP configurations per application security group 4,000
Application security groups that can be specified within all security rules of a network security group 100
User-defined route tables 200
User-defined routes per route table 400
Point-to-site root certificates per Azure VPN Gateway 20
Virtual network TAPs 100
Network interface TAP configurations per virtual network TAP 100

Public IP address limits

Resource Default limit Maximum limit
Public IP addresses - dynamic 1,000 for Basic. Contact support.
Public IP addresses - static 1,000 for Basic. Contact support.
Public IP addresses - static 1,000 for Standard. Contact support.
Public IP prefix length /28 Contact support.

Load balancer limits

The following limits apply only for networking resources managed through Azure Resource Manager per region per subscription. Learn how to view your current resource usage against your subscription limits.

Resource Default/maximum limit
Load balancers 1,000
Rules per resource, Basic 250
Rules per resource, Standard 1,500
Rules per IP configuration 299
Rules per NIC 300
Front-end IP configurations, Basic 200
Front-end IP configurations, Standard 600
Back-end pool, Basic 100, single availability set
Back-end pool, Standard 1,000, single virtual network
Back-end resources per load balancer, Standard1 150
High-availability ports, Standard 1 per internal front-end

1The limit is up to 150 resources, in any combination of standalone virtual machine resources, availability set resources, and virtual machine scale-set resources.

The following limits apply only for networking resources managed through the classic deployment model per subscription. Learn how to view your current resource usage against your subscription limits.

Resource Default limit Maximum limit
Virtual networks 100 100
Local network sites 20 50
DNS servers per virtual network 20 20
Private IP addresses per virtual network 4,096 4,096
Concurrent TCP or UDP flows per NIC of a virtual machine or role instance 500,000, up to 1,000,000 for two or more NICs. 500,000, up to 1,000,000 for two or more NICs.
Network Security Groups (NSGs) 200 200
NSG rules per NSG 1,000 1,000
User-defined route tables 200 200
User-defined routes per route table 400 400
Public IP addresses (dynamic) 500 500
Reserved public IP addresses 500 500
Public VIP per deployment 5 Contact support
Private VIP (internal load balancing) per deployment 1 1
Endpoint access control lists (ACLs) 50 50

ExpressRoute limits

Resource Default/maximum limit
ExpressRoute circuits per subscription 10
ExpressRoute circuits per region per subscription, with Azure Resource Manager 10
Maximum number of routes advertised to Azure private peering with ExpressRoute Standard 4,000
Maximum number of routes advertised to Azure private peering with ExpressRoute Premium add-on 10,000
Maximum number of routes advertised from Azure private peering from the VNet address space for an ExpressRoute connection 200
Maximum number of routes advertised to Microsoft peering with ExpressRoute Standard 200
Maximum number of routes advertised to Microsoft peering with ExpressRoute Premium add-on 200
Maximum number of ExpressRoute circuits linked to the same virtual network in the same peering location 4
Maximum number of ExpressRoute circuits linked to the same virtual network in different peering locations 4
Number of virtual network links allowed per ExpressRoute circuit See the Number of virtual networks per ExpressRoute circuit table.

Number of virtual networks per ExpressRoute circuit

Circuit size Number of virtual network links for Standard Number of virtual network links with Premium add-on
50 Mbps 10 20
100 Mbps 10 25
200 Mbps 10 25
500 Mbps 10 40
1 Gbps 10 50
2 Gbps 10 60
5 Gbps 10 75
10 Gbps 10 100
40 Gbps* 10 100
100 Gbps* 10 100

*100 Gbps ExpressRoute Direct Only

Application Gateway limits

The following table applies to v1, v2, Standard, and WAF SKUs unless otherwise stated.

Resource Default/maximum limit Note
Azure Application Gateway 1,000 per subscription
Front-end IP configurations 2 1 public and 1 private
Front-end ports 1001
Back-end address pools 1001
Back-end servers per pool 1,200
HTTP listeners 1001
HTTP load-balancing rules 1001
Back-end HTTP settings 1001
Instances per gateway 32
SSL certificates 1001 1 per HTTP listeners
Maximum SSL certificate size V1 SKU - 10 KB
V2 SKU - 16 KB
Authentication certificates 100
Trusted root certificates 100
Request timeout minimum 1 second
Request timeout maximum 24 hours
Number of sites 1001 1 per HTTP listeners
URL maps per listener 1
Maximum path-based rules per URL map 100
Redirect configurations 1001
Concurrent WebSocket connections Medium gateways 20k
Large gateways 50k
Maximum URL length 8,000
Maximum file upload size, Standard 2 GB
Maximum file upload size WAF Medium WAF gateways, 100 MB
Large WAF gateways, 500 MB
WAF body size limit, without files 128 KB
Maximum WAF custom rules 100
Maximum WAF exclusions 100

1 In case of WAF-enabled SKUs, we recommend that you limit the number of resources to 40 for optimal performance.

Network Watcher limits

Resource Default limit Maximum limit Note
Azure Network Watcher 1 per region 1 per region Network Watcher is created to enable access to the service. Only one instance of Network Watcher is required per subscription per region.
Packet capture sessions 100 per region 10,000 Number of sessions only, not saved captures.

The following limits apply to Azure private link:

Resource Limit
Number of private endpoints per virtual network 1000
Number of private endpoints per subscription      64000
Number of private link service per subscription       32
Number of IP Configurations on a private link service    8 (This number is for the NAT IP addresses used per PLS)
Number of private endpoints on the same private link service  1000

Traffic Manager limits

Resource Default/maximum limit
Profiles per subscription 200
Endpoints per profile 200

Azure DNS limits

Public DNS zones

Resource Default limit
Public DNS Zones per subscription 250 1
Record sets per public DNS zone 10,000 1
Records per record set in public DNS zone 20
Number of Alias records for a single Azure resource 20
Private DNS zones per subscription 1000
Record sets per private DNS zone 25000
Records per record set for private DNS zones 20
Virtual Network Links per private DNS zone 1000
Virtual Networks Links per private DNS zones with auto-registration enabled 100
Number of private DNS zones a virtual network can get linked to with auto-registration enabled 1
Number of private DNS zones a virtual network can get linked 1000

1If you need to increase these limits, contact Azure Support.

Azure Firewall limits

Resource Default limit
Data throughput 30 Gbps1
Rules 10,000, all rule types combined.
Minimum AzureFirewallSubnet size /26
Port range in network and application rules 0-64,000. Work is in progress to relax this limitation.
Public IP addresses 100 maximum
Route table By default, AzureFirewallSubnet has a 0.0.0.0/0 route with the NextHopType value set to Internet.

Azure Firewall must have direct Internet connectivity. If your AzureFirewallSubnet learns a default route to your on-premises network via BGP, you must override that with a 0.0.0.0/0 UDR with the NextHopType value set as Internet to maintain direct Internet connectivity. By default, Azure Firewall doesn't support forced tunneling to an on-premises network.

However, if your configuration requires forced tunneling to an on-premises network, Microsoft will support it on a case by case basis. Contact Support so that we can review your case. If accepted, we'll allow your subscription and ensure the required firewall Internet connectivity is maintained.

1If you need to increase these limits, contact Azure Support.

Azure Front Door Service limits

Resource Default/maximum limit
Azure Front Door Service resources per subscription 100
Front-end hosts, which includes custom domains per resource 100
Routing rules per resource 100
Back-end pools per resource 50
Back ends per back-end pool 100
Path patterns to match for a routing rule 25
Custom web application firewall rules per policy 10
Web application firewall policy per resource 100
Web application firewall match conditions per custom rule 10
Web application firewall IP address ranges per match condition 600
Web application firewall string match values per match condition 10
Web application firewall string match value length 256
Web application firewall POST body parameter name length 256
Web application firewall HTTP header name length 256
Web application firewall cookie name length 256
Web application firewall HTTP request body size inspected 128 KB
Web application firewall custom response body length 2 KB

Timeout values

Client to Front Door

  • Front Door has an idle TCP connection timeout of 61 seconds.

Front Door to application back-end

  • If the response is a chunked response, a 200 is returned if or when the first chunk is received.
  • After the HTTP request is forwarded to the back end, Front Door waits for 30 seconds for the first packet from the back end. Then it returns a 503 error to the client.
  • After the first packet is received from the back end, Front Door waits for 30 seconds in an idle timeout. Then it returns a 503 error to the client.
  • Front Door to the back-end TCP session timeout is 30 minutes.

Upload and download data limit

With chunked transfer encoding (CTE) Without HTTP chunking
Download There's no limit on the download size. There's no limit on the download size.
Upload There's no limit as long as each CTE upload is less than 2 GB. The size can't be larger than 2 GB.

Other limits

  • Maximum URL size - 8,192 bytes - Specifies maximum length of the raw URL (scheme + hostname + port + path + query string of the URL)- Maximum Query String size - 4,096 bytes - Specifies the maximum length of the query string, in bytes.

Storage limits

The following table describes default limits for Azure general-purpose v1, v2, and Blob storage accounts. The ingress limit refers to all data from requests that are sent to a storage account. The egress limit refers to all data from responses that are received from a storage account.

Resource Default limit
Number of storage accounts per region per subscription, including both standard and premium accounts 250
Maximum storage account capacity 2 PB for US and Europe, and 500 TB for all other regions (including the UK)1
Maximum number of blob containers, blobs, file shares, tables, queues, entities, or messages per storage account No limit
Maximum request rate1 per storage account 20,000 requests per second
Maximum ingress1 per storage account (US, Europe regions) 25 Gbps
Maximum ingress1 per storage account (regions other than US and Europe) 5 Gbps if RA-GRS/GRS is enabled, 10 Gbps for LRS/ZRS2
Maximum egress for general-purpose v2 and Blob storage accounts (all regions) 50 Gbps
Maximum egress for general-purpose v1 storage accounts (US regions) 20 Gbps if RA-GRS/GRS is enabled, 30 Gbps for LRS/ZRS2
Maximum egress for general-purpose v1 storage accounts (non-US regions) 10 Gbps if RA-GRS/GRS is enabled, 15 Gbps for LRS/ZRS2

1Azure Standard Storage accounts support higher capacity limits and higher limits for ingress by request. To request an increase in account limits for ingress, contact Azure Support. For more information, see Announcing larger, higher scale storage accounts.

2 Azure Storage replication options include:

  • RA-GRS: Read-access geo-redundant storage. If RA-GRS is enabled, egress targets for the secondary location are identical to those for the primary location.
  • GRS: Geo-redundant storage.
  • ZRS: Zone-redundant storage.
  • LRS: Locally redundant storage.

Note

We recommend that you use a general-purpose v2 storage account for most scenarios. You can easily upgrade a general-purpose v1 or an Azure Blob storage account to a general-purpose v2 account with no downtime and without the need to copy data.

For more information on Azure Storage accounts, see Storage account overview.

If the needs of your application exceed the scalability targets of a single storage account, you can build your application to use multiple storage accounts. You can then partition your data objects across those storage accounts. For information on volume pricing, see Azure Storage pricing.

All storage accounts run on a flat network topology and support the scalability and performance targets outlined in this article, regardless of when they were created. For more information on the Azure Storage flat network architecture and on scalability, see Microsoft Azure Storage: A Highly Available Cloud Storage Service with Strong Consistency.

For more information on storage account limits, see Azure Storage scalability and performance targets.

Storage resource provider limits

The following limits apply only when you perform management operations by using Azure Resource Manager with Azure Storage.

Resource Default limit
Storage account management operations (read) 800 per 5 minutes
Storage account management operations (write) 200 per hour
Storage account management operations (list) 100 per 5 minutes

Azure Blob storage limits

Resource Target
Maximum size of single blob container Same as maximum storage account capacity
Maximum number of blocks in a block blob or append blob 50,000 blocks
Maximum size of a block in a block blob 100 MiB
Maximum size of a block blob 50,000 X 100 MiB (approximately 4.75 TiB)
Maximum size of a block in an append blob 4 MiB
Maximum size of an append blob 50,000 x 4 MiB (approximately 195 GiB)
Maximum size of a page blob 8 TiB
Maximum number of stored access policies per blob container 5
Target throughput for single blob Up to storage account ingress/egress limits1

1 Single object throughput depends on several factors, including, but not limited to: concurrency, request size, performance tier, speed of source for uploads, and destination for downloads. To take advantage of high-throughput block blob performance enhancements, use a Put Blob or Put Block request size of > 4 MiB (> 256 KiB for premium-performance block blob storage or for Data Lake Storage Gen2).

Azure Files limits

For more information on Azure Files limits, see Azure Files scalability and performance targets.

Resource Standard file shares Premium file shares
Minimum size of a file share No minimum; pay as you go 100 GiB; provisioned
Maximum size of a file share 5 TiB (GA), 100 TiB (preview) 100 TiB
Maximum size of a file in a file share 1 TiB 1 TiB
Maximum number of files in a file share No limit No limit
Maximum IOPS per share 1,000 IOPS (GA), 10,000 IOPS (preview) 100,000 IOPS
Maximum number of stored access policies per file share 5 5
Target throughput for a single file share Up to 60 MiB/sec (GA), up to 300 MiB/sec (preview) See premium file share ingress and egress values
Maximum egress for a single file share See standard file share target throughput Up to 6,204 MiB/s
Maximum ingress for a single file share See standard file share target throughput Up to 4,136 MiB/s
Maximum open handles per file 2,000 open handles 2,000 open handles
Maximum number of share snapshots 200 share snapshots 200 share snapshots
Maximum object (directories and files) name length 2,048 characters 2,048 characters
Maximum pathname component (in the path \A\B\C\D, each letter is a component) 255 characters 255 characters

Azure File Sync limits

Resource Target Hard limit
Storage Sync Services per region 20 Storage Sync Services Yes
Sync groups per Storage Sync Service 100 sync groups Yes
Registered servers per Storage Sync Service 99 servers Yes
Cloud endpoints per sync group 1 cloud endpoint Yes
Server endpoints per sync group 50 server endpoints No
Server endpoints per server 30 server endpoints Yes
File system objects (directories and files) per sync group 50 million objects No
Maximum number of file system objects (directories and files) in a directory 5 million objects Yes
Maximum object (directories and files) security descriptor size 64 KiB Yes
File size 100 GiB No
Minimum file size for a file to be tiered 64 KiB Yes
Concurrent sync sessions V4 agent and later: The limit varies based on available system resources.
V3 agent: Two active sync sessions per processor or a maximum of eight active sync sessions per server.
Yes

Note

An Azure File Sync endpoint can scale up to the size of an Azure file share. If the Azure file share size limit is reached, sync will not be able to operate.

Azure Queue storage limits

Resource Target
Maximum size of a single queue 500 TiB
Maximum size of a message in a queue 64 KiB
Maximum number of stored access policies per queue 5
Maximum request rate per storage account 20,000 messages per second, which assumes a 1-KiB message size
Target throughput for a single queue (1-KiB messages) Up to 2,000 messages per second

Azure Table storage limits

Resource Target
Maximum size of a single table 500 TiB
Maximum size of a table entity 1 MiB
Maximum number of properties in a table entity 255, which includes three system properties: PartitionKey, RowKey, and Timestamp
Maximum total size of property values in an entity 1 MiB
Maximum total size of an individual property in an entity Varies by property type. For more information, see Property Types in Understanding the Table Service Data Model.
Maximum number of stored access policies per table 5
Maximum request rate per storage account 20,000 transactions per second, which assumes a 1-KiB entity size
Target throughput for a single table partition (1 KiB-entities) Up to 2,000 entities per second

Virtual machine disk limits

You can attach a number of data disks to an Azure virtual machine. Based on the scalability and performance targets for a VM's data disks, you can determine the number and type of disk that you need to meet your performance and capacity requirements.

Important

For optimal performance, limit the number of highly utilized disks attached to the virtual machine to avoid possible throttling. If all attached disks aren't highly utilized at the same time, the virtual machine can support a larger number of disks.

For Azure managed disks:

The following table illustrates the default and maximum limits of the number of resources per region per subscription. There is no limit for the number of Managed Disks, snapshots and images per resource group.

Resource Default limit Maximum limit
Standard managed disks 50,000 50,000
Standard SSD managed disks 50,000 50,000
Premium managed disks 50,000 50,000
Standard_LRS snapshots 50,000 50,000
Standard_ZRS snapshots 50,000 50,000
Managed image 50,000 50,000
  • For Standard storage accounts: A Standard storage account has a maximum total request rate of 20,000 IOPS. The total IOPS across all of your virtual machine disks in a Standard storage account should not exceed this limit.

    You can roughly calculate the number of highly utilized disks supported by a single Standard storage account based on the request rate limit. For example, for a Basic tier VM, the maximum number of highly utilized disks is about 66, which is 20,000/300 IOPS per disk. The maximum number of highly utilized disks for a Standard tier VM is about 40, which is 20,000/500 IOPS per disk.

  • For Premium storage accounts: A Premium storage account has a maximum total throughput rate of 50 Gbps. The total throughput across all of your VM disks should not exceed this limit.

For more information, see Virtual machine sizes.

Managed virtual machine disks

Standard HDD managed disks

Standard Disk Type S4 S6 S10 S15 S20 S30 S40 S50 S60 S70 S80
Disk size in GiB 32 64 128 256 512 1,024 2,048 4,096 8,192 16,384 32,767
IOPS per disk Up to 500 Up to 500 Up to 500 Up to 500 Up to 500 Up to 500 Up to 500 Up to 500 Up to 1,300 Up to 2,000 Up to 2,000
Throughput per disk Up to 60 MiB/sec Up to 60 MiB/sec Up to 60 MiB/sec Up to 60 MiB/sec Up to 60 MiB/sec Up to 60 MiB/sec Up to 60 MiB/sec Up to 60 MiB/sec Up to 300 MiB/sec Up to 500 MiB/sec Up to 500 MiB/sec

Standard SSD managed disks

Standard SSD sizes E4 E6 E10 E15 E20 E30 E40 E50 E60 E70 E80
Disk size in GiB 32 64 128 256 512 1,024 2,048 4,096 8,192 16,384 32,767
IOPS per disk Up to 120 Up to 240 Up to 500 Up to 500 Up to 500 Up to 500 Up to 500 Up to 500 Up to 2,000 Up to 4,000 Up to 6,000
Throughput per disk Up to 25 MiB/sec Up to 50 MiB/sec Up to 60 MiB/sec Up to 60 MiB/sec Up to 60 MiB/sec Up to 60 MiB/sec Up to 60 MiB/sec Up to 60 MiB/sec Up to 400 MiB/sec Up to 600 MiB/sec Up to 750 MiB/sec

Premium SSD managed disks: Per-disk limits

Premium SSD sizes  P4 P6 P10 P15 P20 P30 P40 P50 P60 P70 P80
Disk size in GiB 32 64 128 256 512 1,024 2,048 4,096 8,192 16,384 32,767
IOPS per disk Up to 120 Up to 240 Up to 500 Up to 1,100 Up to 2,300 Up to 5,000 Up to 7,500 Up to 7,500 Up to 16,000 Up to 18,000 Up to 20,000
Throughput per disk Up to 25 MiB/sec Up to 50 MiB/sec Up to 100 MiB/sec Up to 125 MiB/sec Up to 150 MiB/sec Up to 200 MiB/sec Up to 250 MiB/sec Up to 250 MiB/sec Up to 500 MiB/sec Up to 750 MiB/sec Up to 900 MiB/sec

Premium SSD managed disks: Per-VM limits

Resource Default limit
Maximum IOPS Per VM 80,000 IOPS with GS5 VM
Maximum throughput per VM 2,000 MB/s with GS5 VM

Unmanaged virtual machine disks

Standard unmanaged virtual machine disks: Per-disk limits

VM tier Basic tier VM Standard tier VM
Disk size 4,095 GB 4,095 GB
Maximum 8-KB IOPS per persistent disk 300 500
Maximum number of disks that perform the maximum IOPS 66 40

Premium unmanaged virtual machine disks: Per-account limits

Resource Default limit
Total disk capacity per account 35 TB
Total snapshot capacity per account 10 TB
Maximum bandwidth per account (ingress + egress)1 <=50 Gbps

1Ingress refers to all data from requests that are sent to a storage account. Egress refers to all data from responses that are received from a storage account.

Premium unmanaged virtual machine disks: Per-disk limits

Premium storage disk type P10 P20 P30 P40 P50
Disk size 128 GiB 512 GiB 1,024 GiB (1 TB) 2,048 GiB (2 TB) 4,095 GiB (4 TB)
Maximum IOPS per disk 500 2,300 5,000 7,500 7,500
Maximum throughput per disk 100 MB/sec 150 MB/sec 200 MB/sec 250 MB/sec 250 MB/sec
Maximum number of disks per storage account 280 70 35 17 8

Premium unmanaged virtual machine disks: Per-VM limits

Resource Default limit
Maximum IOPS per VM 80,000 IOPS with GS5 VM
Maximum throughput per VM 2,000 MB/sec with GS5 VM

Azure Cloud Services limits

Resource Default limit Maximum limit
Web or worker roles per deployment1 25 25
Instance input endpoints per deployment 25 25
Input endpoints per deployment 25 25
Internal endpoints per deployment 25 25
Hosted service certificates per deployment 199 199

1Each Azure Cloud Service with web or worker roles can have two deployments, one for production and one for staging. This limit refers to the number of distinct roles, that is, configuration. This limit doesn't refer to the number of instances per role, that is, scaling.

Azure Cognitive Services limits

The following limits are for the number of Cognitive Services resources per Azure subscription. Each of the Cognitive Services may have additional limitations, for more information see Azure Cognitive Services.

Type Limit Example
A mixture of Cognitive Services resources Maximum of 200 total Cognitive Services resources. 100 Computer Vision resources in West US 2, 50 Speech Service resources in West US, and 50 Text Analytics resources in East US.
A single type of Cognitive Services resources. Maximum of 100 resources per region, with a maximum of 200 total Cognitive Services resources. 100 Computer Vision resources in West US 2, and 100 Computer Vision resources in East US.

App Service limits

The following App Service limits include limits for Web Apps, Mobile Apps, and API Apps.

Resource Free Shared Basic Standard Premium (v2) Isolated
Web, mobile, or API apps per Azure App Service plan1 10 100 Unlimited2 Unlimited2 Unlimited2 Unlimited2
App Service plan 10 per region 10 per resource group 100 per resource group 100 per resource group 100 per resource group 100 per resource group
Compute instance type Shared Shared Dedicated3 Dedicated3 Dedicated3

Dedicated3
Scale out (maximum instances) 1 shared 1 shared 3 dedicated3 10 dedicated3 20 dedicated3 100 dedicated4
Storage5 1 GB5 1 GB5 10 GB5 50 GB5 250 GB5

1 TB5
CPU time (5 minutes)6 3 minutes 3 minutes Unlimited, pay at standard rates Unlimited, pay at standard rates Unlimited, pay at standard rates Unlimited, pay at standard rates
CPU time (day)6 60 minutes 240 minutes Unlimited, pay at standard rates Unlimited, pay at standard rates Unlimited, pay at standard rates Unlimited, pay at standard rates
Memory (1 hour) 1,024 MB per App Service plan 1,024 MB per app N/A N/A N/A N/A
Bandwidth 165 MB Unlimited, data transfer rates apply Unlimited, data transfer rates apply Unlimited, data transfer rates apply Unlimited, data transfer rates apply Unlimited, data transfer rates apply
Application architecture 32-bit 32-bit 32-bit/64-bit 32-bit/64-bit 32-bit/64-bit 32-bit/64-bit
Web sockets per instance7 5 35 350 Unlimited Unlimited Unlimited
Concurrent debugger connections per application 1 1 1 5 5 5
App Service Certificates per subscription10 Not supported Not supported 10 10 10 10
Custom domains per app 0 (azurewebsites.net subdomain only) 500 500 500 500 500
Custom domain SSL support Not supported, wildcard certificate for *.azurewebsites.net available by default Not supported, wildcard certificate for *.azurewebsites.net available by default Unlimited SNI SSL connections Unlimited SNI SSL and 1 IP SSL connections included Unlimited SNI SSL and 1 IP SSL connections included Unlimited SNI SSL and 1 IP SSL connections included
Integrated load balancer X X X X X9
Always On X X X X
Scheduled backups Scheduled backups every 2 hours, a maximum of 12 backups per day (manual + scheduled) Scheduled backups every hour, a maximum of 50 backups per day (manual + scheduled) Scheduled backups every hour, a maximum of 50 backups per day (manual + scheduled)
Autoscale X X X
WebJobs8 X X X X X X
Azure Scheduler support X X X X X
Endpoint monitoring X X X X
Staging slots 5 20 20
SLA 99.95% 99.95% 99.95% 99.95%

1Apps and storage quotas are per App Service plan unless noted otherwise.
2The actual number of apps that you can host on these machines depends on the activity of the apps, the size of the machine instances, and the corresponding resource utilization.
3Dedicated instances can be of different sizes. For more information, see App Service pricing.
4More are allowed upon request.
5The storage limit is the total content size across all apps in the same App Service plan.
6These resources are constrained by physical resources on the dedicated instances (the instance size and the number of instances).
7If you scale an app in the Basic tier to two instances, you have 350 concurrent connections for each of the two instances. For Standard tier and above, there are no theoretical limits to web sockets, but other factors can limit the number of web sockets. For example, maximum concurrent requests allowed (defined by maxConcurrentRequestsPerCpu) are: 7,500 per small VM, 15,000 per medium VM (7,500 x 2 cores), and 75,000 per large VM (18,750 x 4 cores).
8Run custom executables and/or scripts on demand, on a schedule, or continuously as a background task within your App Service instance. Always On is required for continuous WebJobs execution. Azure Scheduler Free or Standard is required for scheduled WebJobs. There's no predefined limit on the number of WebJobs that can run in an App Service instance. There are practical limits that depend on what the application code is trying to do.
9App Service Isolated SKUs can be internally load balanced (ILB) with Azure Load Balancer, so there's no public connectivity from the internet. As a result, some features of an ILB Isolated App Service must be used from machines that have direct access to the ILB network endpoint.
10The App Service Certificate quota limit per subscription can be increased via a support request to a maximum limit of 200.

Functions limits

Resource Consumption plan Premium plan App Service plan1
Scale out Event driven Event driven Manual/autoscale
Max instances 200 20 10-20
Default time out duration (min) 5 30 302
Max time out duration (min) 10 unbounded unbounded3
Max outbound connections (per instance) 600 active (1200 total) unbounded unbounded
Max request size (MB)4 100 100 100
Max query string length4 4096 4096 4096
Max request URL length4 8192 8192 8192
ACU per instance 100 210-840 100-840
Max memory (GB per instance) 1.5 3.5-14 1.75-14
Function apps per plan 100 100 unbounded5
App Service plans 100 per region 100 per resource group 100 per resource group
Storage6 1 GB 250 GB 50-1000 GB
Custom domains per app 5007 500 500
Custom domain SSL support unbounded SNI SSL connection included unbounded SNI SSL and 1 IP SSL connections included unbounded SNI SSL and 1 IP SSL connections included

1 For specific limits for the various App Service plan options, see the App Service plan limits.
2 By default, the timeout for the Functions 1.x runtime in an App Service plan is unbounded.
3 Requires the App Service plan be set to Always On. Pay at standard rates.
4 These limits are set in the host.
5 The actual number of function apps that you can host depends on the activity of the apps, the size of the machine instances, and the corresponding resource utilization.
6 The storage limit is the total content size in temporary storage across all apps in the same App Service plan. Consumption plan uses Azure Files for temporary storage.
7 When your function app is hosted in a Consumption plan, only the CNAME option is supported. For function apps in a Premium plan or an App Service plan, you can map a custom domain using either a CNAME or an A record.

Scheduler limits

The following table describes each of the major quotas, limits, defaults, and throttles in Azure Scheduler.

Resource Limit description
Job size The maximum job size is 16,000. If a PUT or a PATCH operation results in a job size larger than this limit, a 400 Bad Request status code is returned.
Job collections The maximum number of job collections per Azure subscription is 200,000.
Jobs per collection By default, the maximum number of jobs is five jobs in a free job collection and 50 jobs in a standard job collection.

You can change the maximum number of jobs on a job collection. All jobs in a job collection are limited to the value set on the job collection. If you attempt to create more jobs than the maximum jobs quota, the request fails with a 409 Conflict status code.

Time to start time The maximum "time to start time" is 18 months.
Recurrence span The maximum recurrence span is 18 months.
Frequency By default, the maximum frequency quota is one hour in a free job collection and one minute in a standard job collection.

You can make the maximum frequency on a job collection lower than the maximum. All jobs in the job collection are limited to the value set on the job collection. If you attempt to create a job with a higher frequency than the maximum frequency on the job collection, the request fails with a 409 Conflict status code.

Body size The maximum body size for a request is 8,192 chars.
Request URL size The maximum size for a request URL is 2,048 chars.
Header count The maximum header count is 50 headers.
Aggregate header size The maximum aggregate header size is 4,096 chars.
Timeout The request timeout is static, that is, not configurable. and is 60 seconds for HTTP actions. For longer running operations, follow the HTTP asynchronous protocols. For example, return a 202 immediately but continue working in the background.
Job history The maximum response body stored in job history is 2,048 bytes.
Job history retention Job history is kept for up to two months or up to the last 1,000 executions.
Completed and faulted job retention Completed and faulted jobs are kept for 60 days.

Batch limits

Resource Default limit Maximum limit
Azure Batch accounts per region per subscription 1-3 50
Dedicated cores per Batch account 90-900 Contact support
Low-priority cores per Batch account 10-100 Contact support
Active jobs and job schedules per Batch account (completed jobs have no limit) 100-300 1,0001
Pools per Batch account 20-100 5001

Note

Default limits vary depending on the type of subscription you use to create a Batch account. Cores quotas shown are for Batch accounts in Batch service mode. View the quotas in your Batch account.

1To request an increase beyond this limit, contact Azure Support.

BizTalk Services limits

The following table shows the limits for Azure BizTalk Services.

Resource Free (Preview) Developer Basic Standard Premium
Scale out N/A N/A Yes, in increments of 1 Basic unit Yes, in increments of 1 Standard unit Yes, in increments of 1 Premium unit
Scale limit N/A N/A Up to 8 units Up to 8 units Up to 8 units
EAI bridges per unit N/A 25 25 125 500
EDI agreements per unit N/A 10 50 250 1,000
Hybrid connections per unit 5 5 10 50 100
Hybrid connection data transfer (GBs) per unit 5 5 50 250 500
Number of connections that use BizTalk Adapter Service per unit N/A 1 2 5 25
Archiving N/A Available N/A N/A Available
High availability N/A N/A Available Available Available

Azure Cosmos DB limits

For Azure Cosmos DB limits, see Limits in Azure Cosmos DB.

Azure Database for MySQL

For Azure Database for MySQL limits, see Limitations in Azure Database for MySQL.

Azure Database for PostgreSQL

For Azure Database for PostgreSQL limits, see Limitations in Azure Database for PostgreSQL.

Azure Search limits

Pricing tiers determine the capacity and limits of your search service. Tiers include:

  • Free multitenant service, shared with other Azure subscribers, is intended for evaluation and small development projects.
  • Basic provides dedicated computing resources for production workloads at a smaller scale, with up to three replicas for highly available query workloads.
  • Standard, which includes S1, S2, S3, and S3 High Density, is for larger production workloads. Multiple levels exist within the Standard tier so that you can choose a resource configuration that best matches your workload profile.

Limits per subscription

You can create multiple services within a subscription. Each one can be provisioned at a specific tier. You're limited only by the number of services allowed at each tier. For example, you could create up to 12 services at the Basic tier and another 12 services at the S1 tier within the same subscription. For more information about tiers, see Choose an SKU or tier for Azure Search.

Maximum service limits can be raised upon request. If you need more services within the same subscription, contact Azure Support.

Resource Free1 Basic S1 S2 S3 S3 HD L1 L2
Maximum services 1 16 16 8 6 6 6 6
Maximum scale in search units (SU)2 N/A 3 SU 36 SU 36 SU 36 SU 36 SU 36 SU 36 SU

1 Free is based on shared, not dedicated, resources. Scale-up is not supported on shared resources.

2 Search units are billing units, allocated as either a replica or a partition. You need both resources for storage, indexing, and query operations. To learn more about SU computations, see Scale resource levels for query and index workloads.

Limits per search service

Storage is constrained by disk space or by a hard limit on the maximum number of indexes, document, or other high-level resources, whichever comes first. The following table documents storage limits. For maximum limits on indexes, documents, and other objects, see Limits by resource.

Resource Free Basic1 S1 S2 S3 S3 HD2 L1 L2
Service level agreement (SLA)3 No Yes Yes Yes Yes Yes Yes Yes
Storage per partition 50 MB 2 GB 25 GB 100 GB 200 GB 200 GB 1 TB 2 TB
Partitions per service N/A 1 12 12 12 3 12 12
Partition size N/A 2 GB 25 GB 100 GB 200 GB 200 GB 1 TB 2 TB
Replicas N/A 3 12 12 12 12 12 12

1 Basic has one fixed partition. At this tier, additional search units are used for allocating more replicas for increased query workloads.

2 S3 HD has a hard limit of three partitions, which is lower than the partition limit for S3. The lower partition limit is imposed because the index count for S3 HD is substantially higher. Given that service limits exist for both computing resources (storage and processing) and content (indexes and documents), the content limit is reached first.

3 Service level agreements are offered for billable services on dedicated resources. Free services and preview features have no SLA. For billable services, SLAs take effect when you provision sufficient redundancy for your service. Two or more replicas are required for query (read) SLAs. Three or more replicas are required for query and indexing (read-write) SLAs. The number of partitions isn't an SLA consideration.

To learn more about limits on a more granular level, such as document size, queries per second, keys, requests, and responses, see Service limits in Azure Search.

Media Services limits

Note

For resources that aren't fixed, open a support ticket to ask for an increase in the quotas. Don't create additional Azure Media Services accounts in an attempt to obtain higher limits.

Resource Default limit
Azure Media Services accounts in a single subscription 25 (fixed)
Media reserved units per Media Services account 25 (S1)
10 (S2, S3)1
Jobs per Media Services account 50,0002
Chained tasks per job 30 (fixed)
Assets per Media Services account 1,000,000
Assets per task 50
Assets per job 100
Unique locators associated with an asset at one time 54
Live channels per Media Services account 5
Programs in stopped state per channel 50
Programs in running state per channel 3
Streaming endpoints that are stopped or running per Media Services account 2
Streaming units per streaming endpoint 10
Storage accounts 1,0005 (fixed)
Policies 1,000,0006
File size In some scenarios, there's a limit on the maximum file size supported for processing in Media Services.7

1If you change the type, for example, from S2 to S1, the maximum reserved unit limits are reset.

2This number includes queued, finished, active, and canceled jobs. It doesn't include deleted jobs. You can delete old jobs by using IJob.Delete or the DELETE HTTP request.

As of April 1, 2017, any job record in your account older than 90 days is automatically deleted, along with its associated task records. Automatic deletion occurs even if the total number of records is below the maximum quota. To archive the job and task information, use the code described in Manage assets with the Media Services .NET SDK.

3When you make a request to list job entities, a maximum of 1,000 jobs is returned per request. To keep track of all submitted jobs, use the top or skip queries as described in OData system query options.

4Locators aren't designed for managing per-user access control. To give different access rights to individual users, use digital rights management (DRM) solutions. For more information, see Protect your content with Azure Media Services.

5The storage accounts must be from the same Azure subscription.

6There's a limit of 1,000,000 policies for different Media Services policies. An example is for the Locator policy or ContentKeyAuthorizationPolicy.

Note

If you always use the same days and access permissions, use the same policy ID. For information and an example, see Manage assets with the Media Services .NET SDK.

7The maximum size supported for a single blob is currently up to 5 TB in Azure Blob Storage. Additional limits apply in Media Services based on the VM sizes that are used by the service. The size limit applies to the files that you upload and also the files that get generated as a result of Media Services processing (encoding or analyzing). If your source file is larger than 260-GB, your Job will likely fail.

The following table shows the limits on the media reserved units S1, S2, and S3. If your source file is larger than the limits defined in the table, your encoding job fails. If you encode 4K resolution sources of long duration, you're required to use S3 media reserved units to achieve the performance needed. If you have 4K content that's larger than the 260-GB limit on the S3 media reserved units, contact us at amshelp@microsoft.com for potential mitigations to support your scenario.

Media reserved unit type Maximum input size (GB)
S1 26
S2 60
S3 260

Content Delivery Network limits

Resource Default limit
Azure Content Delivery Network profiles 25
Content Delivery Network endpoints per profile 25
Custom domains per endpoint 25

A Content Delivery Network subscription can contain one or more Content Delivery Network profiles. A Content Delivery Network profile can contain one or more Content Delivery Network endpoints. You might want to use multiple profiles to organize your Content Delivery Network endpoints by internet domain, web application, or some other criteria.

Mobile Services limits

Tier Free Basic Standard
API calls 500,000 1.5 million per unit 15 million per unit
Active devices 500 Unlimited Unlimited
Scale N/A Up to 6 units Unlimited units
Push notifications Azure Notification Hubs Free tier included, up to 1 million pushes Notification Hubs Basic tier included, up to 10 million pushes Notification Hubs Standard tier included, up to 10 million pushes
Real-time messaging/
Web Sockets
Limited 350 per mobile service Unlimited
Offline synchronizations Limited Included Included
Scheduled jobs Limited Included Included
Azure SQL Database (required)
Standard rates apply for additional capacity
20 MB included 20 MB included 20 MB included
CPU capacity 60 minutes per day Unlimited Unlimited
Outbound data transfer 165 MB per day (daily rollover) Included Included

For more information on limits and pricing, see Azure Mobile Services pricing.

Azure Monitor limits

Alerts

Resource Default limit Maximum limit
Metric alerts (classic) 100 active alert rules per subscription. Call support.
Metric alerts 1000 active alert rules per subscription (in public clouds) and 100 active alert rules per subscription in Azure China 21Vianet and Azure Government. Call support.
Activity log alerts 100 active alert rules per subscription. Same as default.
Log alerts 512 Call support.
Action groups 2,000 action groups per subscription. Call support.
Autoscale settings 100 per region per subscription. Same as default.

Action groups

Resource Default limit Maximum limit
Azure app push 10 Azure app actions per action group. Call support.
Email 1,000 email actions in an action group.
No more than 100 emails in an hour.
Also see the rate limiting information.
Call support.
ITSM 10 ITSM actions in an action group. Call support.
Logic app 10 logic app actions in an action group. Call support.
Runbook 10 runbook actions in an action group. Call support.
SMS 10 SMS actions in an action group.
No more than 1 SMS message every 5 minutes.
Also see the rate limiting information.
Call support.
Voice 10 voice actions in an action group.
No more than 1 voice call every 5 minutes.
Also see the rate limiting information.
Call support.
Webhook 10 webhook actions in an action group. Maximum number of webhook calls is 1500 per minute per subscription. Other limits are available at action-specific information. Call support.

Log queries and language

Limit Description
Query language Azure Monitor uses the same Kusto query language as Azure Data Explorer. See Azure Monitor log query language differences for KQL language elements not supported in Azure Monitor.
Azure regions Log queries can experience excessive overhead when data spans Log Analytics workspaces in multiple Azure regions. See Query limits for details.
Cross resource queries Maximum number of Application Insights resources and Log Analytics workspaces in a single query limited to 100.
Cross-resource query is not supported in View Designer.
Cross-resource query in log alerts is supported in the new scheduledQueryRules API.
See Cross-resource query limits for details.

Log Analytics workspaces

Data collection volume and retention

Tier Limit per day Data retention Comment
Current Per GB pricing tier
(introduced April 2018)
No limit 30 - 730 days Data retention beyond 31 days is available for additional charges. Learn more about Azure Monitor pricing.
Legacy Free tiers
(introduced April 2016)
500 MB 7 days When your workspace reaches the 500 MB per day limit, data ingestion stops and resumes at the start of the next day. A day is based on UTC. Note that data collected by Azure Security Center is not included in this 500 MB per day limit and will continue to be collected above this limit.
Legacy Standalone Per GB tier
(introduced April 2016)
No limit 30 to 730 days Data retention beyond 31 days is available for additional charges. Learn more about Azure Monitor pricing.
Legacy Per Node (OMS)
(introduced April 2016)
No limit 30 to 730 days Data retention beyond 31 days is available for additional charges. Learn more about Azure Monitor pricing.
Legacy Standard tier No limit 30 days Retention can't be adjusted
Legacy Premium tier No limit 365 days Retention can't be adjusted

Number of workspaces per subscription.

Pricing tier Workspace limit Comments
Free tier 10 This limit can't be increased.
All other tiers No limit You're limited by the number of resources within a resource group and the number of resource groups per subscription.

Azure portal

Category Limits Comments
Maximum records returned by a log query 10,000 Reduce results using query scope, time range, and filters in the query.

Data Collector API

Category Limits Comments
Maximum size for a single post 30 MB Split larger volumes into multiple posts.
Maximum size for field values 32 KB Fields longer than 32 KB are truncated.

Search API

Category Limits Comments
Maximum records returned in a single query 500,000
Maximum size of data returned 64,000,000 bytes (~61 MiB)
Maximum query running time 10 minutes See Timeouts for details.
Maximum request rate 200 requests per 30 seconds per AAD user or client IP address See Rate limits for details.

General workspace limits

Category Limits Comments
Maximum columns in a table 500
Maximum characters for column name 500
Regions at capacity West Central US You cannot currently create a new workspace in this region since it is at temporary capacity limit. This limit is planned to be addressed by end of October, 2019.
Data export Not currently available Use Azure Function or Logic App to aggregate and export data.

Note

Depending on how long you've been using Log Analytics, you might have access to legacy pricing tiers. Learn more about Log Analytics legacy pricing tiers.

Application Insights

There are some limits on the number of metrics and events per application, that is, per instrumentation key. Limits depend on the pricing plan that you choose.

Resource Default limit Note
Total data per day 100 GB You can reduce data by setting a cap. If you need more data, you can increase the limit in the portal, up to 1,000 GB. For capacities greater than 1,000 GB, send email to AIDataCap@microsoft.com.
Throttling 32,000 events/second The limit is measured over a minute.
Data retention 90 days This resource is for Search, Analytics, and Metrics Explorer.
Availability multi-step test detailed results retention 90 days This resource provides detailed results of each step.
Maximum event size 64,000
Property and metric name length 150 See type schemas.
Property value string length 8,192 See type schemas.
Trace and exception message length 32,768 See type schemas.
Availability tests count per app 100
Profiler data retention 5 days
Profiler data sent per day 10 GB

For more information, see About pricing and quotas in Application Insights.

Notification Hubs limits

Tier Free Basic Standard
Included pushes 1 million 10 million 10 million
Active devices 500 200,000 10 million
Tag quota per installation or registration 60 60 60

For more information on limits and pricing, see Notification Hubs pricing.

Event Hubs limits

The following table lists quotas and limits specific to Azure Event Hubs. For information about Event Hubs pricing, see Event Hubs pricing.

Limit Scope Notes Value
Number of Event Hubs namespaces per subscription Subscription - 100
Number of event hubs per namespace Namespace Subsequent requests for creation of a new event hub are rejected. 10
Number of partitions per event hub Entity - 32
Maximum size of Event Hubs event Entity - 1 MB
Maximum size of an event hub name Entity - 50 characters
Number of non-epoch receivers per consumer group Entity - 5
Maximum throughput units Namespace Exceeding the throughput unit limit causes your data to be throttled and generates a server busy exception. To request a larger number of throughput units for a Standard tier, file a support request. Additional throughput units are available in blocks of 20 on a committed purchase basis. 20
Number of authorization rules per namespace Namespace Subsequent requests for authorization rule creation are rejected. 12
Number of calls to the GetRuntimeInformation method Entity - 50 per second
Number of virtual network (VNet) and IP Config rules Entity - 128

Event Hubs Basic and Standard - quotas and limits

Limit Scope Notes Basic Standard
Number of consumer groups per event hub Entity - 1 20
Number of AMQP connections per namespace Namespace Subsequent requests for additional connections are rejected, and an exception is received by the calling code. 100 5,000
Maximum retention period of event data Entity - 1 day 1-7 days
Apache Kafka enabled namespace Namespace Event Hubs namespace streams applications using Kafka protocol No Yes
Capture Entity When enabled, micro-batches on the same stream No Yes

Event Hubs Dedicated - quotas and limits

The Event Hubs Dedicated offering is billed at a fixed monthly price, with a minimum of 4 hours of usage. The Dedicated tier offers all the features of the Standard plan, but with enterprise scale capacity and limits for customers with demanding workloads.

Feature Limits
Bandwidth 20 CUs
Namespaces 50 per CU
Event Hubs 1000 per namespace
Ingress events Included
Message Size 1 Million Bytes
Partitions 2000 per CU
Consumer groups No limit per CU, 1000 per event hub
Brokered connections 100 K included
Message Retention Up to 7 days (90 day retention coming soon), 10 TB included per CU
Capture Included

Service Bus limits

The following table lists quota information specific to Azure Service Bus messaging. For information about pricing and other quotas for Service Bus, see Service Bus pricing.

Quota name Scope Notes Value
Maximum number of Basic or Standard namespaces per Azure subscription Namespace Subsequent requests for additional Basic or Standard namespaces are rejected by the Azure portal. 100
Maximum number of Premium namespaces per Azure subscription Namespace Subsequent requests for additional Premium namespaces are rejected by the portal. 50
Queue or topic size Entity Defined upon creation of the queue or topic.

Subsequent incoming messages are rejected, and an exception is received by the calling code.
1, 2, 3, 4 GB or 5 GB.

In the Premium SKU, and the Standard SKU with partitioning enabled, the maximum queue or topic size is 80 GB.
Number of concurrent connections on a namespace Namespace Subsequent requests for additional connections are rejected, and an exception is received by the calling code. REST operations don't count toward concurrent TCP connections. NetMessaging: 1,000.

AMQP: 5,000.
Number of concurrent receive requests on a queue, topic, or subscription entity Entity Subsequent receive requests are rejected, and an exception is received by the calling code. This quota applies to the combined number of concurrent receive operations across all subscriptions on a topic. 5,000
Number of topics or queues per namespace Namespace Subsequent requests for creation of a new topic or queue on the namespace are rejected. As a result, if configured through the Azure portal, an error message is generated. If called from the management API, an exception is received by the calling code. 10,000 for the Basic or Standard tier. The total number of topics and queues in a namespace must be less than or equal to 10,000.

For the Premium tier, 1,000 per messaging unit (MU). Maximum limit is 4,000.
Number of partitioned topics or queues per namespace Namespace Subsequent requests for creation of a new partitioned topic or queue on the namespace are rejected. As a result, if configured through the Azure portal, an error message is generated. If called from the management API, the exception QuotaExceededException is received by the calling code. Basic and Standard tiers: 100.

Partitioned entities aren't supported in the Premium tier.

Each partitioned queue or topic counts toward the quota of 1,000 entities per namespace.
Maximum size of any messaging entity path: queue or topic Entity - 260 characters.
Maximum size of any messaging entity name: namespace, subscription, or subscription rule Entity - 50 characters.
Maximum size of a message ID Entity - 128
Maximum size of a message session ID Entity - 128
Message size for a queue, topic, or subscription entity Entity Incoming messages that exceed these quotas are rejected, and an exception is received by the calling code. Maximum message size: 256 KB for Standard tier, 1 MB for Premium tier.

Due to system overhead, this limit is less than these values.

Maximum header size: 64 KB.

Maximum number of header properties in property bag: byte/int.MaxValue.

Maximum size of property in property bag: No explicit limit. Limited by maximum header size.
Message property size for a queue, topic, or subscription entity Entity The exception SerializationException is generated. Maximum message property size for each property is 32,000. Cumulative size of all properties can't exceed 64,000. This limit applies to the entire header of the BrokeredMessage, which has both user properties and system properties, such as SequenceNumber, Label, and MessageId.
Number of subscriptions per topic Entity Subsequent requests for creating additional subscriptions for the topic are rejected. As a result, if configured through the portal, an error message is shown. If called from the management API, an exception is received by the calling code. 2,000 per-topic for the Basic or Standard tier.
Number of SQL filters per topic Entity Subsequent requests for creation of additional filters on the topic are rejected, and an exception is received by the calling code. 2,000
Number of correlation filters per topic Entity Subsequent requests for creation of additional filters on the topic are rejected, and an exception is received by the calling code. 100,000
Size of SQL filters or actions Namespace Subsequent requests for creation of additional filters are rejected, and an exception is received by the calling code. Maximum length of filter condition string: 1,024 (1 K).

Maximum length of rule action string: 1,024 (1 K).

Maximum number of expressions per rule action: 32.
Number of SharedAccessAuthorizationRule rules per namespace, queue, or topic Entity, namespace Subsequent requests for creation of additional rules are rejected, and an exception is received by the calling code. Maximum number of rules: 12.

Rules that are configured on a Service Bus namespace apply to all queues and topics in that namespace.
Number of messages per transaction Transaction Additional incoming messages are rejected, and an exception stating "Cannot send more than 100 messages in a single transaction" is received by the calling code. 100

For both Send() and SendAsync() operations.

IoT Hub limits

The following table lists the limits associated with the different service tiers S1, S2, S3, and F1. For information about the cost of each unit in each tier, see Azure IoT Hub pricing.

Resource S1 Standard S2 Standard S3 Standard F1 Free
Messages/day 400,000 6,000,000 300,000,000 8,000
Maximum units 200 200 10 1

Note

If you anticipate using more than 200 units with an S1 or S2 tier hub or 10 units with an S3 tier hub, contact Microsoft Support.

The following table lists the limits that apply to IoT Hub resources.

Resource Limit
Maximum paid IoT hubs per Azure subscription 50
Maximum free IoT hubs per Azure subscription 1
Maximum number of characters in a device ID 128
Maximum number of device identities
returned in a single call
1,000
IoT Hub message maximum retention for device-to-cloud messages 7 days
Maximum size of device-to-cloud message 256 KB
Maximum size of device-to-cloud batch AMQP and HTTP: 256 KB for the entire batch
MQTT: 256 KB for each message
Maximum messages in device-to-cloud batch 500
Maximum size of cloud-to-device message 64 KB
Maximum TTL for cloud-to-device messages 2 days
Maximum delivery count for cloud-to-device
messages
100
Maximum delivery count for feedback messages
in response to a cloud-to-device message
100
Maximum TTL for feedback messages in
response to a cloud-to-device message
2 days
Maximum size of device twin
(tags, reported properties, and desired properties)
8 KB
Maximum size of device twin string value 4 KB
Maximum depth of object in device twin 5
Maximum size of direct method payload 128 KB
Job history maximum retention 30 days
Maximum concurrent jobs 10 (for S3), 5 for (S2), 1 (for S1)
Maximum additional endpoints 10 (for S1, S2, and S3)
Maximum message routing rules 100 (for S1, S2, and S3)
Maximum number of concurrently connected device streams 50 (for S1, S2, S3, and F1 only)
Maximum device stream data transfer 300 MB per day (for S1, S2, S3, and F1 only)

Note

If you need more than 50 paid IoT hubs in an Azure subscription, contact Microsoft Support.

Note

Currently, the maximum number of devices you can connect to a single IoT hub is 1,000,000. If you want to increase this limit, contact Microsoft Support.

IoT Hub throttles requests when the following quotas are exceeded.

Throttle Per-hub value
Identity registry operations
(create, retrieve, list, update, and delete),
individual or bulk import/export
83.33/sec/unit (5,000/min/unit) (for S3).
1.67/sec/unit (100/min/unit) (for S1 and S2).
Device connections 6,000/sec/unit (for S3), 120/sec/unit (for S2), 12/sec/unit (for S1).
Minimum of 100/sec.
Device-to-cloud sends 6,000/sec/unit (for S3), 120/sec/unit (for S2), 12/sec/unit (for S1).
Minimum of 100/sec.
Cloud-to-device sends 83.33/sec/unit (5,000/min/unit) (for S3), 1.67/sec/unit (100/min/unit) (for S1 and S2).
Cloud-to-device receives 833.33/sec/unit (50,000/min/unit) (for S3), 16.67/sec/unit (1,000/min/unit) (for S1 and S2).
File upload operations 83.33 file upload notifications/sec/unit (5,000/min/unit) (for S3), 1.67 file upload notifications/sec/unit (100/min/unit) (for S1 and S2).
10,000 SAS URIs can be out for an Azure Storage account at one time.
10 SAS URIs/device can be out at one time.
Direct methods 24 MB/sec/unit (for S3), 480 KB/sec/unit (for S2), 160 KB/sec/unit (for S1).
Based on 8-KB throttling meter size.
Device twin reads 500/sec/unit (for S3), Maximum of 100/sec or 10/sec/unit (for S2), 100/sec (for S1)
Device twin updates 250/sec/unit (for S3), Maximum of 50/sec or 5/sec/unit (for S2), 50/sec (for S1)
Jobs operations
(create, update, list, and delete)
83.33/sec/unit (5,000/min/unit) (for S3), 1.67/sec/unit (100/min/unit) (for S2), 1.67/sec/unit (100/min/unit) (for S1).
Jobs per-device operation throughput 50/sec/unit (for S3), maximum of 10/sec or 1/sec/unit (for S2), 10/sec (for S1).
Device stream initiation rate 5 new streams/sec (for S1, S2, S3, and F1 only).

IoT Hub Device Provisioning Service limits

The following table lists the limits that apply to Azure IoT Hub Device Provisioning Service resources.

Resource Limit
Maximum device provisioning services per Azure subscription 10
Maximum number of enrollments 1,000,000
Maximum number of registrations 1,000,000
Maximum number of enrollment groups 100
Maximum number of CAs 25
Maximum number of linked IoT hubs 10
Maximum size of message 96 KB

Note

To increase the number of instances in your subscription, contact Microsoft Support.

Note

To increase the number of enrollments and registrations on your provisioning service, contact Microsoft Support.

The Device Provisioning Service throttles requests when the following quotas are exceeded.

Throttle Per-unit value
Operations 200/min/service
Device registrations 200/min/service
Device polling operation 5/10 sec/device

Data Factory limits

Azure Data Factory is a multitenant service that has the following default limits in place to make sure customer subscriptions are protected from each other's workloads. To raise the limits up to the maximum for your subscription, contact support.

Version 2

Resource Default limit Maximum limit
Data factories in an Azure subscription 50 Contact support.
Total number of entities, such as pipelines, data sets, triggers, linked services, and integration runtimes, within a data factory 5,000 Contact support.
Total CPU cores for Azure-SSIS Integration Runtimes under one subscription 256 Contact support.
Concurrent pipeline runs per data factory that's shared among all pipelines in the factory 10,000 Contact support.
Concurrent External activity runs per subscription per Azure Integration Runtime region
External activities are managed on integration runtime but execute on linked services, including Databricks, stored procedure, HDInsights, and others.
3000 Contact support.
Concurrent Pipeline activity runs per subscription per Azure Integration Runtime region
Pipeline activities execute on integration runtime, including Lookup, GetMetadata, and Delete.
1000 Contact support.
Concurrent authoring operations per subscription per Azure Integration Runtime region
Including test connection, browse folder list and table list, preview data.
200 Contact support.
Concurrent Data Integration Units1 consumption per subscription per Azure Integration Runtime region Region group 12: 6000
Region group 22: 3000
Region group 32: 1500
Contact support.
Maximum activities per pipeline, which includes inner activities for containers 40 40
Maximum number of linked integration runtimes that can be created against a single self-hosted integration runtime 100 Contact support.
Maximum parameters per pipeline 50 50
ForEach items 100,000 100,000
ForEach parallelism 20 50
Characters per expression 8,192 8,192
Minimum tumbling window trigger interval 15 min 15 min
Maximum timeout for pipeline activity runs 7 days 7 days
Bytes per object for pipeline objects3 200 KB 200 KB
Bytes per object for dataset and linked service objects3 100 KB 2,000 KB
Data Integration Units1 per copy activity run 256 Contact support.
Write API calls 1,200/h

This limit is imposed by Azure Resource Manager, not Azure Data Factory.
Contact support.
Read API calls 12,500/h

This limit is imposed by Azure Resource Manager, not Azure Data Factory.
Contact support.
Monitoring queries per minute 1,000 Contact support.
Entity CRUD operations per minute 50 Contact support.

1 The data integration unit (DIU) is used in a cloud-to-cloud copy operation, learn more from Data integration units (version 2). For information on billing, see Azure Data Factory pricing.

2 Azure Integration Runtime is globally available to ensure data compliance, efficiency, and reduced network egress costs.

Region group Regions
Region group 1 Central US, East US, East US2, North Europe, West Europe, West US, West US 2
Region group 2 Australia East, Australia Southeast, Brazil South, Central India, Japan East, Northcentral US, Southcentral US, Southeast Asia, West Central US
Region group 3 Canada Central, East Asia, France Central, Korea Central, UK South

3 Pipeline, data set, and linked service objects represent a logical grouping of your workload. Limits for these objects don't relate to the amount of data you can move and process with Azure Data Factory. Data Factory is designed to scale to handle petabytes of data.

Version 1

Resource Default limit Maximum limit
Data factories in an Azure subscription 50 Contact support.
Pipelines within a data factory 2,500 Contact support.
Data sets within a data factory 5,000 Contact support.
Concurrent slices per data set 10 10
Bytes per object for pipeline objects1 200 KB 200 KB
Bytes per object for data set and linked service objects1 100 KB 2,000 KB
Azure HDInsight on-demand cluster cores within a subscription2 60 Contact support.
Cloud data movement units per copy activity run3 32 Contact support.
Retry count for pipeline activity runs 1,000 MaxInt (32 bit)

1 Pipeline, data set, and linked service objects represent a logical grouping of your workload. Limits for these objects don't relate to the amount of data you can move and process with Azure Data Factory. Data Factory is designed to scale to handle petabytes of data.

2 On-demand HDInsight cores are allocated out of the subscription that contains the data factory. As a result, the previous limit is the Data Factory-enforced core limit for on-demand HDInsight cores. It's different from the core limit that's associated with your Azure subscription.

3 The cloud data movement unit (DMU) for version 1 is used in a cloud-to-cloud copy operation, learn more from Cloud data movement units (version 1). For information on billing, see Azure Data Factory pricing.

Resource Default lower limit Minimum limit
Scheduling interval 15 minutes 15 minutes
Interval between retry attempts 1 second 1 second
Retry timeout value 1 second 1 second

Web service call limits

Azure Resource Manager has limits for API calls. You can make API calls at a rate within the Azure Resource Manager API limits.

Data Lake Analytics limits

Azure Data Lake Analytics makes the complex task of managing distributed infrastructure and complex code easy. It dynamically provisions resources, and you can use it to do analytics on exabytes of data. When the job completes, it winds down resources automatically. You pay only for the processing power that was used. As you increase or decrease the size of data stored or the amount of compute used, you don’t have to rewrite code. To raise the default limits for your subscription, contact support.

Resource Default limit Comments
Maximum number of concurrent jobs 20
Maximum number of analytics units (AUs) per account 250 Use any combination of up to a maximum of 250 AUs across 20 jobs. To increase this limit, contact Microsoft Support.
Maximum script size for job submission 3 MB
Maximum number of Data Lake Analytics accounts per region per subscription 5 To increase this limit, contact Microsoft Support.

Data Lake Store limits

Azure Data Lake Storage Gen1 is an enterprise-wide hyper-scale repository for big data analytic workloads. You can use Data Lake Storage Gen1 to capture data of any size, type, and ingestion speed in one single place for operational and exploratory analytics. There's no limit to the amount of data you can store in a Data Lake Storage Gen1 account.

Resource Default limit Comments
Maximum number of Data Lake Storage Gen1 accounts, per subscription, per region 10 To request an increase for this limit, contact support.
Maximum number of access ACLs, per file or folder 32 This is a hard limit. Use groups to manage access with fewer entries.
Maximum number of default ACLs, per file or folder 32 This is a hard limit. Use groups to manage access with fewer entries.

Database Migration Service Limits

Azure Database Migration Service is a fully managed service designed to enable seamless migrations from multiple database sources to Azure data platforms with minimal downtime.

Resource Default limit Comments
Maximum number of services per subscription, per region 2 To request an increase for this limit, contact support.

Stream Analytics limits


Limit identifier Limit Comments
Maximum number of streaming units per subscription per region 500 To request an increase in streaming units for your subscription beyond 500, contact Microsoft Support.
Maximum number of inputs per job 60 There's a hard limit of 60 inputs per Azure Stream Analytics job.
Maximum number of outputs per job 60 There's a hard limit of 60 outputs per Stream Analytics job.
Maximum number of functions per job 60 There's a hard limit of 60 functions per Stream Analytics job.
Maximum number of streaming units per job 192 There's a hard limit of 192 streaming units per Stream Analytics job.
Maximum number of jobs per region 1,500 Each subscription can have up to 1,500 jobs per geographical region.
Reference data blob MB 300 Reference data blobs can't be larger than 300 MB each.

Active Directory limits

Here are the usage constraints and other service limits for the Azure Active Directory (Azure AD) service.

Category Limits
Directories A single user can belong to a maximum of 500 Azure AD directories as a member or a guest.
A single user can create a maximum of 20 directories.
Domains You can add no more than 900 managed domain names. If you set up all of your domains for federation with on-premises Active Directory, you can add no more than 450 domain names in each directory.
Objects
  • A maximum of 50,000 objects can be created in a single directory by users of the Free edition of Azure Active Directory by default. If you have at least one verified domain, the default directory service quota in Azure AD is extended to 300,000 objects.
  • A non-admin user can create no more than 250 objects. Both active objects and deleted objects that are available to restore count toward this quota. Only deleted objects that were deleted fewer than 30 days ago are available to restore. Deleted objects that are no longer available to restore count toward this quota at a value of one-quarter for 30 days. Perhaps assign an administrator role to non-admin users who are likely to repeatedly exceed this quota in the course of their regular duties.
Schema extensions
  • String-type extensions can have a maximum of 256 characters.
  • Binary-type extensions are limited to 256 bytes.
  • Only 100 extension values, across all types and all applications, can be written to any single object.
  • Only User, Group, TenantDetail, Device, Application, and ServicePrincipal entities can be extended with string-type or binary-type single-valued attributes.
  • Schema extensions are available only in the Graph API version 1.21 preview. The application must be granted write access to register an extension.
Applications A maximum of 100 users can be owners of a single application.
Groups
  • A maximum of 100 users can be owners of a single group.
  • Any number of objects can be members of a single group.
  • A user can be a member of any number of groups.
  • The number of members in a group that you can synchronize from your on-premises Active Directory to Azure Active Directory by using Azure AD Connect is limited to 50,000 members.
Application Proxy
  • A maximum of 500 transactions per second per App Proxy application
  • A maximum of 750 transactions per second for the tenant

A transaction is defined as a single http request and response for a unique resource. When throttled, clients will receive a 429 response (too many requests).
Access Panel
  • There's no limit to the number of applications that can be seen in the Access Panel per user. This applies to users assigned licenses for Azure AD Premium or the Enterprise Mobility Suite.
  • A maximum of 10 app tiles can be seen in the Access Panel for each user. This limit applies to users who are assigned licenses for Azure AD Free license plan. Examples of app tiles include Box, Salesforce, or Dropbox. This limit doesn't apply to administrator accounts.
Reports A maximum of 1,000 rows can be viewed or downloaded in any report. Any additional data is truncated.
Administrative units An object can be a member of no more than 30 administrative units.
Admin roles and permissions
  • A group cannot be added as an owner.
  • A group cannot be assigned to a role.
  • Users’ ability to read other users’ directory information cannot be restricted outside of the tenant-wide switch to disable all non-admin users’ access to all directory information (not recommended). More information on default permissions here.
  • It may take up to 15 minutes or signing out/signing in before admin role membership additions and revocations take effect.

Event Grid limits

The following limits apply to Azure Event Grid system topics and custom topics, not event domains.

Resource Limit
Custom topics per Azure subscription 100
Event subscriptions per topic 500
Publish rate for a custom topic (ingress) 5,000 events per second per topic
Publish requests 250 per second
Event size Support for 64 KB in General Availability (GA). Support for 1 MB is currently in preview.

The following limits apply to event domains only.

Resource Limit
Topics per event domain 1,000 during public preview
Event subscriptions per topic within a domain 50 during public preview
Domain scope event subscriptions 50 during public preview
Publish rate for an event domain (ingress) 5,000 events per second during public preview
Publish requests 250 per second

Azure Maps limits

The following table shows the usage limit for the Azure Maps S0 pricing tier. Usage limit depends on the pricing tier.

Resource S0 pricing tier limit
Maximum request rate per subscription 50 requests per second

The following table shows the data size limit for Azure Maps. The Azure Maps data service is available only at the S1 pricing tier.

Resource Limit
Maximum size of data 50 MB

For more information on the Azure Maps pricing tiers, see Azure Maps pricing.

Azure Policy limits

There's a maximum count for each object type for Azure Policy. An entry of Scope means either the subscription or the management group.

Where What Maximum count
Scope Policy definitions 500
Scope Initiative definitions 100
Tenant Initiative definitions 1,000
Scope Policy or initiative assignments 100
Policy definition Parameters 20
Initiative definition Policies 100
Initiative definition Parameters 100
Policy or initiative assignments Exclusions (notScopes) 400
Policy rule Nested conditionals 512

StorSimple System limits

Limit identifier Limit Comments
Maximum number of storage account credentials 64
Maximum number of volume containers 64
Maximum number of volumes 255
Maximum number of schedules per bandwidth template 168 A schedule for every hour, every day of the week.
Maximum size of a tiered volume on physical devices 64 TB for StorSimple 8100 and StorSimple 8600 StorSimple 8100 and StorSimple 8600 are physical devices.
Maximum size of a tiered volume on virtual devices in Azure 30 TB for StorSimple 8010
64 TB for StorSimple 8020
StorSimple 8010 and StorSimple 8020 are virtual devices in Azure that use Standard storage and Premium storage, respectively.
Maximum size of a locally pinned volume on physical devices 9 TB for StorSimple 8100
24 TB for StorSimple 8600
StorSimple 8100 and StorSimple 8600 are physical devices.
Maximum number of iSCSI connections 512
Maximum number of iSCSI connections from initiators 512
Maximum number of access control records per device 64
Maximum number of volumes per backup policy 24
Maximum number of backups retained per backup policy 64
Maximum number of schedules per backup policy 10
Maximum number of snapshots of any type that can be retained per volume 256 This amount includes local snapshots and cloud snapshots.
Maximum number of snapshots that can be present in any device 10,000
Maximum number of volumes that can be processed in parallel for backup, restore, or clone 16
  • If there are more than 16 volumes, they're processed sequentially as processing slots become available.
  • New backups of a cloned or a restored tiered volume can't occur until the operation is finished. For a local volume, backups are allowed after the volume is online.
Restore and clone recover time for tiered volumes <2 minutes
  • The volume is made available within 2 minutes of a restore or clone operation, regardless of the volume size.
  • The volume performance might initially be slower than normal as most of the data and metadata still resides in the cloud. Performance might increase as data flows from the cloud to the StorSimple device.
  • The total time to download metadata depends on the allocated volume size. Metadata is automatically brought into the device in the background at the rate of 5 minutes per TB of allocated volume data. This rate might be affected by Internet bandwidth to the cloud.
  • The restore or clone operation is complete when all the metadata is on the device.
  • Backup operations can't be performed until the restore or clone operation is fully complete.
Restore recover time for locally pinned volumes <2 minutes
  • The volume is made available within 2 minutes of the restore operation, regardless of the volume size.
  • The volume performance might initially be slower than normal as most of the data and metadata still resides in the cloud. Performance might increase as data flows from the cloud to the StorSimple device.
  • The total time to download metadata depends on the allocated volume size. Metadata is automatically brought into the device in the background at the rate of 5 minutes per TB of allocated volume data. This rate might be affected by Internet bandwidth to the cloud.
  • Unlike tiered volumes, if there are locally pinned volumes, the volume data is also downloaded locally on the device. The restore operation is complete when all the volume data has been brought to the device.
  • The restore operations might be long and the total time to complete the restore will depend on the size of the provisioned local volume, your Internet bandwidth, and the existing data on the device. Backup operations on the locally pinned volume are allowed while the restore operation is in progress.
Thin-restore availability Last failover
Maximum client read/write throughput, when served from the SSD tier* 920/720 MB/sec with a single 10-gigabit Ethernet network interface Up to two times with MPIO and two network interfaces.
Maximum client read/write throughput, when served from the HDD tier* 120/250 MB/sec
Maximum client read/write throughput, when served from the cloud tier* 11/41 MB/sec Read throughput depends on clients generating and maintaining sufficient I/O queue depth.

*Maximum throughput per I/O type was measured with 100 percent read and 100 percent write scenarios. Actual throughput might be lower and depends on I/O mix and network conditions.

Backup limits

The following limits apply to Azure Backup.

Limit Default
Servers or machines that can be registered in a vault. Windows Server/Windows Client/System Center Data Protection Manager: 50.

IaaS VMs: 1,000.
Size of a data source in vault storage. 54,400-GB maximum. The limit doesn't apply to IaaS VM backup.
Backup vaults in an Azure subscription. 500 vaults per region.
Schedule daily backups. Windows Server/Client: Three a day.
System Center DPM: Two a day.
IaaS VMs: Once a day.
Data disks attached to an Azure VM for backup. 16
Individual data disk attached to Azure VM for backup. 4,095 GB

Azure SignalR Service limits

Resource Default limit Maximum limit
Azure SignalR Service units per instance for Free tier 1 1
Azure SignalR Service units per instance for Standard tier 100 100
Azure SignalR Service units per subscription per region for Free tier 5 5
Total Azure SignalR Service unit counts per subscription per region 150 Unlimited
Connections per unit per day for Free tier 20 20
Connections per unit per day for Standard tier 1,000 1,000
Included messages per unit per day for Free tier 20,000 20,000
Included messages per unit per day for Standard tier 1,000,000 1,000,000

To request an update to your subscription's default limits, open a support ticket.

Site Recovery limits

The following limits apply to Azure Site Recovery.

Limit identifier Default limit
Number of vaults per subscription 500
Number of servers per Azure vault 250
Number of protection groups per Azure vault No limit
Number of recovery plans per Azure vault No limit
Number of servers per protection group No limit
Number of servers per recovery plan 50

API Management limits

Resource Limit
Maximum number of scale units 10 per region1
Cache size 5 GB per unit2
Concurrent back-end connections3 per HTTP authority 2,048 per unit4
Maximum cached response size 2 MB
Maximum policy document size 256 KB5
Maximum custom gateway domains per service instance6 20
Maximum number of CA certificates per service instance 10
Maximum number of service instances per subscription7 20
Maximum number of subscriptions per service instance7 500
Maximum number of client certificates per service instance7 50
Maximum number of APIs per service instance7 50
Maximum number of API operations per service instance7 1,000
Maximum total request duration7 30 seconds
Maximum buffered payload size7 2 MB

1Scaling limits depend on the pricing tier. To see the pricing tiers and their scaling limits, see API Management pricing.
2Per unit cache size depends on the pricing tier. To see the pricing tiers and their scaling limits, see API Management pricing.
3Connections are pooled and reused unless explicitly closed by the back end.
4This limit is per unit of the Basic, Standard, and Premium tiers. The Developer tier is limited to 1,024. This limit doesn't apply to the Consumption tier.
5This limit applies to the Basic, Standard, and Premium tiers. In the Consumption tier, policy document size is limited to 4 KB.
6This resource is available in the Premium tier only.
7This resource applies to the Consumption tier only.

Azure Cache for Redis limits

Resource Limit
Cache size 530 GB
Databases 64
Maximum connected clients 40,000
Azure Cache for Redis replicas, for high availability 1
Shards in a premium cache with clustering 10

Azure Cache for Redis limits and sizes are different for each pricing tier. To see the pricing tiers and their associated sizes, see Azure Cache for Redis pricing.

For more information on Azure Cache for Redis configuration limits, see Default Redis server configuration.

Because configuration and management of Azure Cache for Redis instances is done by Microsoft, not all Redis commands are supported in Azure Cache for Redis. For more information, see Redis commands not supported in Azure Cache for Redis.

Key Vault limits

Key transactions (maximum transactions allowed in 10 seconds, per vault per region1):

Key type HSM key
CREATE key
HSM key
All other transactions
Software key
CREATE key
Software key
All other transactions
RSA 2,048-bit 5 1,000 10 2,000
RSA 3,072-bit 5 250 10 500
RSA 4,096-bit 5 125 10 250
ECC P-256 5 1,000 10 2,000
ECC P-384 5 1,000 10 2,000
ECC P-521 5 1,000 10 2,000
ECC SECP256K1 5 1,000 10 2,000

Note

In the previous table, we see that for RSA 2,048-bit software keys, 2,000 GET transactions per 10 seconds are allowed. For RSA 2,048-bit HSM-keys, 1,000 GET transactions per 10 seconds are allowed.

The throttling thresholds are weighted, and enforcement is on their sum. For example, as shown in the previous table, when you perform GET operations on RSA HSM-keys, it's eight times more expensive to use 4,096-bit keys compared to 2,048-bit keys. That's because 1,000/125 = 8.

In a given 10-second interval, an Azure Key Vault client can do only one of the following operations before it encounters a 429 throttling HTTP status code:

  • 2,000 RSA 2,048-bit software-key GET transactions
  • 1,000 RSA 2,048-bit HSM-key GET transactions
  • 125 RSA 4,096-bit HSM-key GET transactions
  • 124 RSA 4,096-bit HSM-key GET transactions and 8 RSA 2,048-bit HSM-key GET transactions

Secrets, managed storage account keys, and vault transactions:

Transactions type Maximum transactions allowed in 10 seconds, per vault per region1
All transactions 2,000

For information on how to handle throttling when these limits are exceeded, see Azure Key Vault throttling guidance.

1 A subscription-wide limit for all transaction types is five times per key vault limit. For example, HSM-other transactions per subscription are limited to 5,000 transactions in 10 seconds per subscription.

Multi-Factor Authentication limits

Resource Default limit Maximum limit
Maximum number of trusted IP addresses or ranges per subscription 0 50
Remember my devices, number of days 14 60
Maximum number of app passwords 0 No limit
Allow X attempts during MFA call 1 99
Two-way text message timeout seconds 60 600
Default one-time bypass seconds 300 1,800
Lock user account after X consecutive MFA denials Not set 99
Reset account lockout counter after X minutes Not set 9,999
Unlock account after X minutes Not set 9,999

Automation limits

Process automation

Resource Maximum limit Notes
Maximum number of new jobs that can be submitted every 30 seconds per Azure Automation account (nonscheduled jobs) 100 When this limit is reached, the subsequent requests to create a job fail. The client receives an error response.
Maximum number of concurrent running jobs at the same instance of time per Automation account (nonscheduled jobs) 200 When this limit is reached, the subsequent requests to create a job fail. The client receives an error response.
Maximum storage size of job metadata for a 30-day rolling period 10 GB (approximately 4 million jobs) When this limit is reached, the subsequent requests to create a job fail.
Maximum job stream limit 1MB A single stream cannot be larger than 1 MB.
Maximum number of modules that can be imported every 30 seconds per Automation account 5
Maximum size of a module 100 MB
Job run time, Free tier 500 minutes per subscription per calendar month
Maximum amount of disk space allowed per sandbox1 1 GB Applies to Azure sandboxes only.
Maximum amount of memory given to a sandbox1 400 MB Applies to Azure sandboxes only.
Maximum number of network sockets allowed per sandbox1 1,000 Applies to Azure sandboxes only.
Maximum runtime allowed per runbook1 3 hours Applies to Azure sandboxes only.
Maximum number of Automation accounts in a subscription No limit
Maximum number of Hybrid Worker Groups per Automation Account 4,000
Maximum number of concurrent jobs that can be run on a single Hybrid Runbook Worker 50
Maximum runbook job parameter size 512 kilobits
Maximum runbook parameters 50 If you reach the 50-parameter limit, you can pass a JSON or XML string to a parameter and parse it with the runbook.
Maximum webhook payload size 512 kilobits
Maximum days that job data is retained 30 days
Maximum PowerShell workflow state size 5 MB Applies to PowerShell workflow runbooks when checkpointing workflow.

1A sandbox is a shared environment that can be used by multiple jobs. Jobs that use the same sandbox are bound by the resource limitations of the sandbox.

Change Tracking and Inventory

The following table shows the tracked item limits per machine for change tracking.

Resource Limit Notes
File 500
Registry 250
Windows software 250 Doesn't include software updates.
Linux packages 1,250
Services 250
Daemon 250

Update Management

The following table shows the limits for Update Management.

Resource Limit Notes
Number of machines per update deployment 1000

Identity Manager limits

Category Limit
User-assigned managed identities
  • When you create user-assigned managed identities, only alphanumeric characters (0-9, a-z, and A-Z) and the hyphen (-) are supported. For the assignment to a virtual machine or virtual machine scale set to work properly, the name is limited to 24 characters.
  • If you use the managed identity virtual machine extension, the supported limit is 32 user-assigned managed identities. Without the managed identity virtual machine extension, the supported limit is 512 user-assigned identities.

Role-based access control limits

Resource Limit
Role assignments for Azure resources per Azure subscription 2,000
Role assignments for Azure resources per management group 500
Custom roles for Azure resources per tenant 5,000
Custom roles for Azure resources per tenant
(specialized clouds, such as Azure Government, Azure Germany, and Azure China 21Vianet)
2,000

SQL Database limits

For SQL Database limits, see SQL Database resource limits for single databases, SQL Database resource limits for elastic pools and pooled databases, and SQL Database resource limits for managed instances.

SQL Data Warehouse limits

For SQL Data Warehouse limits, see SQL Data Warehouse resource limits.

See also