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 of the platform.

Please visit Azure Pricing Overview to learn more about Azure pricing. There, you can estimate your costs using the Pricing Calculator or by visiting the pricing details page for a 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 is no Maximum Limit column, then the resource doesn't have adjustable limits.

Free Trial subscriptions are not 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 Azure Free Trial to Pay-As-You-Go and Free Trial subscription FAQ.

Limits and the Azure Resource Manager

It is now possible to combine multiple Azure resources in to a single Azure Resource Group. When using Resource Groups, limits that once were global become managed at a regional level with the Azure Resource Manager. For more information about Azure Resource Groups, see Azure Resource Manager overview.

In the limits below, a new table has been added to reflect any differences in limits when using the Azure Resource Manager. For example, there is a Subscription Limits table and a Subscription Limits - Azure Resource Manager table. When a limit applies to both scenarios, it is only shown in the first table. Unless otherwise indicated, limits are global across all regions.

Note

It is important to emphasize that quotas for resources in Azure Resource Groups are per-region accessible by your subscription, and are not per-subscription, as the service management quotas are. Let's use vCPU quotas as an example. If you need to request a quota increase with support for vCPUs, you need to decide how many vCPUs you want to use in which regions, and then make a specific request for Azure Resource Group vCPU quotas for the amounts and regions that you want. Therefore, if you need to use 30 vCPUs in West Europe to run your application there, you should specifically request 30 vCPUs in West Europe. But you will not have a vCPU quota increase in any other region -- only West Europe will have the 30-vCPU quota.

As a result, you may find it useful to consider deciding what your Azure Resource Group quotas need to be for your workload in any one region, and request that amount in each region into which you are considering deployment. See troubleshooting deployment issues for more help discovering your current quotas for specific regions.

Service-specific limits

Subscription limits

Subscription limits - Azure Service Management (Classic Resources)

Resource Default Limit Maximum Limit
vCPUs per subscription 1 20 10,000
Co-administrators per subscription 200 200
Storage accounts per subscription 2 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

1Extra Small instances count as one vCPU towards 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 using the Azure Resource Manager and Azure Resource Groups. Limits that have not changed with the Azure Resource Manager are not listed below. Please refer to 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 10,000 1 per Region 10,000 per Region
VM total cores per subscription 201 per Region Contact support
VM per series (Dv2, F, etc.) cores per subscription 201 per Region Contact support
Co-administrators per subscription Unlimited Unlimited
Storage accounts per region per subscription 200 2002
Resource Groups per subscription 980 980
Availability Sets per subscription 2,000 per Region 2,000 per Region
Resource Manager API request size 4,194,304 bytes 4,194,304 bytes
Tags per subscription3 unlimited unlimited
Unique tag calculations per subscription3 10,000 10,000
Cloud services per subscription Not Applicable4 Not Applicable4
Affinity groups per subscription Not Applicable4 Not Applicable4
Subscription level deployments per location 800 800

1Default limits vary by offer Category Type, such as Free Trial, Pay-As-You-Go, and series, such as Dv2, F, G, etc.

2This includes both Standard and Premium storage accounts. If you require more than 200 storage accounts, make a request through Azure Support. The Azure Storage team will review your business case and may approve up to 250 storage accounts.

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

4These features are no longer required with Azure Resource Groups and the Azure Resource Manager.

Note

It is important to emphasize that virtual machine cores have a regional total limit as well as a regional per size series (Dv2, F, etc.) limit that 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 would be allowed to deploy 30 A1 VMs, or 30 D1 VMs, or a combination of the two not to exceed a total of 30 cores (for example, 10 A1 VMs and 20 D1 VMs).

Resource Group limits

Resource Default Limit Maximum Limit
Resources per resource group (per resource type) 800 Varies per resource type
Deployments per resource group in the deployment history 800 800
Resources per deployment 800 800
Management Locks (per unique scope) 20 20
Number of Tags (per resource or resource group) 15 15
Tag key length 512 512
Tag value length 256 256

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 1 MB 1 MB
Parameter file size 64 KB 64 KB

You can exceed some template limits by using a nested template. For more information, see Using linked templates when deploying 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.

If you reach the limit of 800 deployments per resource group, delete deployments from the history that are no longer needed. You can delete entries from the history with az group deployment delete for Azure CLI, or Remove-AzureRmResourceGroupDeployment in PowerShell. Deleting an entry from the deployment history does not affect the deploy resources.

Virtual Machines limits

Virtual Machine limits

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

1Virtual machines created in Service Management (instead of 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. See How to Set Up Endpoints to a Virtual Machine.

Virtual Machines limits - Azure Resource Manager

The following limits apply when using the Azure Resource Manager and Azure Resource Groups. Limits that have not changed with the Azure Resource Manager are not listed below. Please refer to 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. Although the number of certificates is unlimited for a subscription, there is still a 1 MB limit of certificates per deployment (which consists of either a single VM or an availability set).

Virtual Machine Scale Sets limits

Resource Default Limit Maximum Limit
Maximum number of VMs in a scale set 1000 1000
Maximum number of VMs based on a custom VM image in a scale set 600 600
Maximum number of scale sets in a region 2000 2000

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 creates per hour 3001
Container creates per 5 minutes 1001
Container deletes per hour 3001
Container deletes per 5 minutes 1001
Multiple containers per container group Linux only2
Azure Files volumes Linux only2
GitRepo volumes Linux only2
Secret volumes Linux only2

1 Create an Azure support request to request a limit increase.
2 Windows support for this feature is planned.

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
Max image layer size 20 GiB 20 GiB 50 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 (preview) N/A N/A Supported

1 The 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 Container Registry pricing.

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

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

4 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.

Kubernetes Service limits

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

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

Networking limits

ExpressRoute Limits

The following limits apply to ExpressRoute resources per subscription.

Resource Default/Max Limit
ExpressRoute circuits per subscription 10
ExpressRoute circuits per region per subscription (Azure Resource Manager) 10
Maximum number of routes for Azure private peering with ExpressRoute standard 4,000
Maximum number of routes for Azure private peering with ExpressRoute premium add-on 10,000
Maximum number of routes for Azure Microsoft peering with ExpressRoute standard 200
Maximum number of routes for Azure Microsoft peering with ExpressRoute premium add-on 200
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 table below

Number of Virtual Networks per ExpressRoute circuit

Circuit Size Number of VNet links for standard Number of VNet 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

Networking limits

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 50 100
Local network sites 20 contact support
DNS Servers per virtual network 20 20
Private IP Addresses per virtual network 4096 4096
Concurrent TCP or UDP flows per NIC of a virtual machine or role instance 500K 500K
Network Security Groups (NSG) 100 200
NSG rules per NSG 200 1000
User defined route tables 100 200
User defined routes per route table 100 400
Public IP addresses (dynamic) 5 contact support
Reserved public IP addresses 20 contact support
Public VIP per deployment 5 contact support
Private VIP (ILB) per deployment 1 1
Endpoint Access Control Lists (ACLs) 50 50

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 is no Maximum Limit column, then the resource doesn't have adjustable limits. If you have had these limits increased by support in the past and do not see updated limits as below, you can open an online customer support request at no charge

Resource Default limit
Virtual networks 1000
Subnets per virtual network 3000
Virtual network peerings per Virtual Network 100
DNS Servers per virtual network 20
Private IP Addresses per virtual network 65536
Private IP Addresses per network interface 256
Concurrent TCP or UDP flows per NIC of a virtual machine or role instance 500K
Network Interfaces (NIC) 65536
Network Security Groups (NSG) 5000
NSG rules per NSG 1000
IP addresses and ranges specified for source or destination in a security group 4000
Application security groups 3000
Application security groups per IP configuration, per NIC 20
IP configurations per application security group 4000
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 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 (Basic) 1000 contact support
Public IP addresses - static (Basic) 200 contact support
Public IP addresses - static (Standard) 200 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 limit
Load Balancers 1000
Rules per resource, Basic 250
Rules per resource, Standard 1500
Rules per IP configuration 299
Frontend IP configurations, Basic 200
Frontend IP configurations, Standard 600
Backend pool, Basic 100, single Availability Set
Backend pool, Standard 1000, single VNet
Backend resources per Load Balancer, Standard * 150
HA Ports, Standard 1 per internal frontend

** Up to 150 resources, any combination of standalone virtual machines, availability sets, and virtual machine scale sets.

Contact support in case you need to increase limits from default.

Application Gateway limits

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

Resource Default limit Note
Application Gateway 1000 per subscription
Frontend IP Configurations 2 1 public and 1 private
Frontend Ports 40
Backend Address Pools 40
Backend Servers per pool 1200
HTTP Listeners 40
HTTP load balancing rules 400 # of HTTP Listeners * n
Backend HTTP settings 40
Instances per gateway 75
SSL certificates 40 1 per HTTP Listeners
Authentication certificates 40
Request time out min 1 second
Request time out max 24 hrs
Number of sites 40 1 per HTTP Listeners
URL Maps per listener 1
Maximum path-based rules per URL map 100
Redirect configurations 40
Concurrent WebSocket Connections 5000
Maximum URL length 8000
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

Network Watcher limits

Resource Default limit Maximum Limit Note
Network Watcher 1 per region 1 per region Network Watcher resource is created to enable access to the service. Only 1 Network Watcher resource is required per subscription per region
Packet Capture sessions 100 per region 10,000 # of sessions only, not saved captures

Traffic Manager limits

Resource Default limit
Profiles per subscription 200 1
Endpoints per profile 200

1Contact support in case you need to increase these limits.

DNS limits

Resource Default limit
Zones per subscription 100 1
Record sets per zone 5000 1
Records per record set 20

1 Contact Azure Support in case you need to increase these limits.

Azure Firewall limits

Resource Default limit
Data processed 1000 TB/firewall/month 1
Rules 10k - all rule types combined
Global peering Not supported. You should have at least one firewall deployment per region.
Maximum ports in a single network rule 15
A range of ports (for example: 2 - 10) is counted as two.
Minimum AzureFirewallSubnet size /26

1 Contact Azure Support in case you need to increase these limits.

Azure Front Door Service limits

Resource Default limit
Front Door resources per subscription 100
Front-end hosts including custom domains per resource 100
Routing rules per resource 100
Backend pools per resource 50
Backends per backend 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

Timeout Values

Client to Front Door

  • Front Door has an idle TCP connection timeout of 61 seconds. #### Front Door to application backend
  • If the response is a chunked response, a 200 will be returned if / when the first chunk is received.
  • After the HTTP request is forwarded to the backend, Front Door will wait for 30 seconds for the first packet from backend, before returning a 503 error to the client.
  • After the first packet is received from the backend, Front Door waits for 30 seconds (idle timeout) before returning a 503 error to the client.
  • Front Door to backend TCP session timeout is 30 minutes.

Upload / download data limit

With Chunked Transfer Encoding (CTE) Without HTTP Chunking
Download There is no limit on the download size There is no limit on the download size
Upload No limit as long as each CTE upload is less than 28.6 MB The size can't be larger than 28.6 MB.

Storage limits

The following table describes default limits for Azure Storage. The ingress limit refers to all data (requests) being sent to a storage account. The egress limit refers to all data (responses) being received from a storage account.

Resource Default Limit
Number of storage accounts per region per subscription, including both standard and premium accounts 250
Max storage account capacity 2 PB for US and Europe, 500 TB for all other regions including UK
Max 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
Max ingress1 per storage account (US Regions) 10 Gbps if RA-GRS/GRS enabled, 20 Gbps for LRS/ZRS2
Max ingress1 per storage account (Non-US regions) 5 Gbps if RA-GRS/GRS enabled, 10 Gbps for LRS/ZRS2
Max egress for general-purpose v2 and Blob storage accounts (all regions) 50 Gbps
Max egress for general-purpose v1 storage accounts (US regions) 20 Gbps if RA-GRS/GRS enabled, 30 Gbps for LRS/ZRS 2
Max egress for general-purpose v1 storage accounts (Non-US regions) 10 Gbps if RA-GRS/GRS enabled, 15 Gbps for LRS/ZRS 2

1 Azure storage accounts support higher limits for ingress by request. To request an increase in account limits for ingress, contact Azure Support.

2Azure 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.

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. See Azure Storage Pricing for information on volume 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 additional details on storage account limits, see Azure Storage Scalability and Performance Targets.

Storage resource provider limits

The following limits apply only when performing management operations 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
Max size of single blob container Same as max storage account capacity
Max number of blocks in a block blob or append blob 50,000 blocks
Max size of a block in a block blob 100 MiB
Max size of a block blob 50,000 X 100 MiB (approx. 4.75 TiB)
Max size of a block in an append blob 4 MiB
Max size of an append blob 50,000 x 4 MiB (approx. 195 GiB)
Max size of a page blob 8 TiB
Max number of stored access policies per blob container 5
Target throughput for single blob Up to 60 MiB per second, or up to 500 requests per second

Azure Files limits

For additional details on Azure Files limits, see Azure Files scalability and performance targets.

Resource Standard file shares Premium file shares (preview)
Minimum size of a file share (no minimum; pay as you go) 100 GiB
Max size of a file share 5 TiB 5 TiB
Max size of a file in a file share 1 TiB 1 TiB
Max number of files in a file share No limit No limit
Max IOPS per share 1000 IOPS 5120 IOPS baseline
15,360 IOPS with burst
Max number of stored access policies per file share 5 5
Target throughput for single file share Up to 60 MiB/second Up to 612 MiB/sec (provisioned)
Maximum open handles per file 2,000 open handles 2,000 open handles
Maximum number of share snapshots 200 share snapshots 200 share snapshots

Azure File Sync limits

Resource Target Hard limit
Storage Sync Services per subscription 15 Storage Sync Services per region No
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 33-99 server endpoints Yes, but varies based on configuration (CPU, memory, volumes, file churn, file count, etc.)
Endpoint size 4 TiB No
File system objects (directories and files) per sync group 25 million objects No
Maximum number of file system objects (directories and files) in a directory 200,000 objects Yes
Maximum object (directories and files) name length 255 characters Yes
Maximum object (directories and files) security descriptor size 4 KiB Yes
File size 100 GiB No
Minimum file size for a file to be tiered 64 KiB Yes
Concurrent sync sessions V4 agent: Limit varies based on available system resources.
V3 agent: 2 active sync sessions per processor or maximum of 8 active sync sessions per server
Yes

Azure Queue storage limits

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

Azure Table storage limits

Resource Target
Max size of single table 500 TiB
Max size of a table entity 1 MiB
Max number of properties in a table entity 255 (including 3 system properties: PartitionKey, RowKey and Timestamp)
Max number of stored access policies per table 5
Maximum request rate per storage account 20,000 transactions per second (assuming 1 KiB entity size)
Target throughput for single table partition (1 KiB entities) Up to 2000 entities per second

Virtual machine disk limits

An Azure virtual machine supports attaching a number of data disks. This article describes scalability and performance targets for a VM's data disks. Use these targets to help decide 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 are not highly utilized at the same time, then the virtual machine can support a larger number of disks.

  • For Azure Managed Disks:
Resource Default Limit Maximum Limit
Standard Managed Disks 10,000 50,000
Standard SSD Managed Disks 10,000 50,000
Premium Managed Disks 10,000 50,000
Standard_LRS Snapshots 10,000 50,000
Standard_ZRS Snapshots 10,000 50,000
Managed Image 10,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 (20,000/300 IOPS per disk), and for a Standard Tier VM, it is about 40 (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.

See Virtual machine sizes for additional details.

Managed virtual machine disks

Standard managed virtual machine HDDs

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,095 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 managed virtual machine SSDs

Standard SSD Disk Type E10 E15 E20 E30 E40 E50 E60 * E70 * E80 *
Disk size in GiB 128 256 512 1,024 2,048 4,095 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
Throughput per disk Up to 60 MB/sec Up to 60 MB/sec Up to 60 MB/sec Up to 60 MB/sec Up to 60 MB/sec Up to 60 MB/sec Up to 60 MB/sec Up to 60 MB/sec Up to 300 MiB/sec

Premium managed virtual machine disks: per disk limits

Premium Disk Type P4 P6 P10 P15 P20 S30 P40 P50 P60 * P70 * P80 *
Disk size in GiB 32 64 128 256 512 1,024 2,048 4,095 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 12,500 Up to 15,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 480 MiB/sec Up to 750 MiB/sec Up to 750 MiB/sec

Premium managed virtual machine disks: per VM limits

Resource Default Limit
Max IOPS Per VM 80,000 IOPS with GS5 VM
Max 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 4095 GB 4095 GB
Max 8 KB IOPS per persistent disk 300 500
Max number of disks performing max 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
Max bandwidth per account (ingress + egress1) <=50 Gbps

1Ingress refers to all data (requests) being sent to a storage account. Egress refers to all data (responses) being 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 1024 GiB (1 TB) 2048 GiB (2 TB) 4095 GiB (4 TB)
Max IOPS per disk 500 2300 5000 7500 7500
Max throughput per disk 100 MB/s 150 MB/s 200 MB/s 250 MB/s 250 MB/s
Max number of disks per storage account 280 70 35 17 8

Premium unmanaged virtual machine disks: per VM limits

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

Cloud Services limits

Resource Default Limit Maximum Limit
Web/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 Cloud Service with Web/Worker roles can have two deployments, one for production and one for staging. Also note that this limit refers to the number of distinct roles (configuration) and not the number of instances per role (scaling).

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 App Service plan1 10 100 Unlimited2 Unlimited2 Unlimited2 Unlimited2
App Service plan 1 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 (max 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 min)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) 1024 MB per App Service plan 1024 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 max of 12 backups per day (manual + scheduled) Scheduled backups every hour, a max of 50 backups per day (manual + scheduled) Scheduled backups every hour, a max of 50 backups per day (manual + scheduled)
Auto Scale 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.9% 99.95% 99.95% 99.95%

1 Apps and storage quotas are per App Service plan unless noted otherwise.
2 The 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.
3 Dedicated instances can be of different sizes. See App Service Pricing for more details.
4 More allowed upon request.
5 The storage limit is the total content size across all apps in the same App Service plan.
6 These resources are constrained by physical resources on the dedicated instances (the instance size and the number of instances).
7 If you scale an app in the Basic tier to two instances, you have 350 concurrent connections for each of the two instances.
8 Run 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 is no predefined limit on the number of WebJobs that can run in an App Service instance, but there are practical limits that depend on what the application code is trying to do.
9 App Service Isolated SKUs have the ability to be internally load balanced (ILB) with Azure Load Balancer, which means 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.
10 The App Service Certificate quota limit per subscription can be increased via a support request to a maximum limit of 200.

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 16K. 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 8192 chars.
Request URL size The maximum size for a request URL is 2048 chars.
Header count The maximum header count is 50 headers.
Aggregate header size The maximum aggregate header size is 4096 chars.
Timeout The request timeout is static (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 2048 bytes.
Job history retention Job history is kept for up to 2 months or up to the last 1000 executions.
Completed and faulted job retention Completed and faulted jobs are kept for 60 days.

Batch limits

Resource Default Limit Maximum Limit
Batch accounts per region per subscription 1 - 3 50
Dedicated cores per Batch account 10 - 100 N/A1
Low-priority cores per Batch account 10 - 100 N/A2
Active jobs and job schedules3 per Batch account 100 - 300 10004
Pools per Batch account 20 - 100 5004

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.

1 The number of dedicated cores per Batch account can be increased, but the maximum number is unspecified. Contact Azure support to discuss increase options.

2 The number of low-priority cores per Batch account can be increased, but the maximum number is unspecified. Contact Azure support to discuss increase options.

3 Completed jobs and job schedules are not limited.

4 Contact Azure support if you want to request an increase beyond this limit.

Batch AI limits

Resource Default limit Maximum limit
Dedicated cores per region 10 - 24 N/A1
Low-priority cores per region 10 - 24 N/A2
Clusters per region 20 2003

Note

Default limits vary depending on the type of subscription you have.

1 The number of dedicated cores per region can be increased, but the maximum number is unspecified. Contact Azure support to discuss increase options.

2 The number of low-priority cores per region can be increased, but the maximum number is unspecified. Contact Azure support to discuss increase options.

3 Contact Azure support if you want to request an increase beyond this limit.

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 1000
Hybrid Connections per Unit 5 5 10 50 100
Hybrid Connection Data Transfer (GBs) per Unit 5 5 50 250 500
Number of connections using 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

Azure Cosmos DB is a global scale database in which throughput and storage can be scaled to handle whatever your application requires. If you have any questions about the scale Azure Cosmos DB provides, please send email to askcosmosdb@microsoft.com.

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.

Search limits

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

  • Free multi-tenant service, shared with other Azure subscribers, 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 (S1, S2, S3, 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 provisioned at a specific tier, 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 a SKU or tier for Azure Search.

Maximum service limits can be raised upon request. Contact Azure Support if you need more services within the same subscription.

Resource Free 1 Basic S1 S2 S3 S3 HD
Maximum services 1 12 12 6 6 6
Maximum scale in SU 2 N/A 3 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 (SU) 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 Basic 1 S1 S2 S3 S3 HD 2
Service Level Agreement (SLA) 3 No Yes Yes Yes Yes Yes
Storage per partition 50 MB 2 GB 25 GB 100 GB 200 GB 200 GB
Partitions per service N/A 1 12 12 12 3
Partition size N/A 2 GB 25 GB 100 GB 200 GB 200 GB
Replicas N/A 3 12 12 12 12

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

2 S3 HD has a hard limit of 3 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 (SLAs) 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) SLA. Three or more replicas are required for query and indexing (read-write) SLA. The number of partitions is not 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 are not fixed, you may ask for the quotas to be raised, by opening a support ticket. Do not create additional Azure Media Services accounts in an attempt to obtain higher limits.

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

1 If you change the type (for example, from S2 to S1,) the max RU limits are reset.

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

As of April 1, 2017, any Job record in your account older than 90 days will be automatically deleted, along with its associated Task records, even if the total number of records is below the maximum quota. If you need to archive the job/task information, you can use the code described here.

3 When making a request to list Job entities, a maximum of 1,000 jobs is returned per request. If you need to keep track of all submitted Jobs, you can use top/skip as described in OData system query options.

4 Locators are not 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 this section.

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

6 There is a limit of 1,000,000 policies for different AMS policies (for example, for Locator policy or ContentKeyAuthorizationPolicy).

Note

You should use the same policy ID if you are always using the same days / access permissions / etc. For information and an example, see this section.

7If you are uploading content to an Asset in Azure Media Services to process it with one of the media processors in the service (that is, encoders like Media Encoder Standard and Media Encoder Premium Workflow, or analysis engines like Face Detector), then you should be aware of the constraints on the maximum file sizes supported.

The maximum size supported for a single blob is currently up to 5 TB in Azure Blob Storage. However, additional limits apply in Azure Media Services based on the VM sizes that are used by the service. The following table shows the limits on each of the Media Reserved Units (S1, S2, S3.) If your source file is larger than the limits defined in the table, your encoding job will fail. If you are encoding 4K resolution sources of long duration, you are required to use S3 Media Reserved Units to achieve the performance needed. If you have 4K content that is larger than 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 325
S2 640
S3 260

CDN limits

Resource Default limit Maximum limit
CDN profiles 25 25
CDN endpoints per profile 10 25
Custom domains per endpoint 10 25

A CDN subscription can contain one or more CDN profiles and a CDN profile can contain one or more CDN endpoints. You may wish to use multiple profiles to organize your CDN endpoints by internet domain, web application, or some other criteria.

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

Mobile Services limits

TIER: FREE BASIC STANDARD
API Calls 500 K 1.5 M / unit 15 M / unit
Active Devices 500 Unlimited Unlimited
Scale N/A Up to 6 units Unlimited units
Push Notifications Notification Hubs Free Tier included, up to 1 M pushes Notification Hubs Basic Tier included, up to 10 M pushes Notification Hubs Standard Tier included, up to 10 M pushes
Real time messaging/
Web Sockets
Limited 350 / mobile service Unlimited
Offline synchronizations Limited Included Included
Scheduled jobs Limited Included Included
SQL Database (required)
Standard rates apply for additional capacity
20 MB included 20 MB included 20 MB included
CPU capacity 60 minutes / day Unlimited Unlimited
Outbound data transfer 165 MB per day (daily Rollover) Included Included

For additional details on these limits and for information on pricing, see Mobile Services Pricing.

Monitor limits

Resource Default Limit Maximum Limit
Autoscale Settings 100 per region per subscription same as default
Metric Alerts (classic) 100 active alert rules per subscription call support
Metric Alerts 100 active alert rules per subscription call support
Action Groups 2000 action groups per subscription call support

Notification Hub Service limits

TIER: FREE BASIC STANDARD
Included Pushes 1 Million 10 Million 10 Million
Active Devices 500 200,000 10 million
Tag quota per installation/registration 60 60 60

For additional details on these limits and for information on 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 - 1000
Number of event hubs per namespace Namespace Subsequent requests for creation of a new event hub will be rejected. 10
Number of partitions per event hub Entity - 32
Number of consumer groups per event hub Entity - 20
Number of AMQP connections per namespace Namespace Subsequent requests for additional connections will be rejected and an exception is received by the calling code. 5,000
Maximum size of Event Hubs event Entity - 256 KB
Maximum size of an event hub name Entity - 50 characters
Number of non-epoch receivers per consumer group Entity - 5
Maximum retention period of event data Entity - 1-7 days
Maximum throughput units Namespace Exceeding the throughput unit limit causes your data to be throttled and generates a ServerBusyException. You can request a larger number of throughput units for a Standard tier by filing 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 will be rejected. 12

Service Bus limits

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

Quota Name Scope Notes Value
Maximum number of basic / standard namespaces per Azure subscription Namespace Subsequent requests for additional basic / standard namespaces are rejected by the portal. 100
Maximum number of premium namespaces per Azure subscription Namespace Subsequent requests for additional premium namespaces are rejected by the portal. 10
Queue/topic size Entity Defined upon creation of the queue/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, as well as Standard with partitioning enabled, the maximum queue/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 do not count towards concurrent TCP connections. NetMessaging: 1,000

AMQP: 5,000
Number of concurrent receive requests on a queue/topic/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/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. 1000 (Basic/Standard tier). The total number of topics and queues in a namespace must be less than or equal to 1000.

For premium tier, 1000 per messaging unit(MU). Maximum limit is 4000.
Number of partitioned topics/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, a QuotaExceededException exception is received by the calling code. Basic and Standard Tiers - 100

Partitioned entities are not supported in the Premium tier.

Each partitioned queue or topic counts towards the quota of 1000 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 SessionID Entity - 128
Message size for a queue/topic/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 (Standard tier) / 1 MB (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/subscription entity Entity A SerializationException exception is generated. Maximum message property size for each property is 32 K. Cumulative size of all properties cannot exceed 64 K. This limit applies to the entire header of the BrokeredMessage, which has both user properties as well as system properties (such as SequenceNumber, Label, MessageId, and so on).
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. Standard Tier - Each subscription counts against the quota of 1000 entities (queues, topics and subscriptions) per namespace.

Premium Tier - 2,000
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/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: 1024 (1 K).

Maximum length of rule action string: 1024 (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, F1). For information about the cost of each unit in each tier, see 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 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
1000
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, S3)
Maximum message routing rules 100 (for S1, S2, S3)

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 500,000. If you want to increase this limit, contact Microsoft Support.

The IoT Hub service throttles requests when the following quotas are exceeded:

Throttle Per-hub value
Identity registry operations
(create, retrieve, list, update, delete),
individual or bulk import/export
83.33/sec/unit (5000/min/unit) (for S3)
1.67/sec/unit (100/min/unit) (for S1 and S2).
Device connections 6000/sec/unit (for S3), 120/sec/unit (for S2), 12/sec/unit (for S1).
Minimum of 100/sec.
Device-to-cloud sends 6000/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 (5000/min/unit) (for S3), 1.67/sec/unit (100/min/unit) (for S1 and S2).
Cloud-to-device receives 833.33/sec/unit (50000/min/unit) (for S3), 16.67/sec/unit (1000/min/unit) (for S1 and S2).
File upload operations 83.33 file upload notifications/sec/unit (5000/min/unit) (for S3), 1.67 file upload notifications/sec/unit (100/min/unit) (for S1 and S2).
10000 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 24MB/sec/unit (for S3), 480KB/sec/unit (for S2), 160KB/sec/unit (for S1)
Based on 8KB throttling meter size.
Device twin reads 50/sec/unit (for S3), Maximum of 10/sec or 1/sec/unit (for S2), 10/sec (for S1)
Device twin updates 50/sec/unit (for S3), Maximum of 10/sec or 1/sec/unit (for S2), 10/sec (for S1)
Jobs operations
(create, update, list, delete)
83.33/sec/unit (5000/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)

IoT Hub Device Provisioning Service limits

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

Resource Limit
Maximum Device Provisioning Services per Azure subscription 10
Maximum number of enrollments 500,000
Maximum number of registrations 500,000
Maximum number of enrollment groups 100
Maximum number of CAs 25

Note

You can contact Microsoft Support to increase the number of instances in your subscription.

Note

You can contact Microsoft Support to increase the number of enrollments and registrations on your provisioning service.

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/10sec/device

Data Factory limits

Data factory is a multi-tenant service that has the following default limits in place to make sure customer subscriptions are protected from each other's workloads. Many of the limits can be easily raised for your subscription up to the maximum limit by contacting support.

Version 2

Resource Default Limit Maximum Limit
Data factories in an Azure subscription 50 Contact support
Total number of entities (Pipeline, Datasets, Triggers, Linked Services, Integration runtimes) within a data factory 5000 Contact support
Total CPU cores for Azure-SSIS Integration Runtime(s) under one subscription 128 Contact support
Concurrent pipeline runs per pipeline 100 Contact support
Concurrent pipeline runs per data factory 10,000 Contact support
Max activities per pipeline (includes inner activities for containers) 40 40
Max 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
Max Timeout for pipeline activity runs 7 days 7 days
Bytes per object for pipeline objects 1 200 KB 200 KB
Bytes per object for dataset and linked service objects 1 100 KB 2000 KB
Data integration units per copy activity run 3 256 Contact support
Write API calls 2500/hr

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

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

Version 1

Resource Default Limit Maximum Limit
Data factories in an Azure subscription 50 Contact support
Pipelines within a data factory 2500 Contact support
Datasets within a data factory 5000 Contact support
Concurrent slices per dataset 10 10
Bytes per object for pipeline objects 1 200 KB 200 KB
Bytes per object for dataset and linked service objects 1 100 KB 2000 KB
HDInsight on-demand cluster cores within a subscription 2 60 Contact support
Cloud data movement units per copy activity run 3 32 Contact support
Retry count for pipeline activity runs 1000 MaxInt (32 bit)

1 Pipeline, dataset, and linked service objects represent a logical grouping of your workload. Limits for these objects do not relate to amount of data you can move and process with the Azure Data Factory service. 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 above limit is the Data Factory enforced core limit for on-demand HDInsight cores and is different from the core limit associated with your Azure subscription.

3 Data Integration Unit (DIU) for v2 or Cloud Data Movement Unit (DMU) for v1 is being used in a cloud-to-cloud copy operation. It is a measure that represents the power (a combination of CPU, memory, and network resource allocation) of a single unit in Data Factory. You can achieve higher copy throughput by using more DMUs for some scenarios. Refer to Data integration units (V2) and Cloud data movement units (V1) section on details, and Azure Data Factory pricing page for billing implication.

4 The Integration Runtime (IR) is the compute infrastructure used by Azure Data Factory to provide the following data integration capabilities across different network environments: data movement, dispatching activities to compute services, execution of SSIS packages. For more information, see Integration Runtime overview.

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

Data Lake Analytics makes the complex task of managing distributed infrastructure and complex code easy. It dynamically provisions resources and lets you do analytics on exabytes of data. When the job completes, it winds down resources automatically, and you pay only for the processing power used. As you increase or decrease the size of data stored or the amount of compute used, you don’t have to rewrite code. Many of the default limits can be easily raised for your subscription by contacting 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. Contact Microsoft support to increase this limit.
Maximum script size for job submission 3 MB
Maximum number of ADLA accounts per region per subscription 5 Contact Microsoft support to increase this limit.

Data Lake Store limits

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

Resource Default Limit Comments
Max number of Data Lake Storage Gen1 accounts, per subscription, per region 10 Contact Support to request an increase for this limit
Max number of access ACLs, per file or folder 32 This is a hard limit. Use groups to manage access with fewer entries
Max 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

The 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 Contact Support to request an increase for this limit

Stream Analytics limits


Limit identifier Limit Comments
Maximum number of Streaming Units per subscription per region 200 A request to increase streaming units for your subscription beyond 200 can be made by contacting Microsoft Support.
Maximum number of inputs per job 60 There is a hard limit of 60 inputs per Stream Analytics job.
Maximum number of outputs per job 60 There is a hard limit of 60 outputs per Stream Analytics job.
Maximum number of functions per job 60 There is a hard limit of 60 functions per Stream Analytics job.
Maximum number of Streaming Units per job 120 There is a hard limit of 120 Streaming Units per Stream Analytics job.
Maximum number of jobs per region 1500 Each subscription may have up to 1500 jobs per geographical region.
Reference data blob MB 300 Reference data blobs cannot 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're setting 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 500,000 objects can be created in a single directory by users of the Free edition of Azure Active Directory.
  • A non-admin user can create no more than 250 objects.
Schema extensions
  • String type extensions can have maximum of 256 characters.
  • Binary type extensions are limited to 256 bytes.
  • 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 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 you can synchronize from your on-premises Active Directory to Azure Active Directory using Azure AD Connect is limited to 50 K members.
Access Panel
  • There is no limit to the number of applications that can be seen in the Access Panel per end user, for users assigned licenses for Azure AD Premium or the Enterprise Mobility Suite.
  • A maximum of 10 app tiles (examples: Box, Salesforce, or Dropbox) can be seen in the Access Panel for each end user for users assigned licenses for Free or Azure AD Basic editions of Azure Active Directory. This limit does not 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.

Azure Event Grid limits

#

The following limits apply to 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

#

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

Azure Maps limits

Following is the usage limit for the Azure Maps service S0 pricing tier. Usage limit depends on the pricing tier. For more information on the Azure Maps pricing tiers, see Azure Maps pricing details.

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

Azure Policy limits

There is 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 250
Scope Initiative Definitions 100
Tenant Initiative Definitions 1000
Scope Policy/Initiative Assignments 100
Policy Definition Parameters 20
Initiative Definition Policies 100
Initiative Definition Parameters 100
Policy/Initiative Assignments Exclusions (notScopes) 250
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 (24*7).
Maximum size of a tiered volume on physical devices 64 TB for 8100 and 8600 8100 and 8600 are physical devices.
Maximum size of a tiered volume on virtual devices in Azure 30 TB for 8010
64 TB for 8020
8010 and 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 8100
24 TB for 8600
8100 and 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 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 will be processed sequentially as processing slots become available.
  • New backups of a cloned or a restored tiered volume cannot occur until the operation is finished. However, 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 restore or clone operation, regardless of the volume size.
  • The volume performance may initially be slower than normal as most of the data and metadata still resides in the cloud. Performance may 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 may 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 cannot 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 may initially be slower than normal as most of the data and metadata still resides in the cloud. Performance may 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 may be affected by Internet bandwidth to the cloud.
  • Unlike tiered volumes, in the case of 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 may 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/s with a single 10GbE network interface Up to 2x with MPIO and two network interfaces.
Maximum client read/write throughput (when served from the HDD tier)* 120/250 MB/s
Maximum client read/write throughput (when served from the cloud tier)* 11/41 MB/s 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 may be lower and depends on I/O mix and network conditions.

Log Analytics limits

The following limits apply to Log Analytics resources per subscription:

Resource Default Limit Comments
Number of free workspaces per subscription 10 This limit cannot be increased.
Number of paid workspaces per subscription N/A You are limited by the number of resources within a resource group and number of resource groups per subscription

Note

As of April 2, 2018, new workspaces in a new subscription will automatically use the Per GB pricing plan. For existing subscriptions created before April 2, or a subscription that was tied to an existing EA enrollment, you can continue choosing between the three pricing tiers for new workspaces.

The following limits apply to each Log Analytics workspace:

Free Standard Premium Standalone OMS Per GB
Data volume collected per day 500 MB1 None None None None None
Data retention period 7 days 1 month 12 months 1 month2 1 month 2 1 month 2

1 When customers reach their 500 MB daily data transfer limit, data analysis stops and resumes at the start of the next day. A day is based on UTC.

2 The data retention period for the Standalone, OMS, and Per GB pricing plans can be increased to 730 days.

Category Limits Comments
Data Collector API Maximum size for a single post is 30 MB
Maximum size for field values is 32 KB
Split larger volumes into multiple posts
Fields longer than 32 KB are truncated.
Search API 5000 records returned for non-aggregated data
500000 records for aggregated data
Aggregated data is a search that includes the summarize command

Backup limits

The following limits apply to Azure Backup.

Limit Default
Servers/machines that can be registered in a vault Windows Server/Windows Client/System Center DPM: 50

IaaS VMs: 1000
Size of a data source in vault storage 54400 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: 3 a day
System Center DPM: 2 a day
IaaS VMs: Once a day
Data disks attached to an Azure VM for backup 32
Individual data disk attached to Azure VM for backup 4095 GB

SignalR Service limits

Resource Default limit Maximum limit
SignalR service units per instance for Free tier 1 1
SignalR service units per instance for Standard tier 100 100
SignalR service units per subscription per region for Free tier 5 5
Total SignalR service unit counts per subscription per region 50 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

Application Insights limits

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 mail to AIDataCap@microsoft.com.
Throttling 32 K 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 K
Property and metric name length 150 See type schemas.
Property value string length 8,192 See type schemas.
Trace and exception message length 10 K 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.

API Management limits

Resource Limit
Maximum number of scale units 10 per region1
Cache size 5 GB per unit2
Concurrent backend connections3 per HTTP authority 2048 per unit4
Maximum cached response size 2MB
Maximum policy document size 256KB5
Maximum custom gateway domains per service instance6 20
Maximum number of service instances per subscription7 5
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 1000
Maximum total request duration7 30 seconds
Maximum buffered payload size7 2MB

1 Scaling limits depend on the pricing tier. To see the pricing tiers and their scaling limits go to API Management Pricing.
2 Per unit cache size depends on the pricing tier. To see the pricing tiers and their scaling limits go to API Management Pricing.
3 Connections are pooled and re-used, unless explicitly closed by the backend.
4 Per unit of the Basic, Standard and Premium tiers. The Developer tier is limited to 1024. Doesn't apply to the Consumption tier.
5 In the Basic, Standard and Premium tiers. In the Consumption tier policy document size is limited to 4KB.
6 Available in the Premium tier only.
7 Applies to the Consumption tier only.

Azure Cache for Redis limits

Resource Limit
Cache size 530 GB
Databases 64
Max 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 (Max 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 2048-bit 5 1000 10 2000
RSA 3072-bit 5 250 10 500
RSA 4096-bit 5 125 10 250
ECC P-256 5 1000 10 2000
ECC P-384 5 1000 10 2000
ECC P-521 5 1000 10 2000
ECC SECP256K1 5 1000 10 2000

Secrets, Managed Storage Account Keys, and vault transactions:

Transactions Type Max transactions allowed in 10 seconds, per vault per region1
All transactions 2000

See Azure Key Vault throttling guidance for information on how to handle throttling when these limits are exceeded.

1 There is a subscription-wide limit for all transaction types, that is 5x per key vault limit. For example, HSM- other transactions per subscription are limited to 5000 transactions in 10 seconds per subscription.

Multi-Factor Authentication

Resource Default Limit Maximum Limit
Max number of Trusted IP addresses/ranges per subscription 0 50
Remember my devices - number of days 14 60
Max 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 1800
Lock user account after X consecutive MFA denials Not Set 99
Reset account lockout counter after X minutes Not Set 9999
Unlock account after X minutes Not Set 9999

Automation limits

Resource Maximum Limit Notes
Max number of new jobs that can be submitted every 30 seconds per Automation Account (non Scheduled jobs) 100 When this limit it hit, the subsequent requests to create a job fail. The client receives an error response.
Max number of concurrent running jobs at the same instance of time per Automation Account (non Scheduled jobs) 200 When this limit it hit, the subsequent requests to create a job fail. The client receives an error response.
Max storage size of job metadata for a 30 day rolling period. 10GB (approximately 4 million jobs) When this limit it hit, the subsequent requests to create a job fail.
Max number of modules that can be imported every 30 seconds per Automation Account 5
Max size of a Module 100 MB
Job Run Time - Free tier 500 minutes per subscription per calendar month
Max amount of disk space allowed per sandbox 1 1 GB Applies to Azure sandboxes only
Max amount of memory given to a sandbox 1 400 MB Applies to Azure sandboxes only
Max number of network sockets allowed per sandbox 1 1000 Applies to Azure sandboxes only
Maximum runtime allowed per runbook 1 3 hours Applies to Azure sandboxes only
Max number of Automation Accounts in a subscription No Limit
Max number of concurrent jobs that be run on a single Hybrid Runbook Worker 50
Max Runbook Job parameters size 512 kb
Max Runbook parameters 50 You can pass a JSON or XML string to a parameter and parse it with the runbook if you hit the 50 parameter limit
Max webhook payload size 512 kb
Max days that job data is retained 30 days

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

Managed Identity limits

Category Limit
User assigned managed identities
  • When creating user assigned managed identities, only alphanumeric characters (0-9, a-z, A-Z) and the hyphen (-) are supported. Additionally, the name should be limited to 24 characters in length for the assignment to VM/VMSS to work properly.
  • If using 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 per Azure subscription 2000
Custom roles per tenant 2000

SQL Database limits

For SQL Database limits, see SQL Database Resource Limits for single databases and SQL Database Resource Limits for elastic pools and pooled databases.

SQL Data Warehouse limits

For SQL Data Warehouse limits, see SQL Data Warehouse Resource Limits.

See also

Understanding Azure Limits and Increases

Virtual Machine and Cloud Service Sizes for Azure

Sizes for Cloud Services