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, you can upgrade to a Pay-As-You-Go subscription. For more information, see Upgrade Azure Free Trial to Pay-As-You-Go.
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 core quotas as an example. If you need to request a quota increase with support for cores, you need to decide how many cores you want to use in which regions, and then make a specific request for Azure Resource Group core quotas for the amounts and regions that you want. Therefore, if you need to use 30 cores in West Europe to run your application there; you should specifically request 30 cores in West Europe. But you will not have a core quota increase in any other region -- only West Europe will have the 30-core 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
- Active Directory
- API Management
- App Service
- Application Gateway
- Application Insights
- Automation
- Azure Cosmos DB
- Azure Event Grid
- Azure Redis Cache
- Backup
- Batch
- BizTalk Services
- CDN
- Cloud Services
- Container Instances
- Data Factory
- Data Lake Analytics
- Data Lake Store
- DNS
- Event Hubs
- IoT Hub
- IoT Hub Device Provisioning Service
- Key Vault
- Log Analytics / Operational Insights
- Media Services
- Mobile Engagement
- Mobile Services
- Monitor
- Multi-Factor Authentication
- Networking
- Network Watcher
- Notification Hub Service
- Resource Group
- Scheduler
- Search
- Service Bus
- Site Recovery
- SQL Database
- Storage
- StorSimple System
- Stream Analytics
- Subscription
- Traffic Manager
- Virtual Machines
- Virtual Machine Scale Sets
Subscription limits
Subscription limits
| Resource | Default Limit | Maximum Limit |
|---|---|---|
| Cores per subscription 1 | 20 | 10,000 |
| Co-administrators per subscription | 200 | 200 |
| Storage accounts per subscription2 | 200 | 250 |
| Cloud services per subscription | 20 | 200 |
| Local networks per subscription | 10 | 500 |
| SQL Database servers per subscription | 6 | 150 |
| DNS servers per subscription | 9 | 100 |
| Reserved IPs per subscription | 20 | 100 |
| Hosted service certificates per subscription | 400 | 400 |
| Affinity groups per subscription | 256 | 256 |
| Alert rules per subscription | 250 | 250 |
1Extra Small instances count as one core towards the core limit despite using a partial core.
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.
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 handling limits on Resource Manager requests, 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 subscription | 200 | 2002 |
| Resource Groups per subscription | 800 | 800 |
| Availability Sets per subscription | 2,000 per Region | 2,000 per Region |
| Resource Manager API Reads | 15,000 per hour | 15,000 per hour |
| Resource Manager API Writes | 1,200 per hour | 1,200 per hour |
| 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 |
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 | 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.
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. See How to Connect Virtual Machines with a Virtual Network or Cloud Service.
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 | 300 | 300 |
| Maximum number of scale sets in a region | 2000 | 2000 |
Container Instances Limits
| Resource | Default Limit |
|---|---|
| Container groups per subscription | 20 |
Networking limits
ExpressRoute Limits
The following limits apply to ExpressRoute resources per subscription.
| Resource | Default Limit |
|---|---|
| ExpressRoute circuits per subscription | 10 |
| ExpressRoute circuits per region per subscription for ARM | 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 public peering with ExpressRoute standard | 200 |
| Maximum number of routes for Azure public peering with ExpressRoute premium add-on | 200 |
| 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 |
| 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.
| Resource | Default limit | Maximum limit |
|---|---|---|
| Virtual networks | 50 | 100 |
| Local network sites | 20 | contact support |
| DNS Servers per virtual network | 20 | 100 |
| 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 | 400 |
| 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.
| Resource | Default limit | Maximum Limit |
|---|---|---|
| Virtual networks | 50 | 1000 |
| Subnets per virtual network | 1000 | 10000 |
| Virtual network peerings per Virtual Network | 10 | 50 |
| DNS Servers per virtual network | 9 | 25 |
| Private IP Addresses per virtual network | 4096 | 8192 |
| Private IP Addresses per network interface | 256 | 1024 |
| Concurrent TCP or UDP flows per NIC of a virtual machine or role instance | 500K | 500K |
| Network Interfaces (NIC) | 350 | 20000 |
| Network Security Groups (NSG) | 100 | 5000 |
| NSG rules per NSG | 200 | 500 |
| IP addresses and ranges specified for source or destination in a security rule | 2000 | 4000 |
| Application security groups | 200 | 500 |
| Application security groups per IP configuration, per NIC | 10 | 20 |
| IP configurations per application security group | 1000 | 4000 |
| Application security groups that can be specified within all security rules of a network security group | 50 | 100 |
| User defined route tables | 100 | 200 |
| User defined routes per route table | 100 | 400 |
| Public IP addresses - dynamic | (Basic) | 60 |
| Public IP addresses - static | (Basic) 20 | contact support |
| Public IP addresses - static | (Standard) 20 | contact support |
| Load Balancers (internal and internet facing, Basic and Standard) | 100 | 1000 |
| Load Balancer (Basic) rules per load balancer | 150 | 250 |
| Load Balancer (Standard) rules per load balancer | 1250 | 1500 |
| Load Balancer (Basic) rules per IP configuration | 250 | 250 |
| Public front end IP per Load Balancer (Basic) | 10 | 30 |
| Public front end IP per Load Balancer (Standard) | 10 | 600 |
| Private front end IP per Load Balancer (Basic) | 10 | contact support |
| Private front end IP per Load Balancer (Standard) | 10 | 600 |
| Point-to-Site Root Certificates per VPN Gateway | 20 | 20 |
Contact support in case you need to increase limits from default.
Application Gateway limits
| Resource | Default limit | Note |
|---|---|---|
| Application Gateway | 50 per subscription | Maximum 100 |
| Frontend IP Configurations | 2 | 1 public and 1 private |
| Frontend Ports | 20 | |
| Backend Address Pools | 20 | |
| Backend Servers per pool | 100 | |
| HTTP Listeners | 20 | |
| HTTP load balancing rules | 200 | # of HTTP Listeners * n, n=10 Default |
| Backend HTTP settings | 20 | 1 per Backend Address Pool |
| Instances per gateway | 10 | |
| SSL certificates | 20 | 1 per HTTP Listeners |
| Authentication certificates | 5 | Maximum 10 |
| Request time out min | 1 second | |
| Request time out max | 24 hrs | |
| Number of sites | 20 | 1 per HTTP Listeners |
| URL Maps per listener | 1 |
Network Watcher limits
| Resource | Default limit | Note |
|---|---|---|
| Network Watcher | 1 per region | |
| Packet Capture sessions | 10 per region | # of sessions only, not saved captures |
Traffic Manager limits
| Resource | Default limit |
|---|---|
| Profiles per subscription | 100 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.
Storage limits
For additional details on storage account limits, see Azure Storage Scalability and Performance Targets.
Storage Service limits
| Resource | Default Limit |
|---|---|
| Number of storage accounts per subscription | 2001 |
| Max storage account capacity | 500 TB2 |
| Max number of blob containers, blobs, file shares, tables, queues, entities, or messages per storage account | No limit |
| Max size of a single blob container, table, or queue | Same as max storage account capacity |
| Max number of blocks in a block blob or append blob | 50,000 |
| Max size of a block in a block blob | 100 MB |
| Max size of a block blob | 50,000 X 100 MB (approx. 4.75 TB) |
| Max size of a block in an append blob | 4 MB |
| Max size of an append blob | 50,000 X 4 MB (approx. 195 GB) |
| Max size of a page blob | 8 TB |
| Max size of a table entity | 1 MB |
| Max number of properties in a table entity | 252 |
| Max size of a message in a queue | 64 KB |
| Max size of a file share | 5 TB |
| Max size of a file in a file share | 1 TB |
| Max number of files in a file share | Only limit is the 5 TB total capacity of the file share |
| Max IOPS per share | 1000 |
| Max number of stored access policies per container, file share, table, or queue |5 |
| Maximum request rate per storage account |Blobs: 20,000 requests per second2 for blobs of any valid size3
Files: 20,000 requests per second 2 for files of any valid size3
Queues: 20,000 messages per second (assuming 1 KB message size)
Tables: 20,000 transactions per second (assuming 1 KB entity size) |
| Target throughput for single blob |Up to 60 MB per second, or up to 500 requests per second |
| Target throughput for single queue (1 KB messages) |Up to 2000 messages per second |
| Target throughput for single table partition (1 KB entities) |Up to 2000 entities per second |
| Target throughput for single file share |Up to 60 MB per second |
| Max ingress3 per storage account (US Regions) |10 Gbps if GRS/ZRS4 enabled, 20 Gbps for LRS2 |
| Max egress3 per storage account (US Regions) |20 Gbps if RA-GRS/GRS/ZRS4 enabled, 30 Gbps for LRS2 |
| Max ingress3 per storage account (Non-US regions) |5 Gbps if GRS/ZRS4 enabled, 10 Gbps for LRS2 |
| Max egress3 per storage account (Non-US regions) |10 Gbps if RA-GRS/GRS/ZRS4 enabled, 15 Gbps for LRS2 |
1Includes 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.
2 To get your standard storage accounts to grow past the advertised limits in capacity, ingress/egress and request rate, please make a request through Azure Support. The Azure Storage team will review the request and may approve higher limits on a case by case basis.
3 Capped only by the account's ingress/egress limits. Ingress refers to all data (requests) being sent to a storage account. Egress refers to all data (responses) being received from a storage account.
4Azure 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. Available only for block blobs.
- LRS: Locally redundant storage.
Virtual machine disk limits
An Azure virtual machine supports attaching a number of data disks. For optimal performance, you will want to limit the number of highly utilized disks attached to the virtual machine to avoid possible throttling. If all disks are not being highly utilized at the same time, the storage account can support a larger number disks.
For Azure Managed Disks: Managed Disks count limit is regional and also depends on the storage type. The default and also the maximum limit is 10,000 per subscription, per region and per storage type. For example, you can create up to 10,000 standard managed disks and also 10,000 premium managed disks in a subscription and in a region.
Managed Snapshots and Images are counted against the Managed Disks limit.
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), as shown in the table below.
- 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 disks
| Standard Disk Type | S4 | S6 | S10 | S20 | S30 | S40 | S50 |
|---|---|---|---|---|---|---|---|
| Disk size | 32 GB | 64 GB | 128 GB | 512 GB | 1024 GB (1 TB) | 2048 GB (2TB) | 4095 GB (4 TB) |
| IOPS per disk | 500 | 500 | 500 | 500 | 500 | 500 | 500 |
| Throughput per disk | 60 MB/sec | 60 MB/sec | 60 MB/sec | 60 MB/sec | 60 MB/sec | 60 MB/sec | 60 MB/sec |
Premium managed virtual machine disks: per disk limits
| Premium Disks Type | P4 | P6 | P10 | P20 | P30 | P40 | P50 |
|---|---|---|---|---|---|---|---|
| Disk size | 32 GB | 64 GB | 128 GB | 512 GB | 1024 GB (1 TB) | 2048 GB (2 TB) | 4095 GB (4 TB) |
| IOPS per disk | 120 | 240 | 500 | 2300 | 5000 | 7500 | 7500 |
| Throughput per disk | 25 MB/sec | 50 MB/sec | 100 MB/sec | 150 MB/sec | 200 MB/sec | 250 MB/sec | 250 MB/sec |
Premium managed virtual machine disks: per VM limits
| Resource | Default Limit |
|---|---|
| Max IOPS Per VM | 80,000 IOPS with GS5 VM1 |
| Max throughput per VM | 2,000 MB/s with GS5 VM1 |
1Refer to VM Size for limits on other VM sizes.
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 VM1 |
| Max throughput per VM | 2,000 MB/s with GS5 VM1 |
1Refer to VM Size for limits on other VM sizes.
Storage Resource Provider limits
The following limits apply when using the Azure Resource Manager and Azure Resource Groups only.
| 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 |
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 |
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, API Apps, and Logic Apps.
| Resource | Free | Shared (Preview) | Basic | Standard | Premium (Preview) |
|---|---|---|---|---|---|
| Web, mobile, or API apps per App Service plan1 | 10 | 100 | Unlimited2 | Unlimited2 | Unlimited2 |
| Logic apps per App Service plan1 | 10 | 10 | 10 | 20 per core | 20 per core |
| App Service plan | 1 per region | 10 per resource group | 100 per resource group | 100 per resource group | 100 per resource group |
| Compute instance type | Shared | Shared | Dedicated3 | Dedicated3 | Dedicated3 |
| Scale-Out (max instances) | 1 shared | 1 shared | 3 dedicated3 | 10 dedicated3 | 20 dedicated (50 in ASE)3,4 |
| Storage5 | 1 GB5 | 1 GB5 | 10 GB5 | 50 GB5 | 500 GB4,5 |
| CPU time (5 min)6 | 3 minutes | 3 minutes | 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 |
| Memory (1 hour) | 1024 MB per App Service plan | 1024 MB per app | 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 |
| Application architecture | 32-bit | 32-bit | 32-bit/64-bit | 32-bit/64-bit | 32-bit/64-bit |
| Web Sockets per instance7 | 5 | 35 | 350 | Unlimited | Unlimited |
| Concurrent debugger connections per application | 1 | 1 | 1 | 5 | 5 |
| azurewebsites.net subdomain with FTP/S and SSL | X | X | X | X | X |
| Custom domain support | X | X | X | X | |
| Custom domain SSL support | Unlimited | Unlimited, 5 SNI SSL and 1 IP SSL connections included | Unlimited, 5 SNI SSL and 1 IP SSL connections included | ||
| Integrated Load Balancer | X | X | X | X | |
| Always On | X | X | X | ||
| Scheduled Backups | Once per day | Once every 5 minutes8 | |||
| Auto Scale | X | X | X | ||
| WebJobs9 | X | X | X | X | X |
| Azure Scheduler support | X | X | X | X | |
| Endpoint monitoring | X | X | X | ||
| Staging Slots | 5 | 20 | |||
| Custom domains per app | 500 | 500 | 500 | 500 | |
| SLA | 99.9% | 99.95%10 | 99.95%10 |
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. See App Service Pricing for more details.
4Premium tier allows up to 50 computes instances (subject to availability) and 500 GB of disk space when using App Service Environments, and 20 compute instances and 250 GB storage otherwise.
5The storage limit is the total content size across all apps in the
same App Service plan. More storage options are available in App Service Environment
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.
8Premium tier allows backup intervals down up to every 5 minutes when using App Service Environments, and 50 times per day otherwise.
9Run 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.
10SLA of 99.95% provided for deployments that use multiple instances with Azure Traffic Manager configured for failover.
Scheduler limits
The following table describes each of the major quotas, limits, defaults, and throttles in Azure Scheduler.
| Resource | Limit Description |
|---|---|
| Job size | Maximum job size is 16K. If a PUT or a PATCH results in a job larger than these limits, a 400 Bad Request status code is returned. |
| Request URL size | Maximum size of the request URL is 2048 chars. |
| Aggregate header size | Maximum aggregate header size is 4096 chars. |
| Header count | Maximum header count is 50 headers. |
| Body size | Maximum body size is 8192 chars. |
| Recurrence span | Maximum recurrence span is 18 months. |
| Time to start time | Maximum “time to start time” is 18 months. |
| Job history | Maximum response body stored in job history is 2048 bytes. |
| Frequency | The default max frequency quota is 1 hour in a free job collection and 1 minute in a standard job collection. The max frequency is configurable on a job collection to be lower than the maximum. All jobs in the job collection are limited 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 then request will fail with a 409 Conflict status code. |
| Jobs | The default max jobs quota is 5 jobs in a free job collection and 50 jobs in a standard job collection. The maximum number of jobs is configurable on a job collection. All jobs in the job collection are limited the value set on the job collection. If you attempt to create more jobs than the maximum jobs quota, then the request fails with a 409 Conflict status code. |
| Job collections | Maximum number of job collection per subscription is 200,000. |
| Job history retention | Job history is retained for up to 2 months or up to the last 1000 executions. |
| Completed and faulted job retention | Completed and faulted jobs are retained for 60 days. |
| Timeout | There’s a static (not configurable) request timeout of 60 seconds for HTTP actions. For longer running operations, follow HTTP asynchronous protocols; for example, return a 202 immediately but continue working in the background. |
Batch limits
| Resource | Default Limit | Maximum Limit |
|---|---|---|
| Batch accounts per region per subscription | 3 | 50 |
| Dedicated cores per Batch account (Batch service mode)1 | 20 | N/A2 |
| Low-priority cores per Batch account (Batch service mode)3 | 50 | N/A4 |
| Active jobs and job schedules5 per Batch account | 20 | 50006 |
| Pools per Batch account | 20 | 2500 |
1 Dedicated core quotas shown are only for accounts with pool allocation mode set to Batch service. For accounts with the mode set to user subscription, core quotas are based on the VM cores quota at a regional level or per VM family in your subscription.
2 The number of dedicated cores per Batch account can be increased, but the maximum number is unspecified. Contact Azure support to discuss increase options.
3 Low-priority core quotas shown are only for accounts with pool allocation mode set to Batch service. Low-priority cores are not available for accounts with pool allocation mode set to user subscription.
4 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.
5 Completed jobs and job schedules are not limited.
6 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.
Mobile Engagement limits
| Resource | Maximum Limit |
|---|---|
| App Collection Users | 5 per App Collection |
| Average Data points | 200 per Active User/Day |
| Average App-Info set | 50 per Active User/Day |
| Average Messages pushed | 20 per Active User/Day |
| Segments | 100 per app |
| Criteria per segment | 10 |
| Active Push Campaigns | 50 per app |
| Total Push Campaigns (includes Active & Completed) | 1000 per app |
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 | Basic | S1 | S2 | S3 | S3 HD 1 |
|---|---|---|---|---|---|---|
| Maximum services | 1 | 12 | 12 | 6 | 6 | 6 |
| Maximum scale in SU 2 | N/A 3 | 3 SU 4 | 36 SU | 36 SU | 36 SU | 36 SU |
1 S3 HD does not support indexers at this time.
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 how search units are computed, plus a chart of valid combinations that stay under the maximum limits, see Scale resource levels for query and index workloads.
3 Free is based on shared resources used by multiple subscribers. At this tier, there are no dedicated resources for an individual subscriber. For this reason, maximum scale is marked as not applicable.
4 Basic has one fixed partition. At this tier, additional SUs are used for allocating more replicas for increased query workloads.
Limits per search service
Storage is constrained by disk space or by a hard limit on the maximum number of indexes or documents, whichever comes first.
| Resource | Free | Basic | S1 | S2 | S3 | S3 HD |
|---|---|---|---|---|---|---|
| Service Level Agreement (SLA) | No 1 | 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 2 |
| Partition size | N/A | 2 GB | 25 GB | 100 GB | 200 GB | 200 GB |
| Replicas | N/A | 3 | 12 | 12 | 12 | 12 |
| Maximum indexes | 3 | 5 | 50 | 200 | 200 | 1000 per partition or 3000 per service |
| Maximum indexers | 3 | 5 | 50 | 200 | 200 | No indexer support |
| Maximum datasources | 3 | 5 | 50 | 200 | 200 | No indexer support |
| Maximum documents | 10,000 | 1 million | 15 million per partition or 180 million per service | 60 million per partition or 720 million per service | 120 million per partition or 1.4 billion per service | 1 million per index or 200 million per partition |
| Estimated queries per second (QPS) | N/A | ~3 per replica | ~15 per replica | ~60 per replica | ~60 per replica | >60 per replica |
1 Free tier and preview features do not come with service level agreements (SLAs). For all billable tiers, 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.
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.
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, S2) 10 (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 S3 RUs are not available in India West. The max RU limits get reset if the customer changes the type (for example, from S2 to S1).
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.
Starting 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 will be 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 with the intent to process it with one of the media processors in our service (i.e. encoders like Media Encoder Standard and Media Encoder Premium Workflow, or analysis engines like Face Detector), then you should be aware of the constraint on the maximum size.
As of May 15, 2017, the maximum size supported for a single blob is 195 TB - with file largers than this limit, your Task will fail. We are working a fix to address this limit. In addition, the constraint on the maximum size of the Asset is as follows.
| Media Reserved Unit type | Maximum Input Size (GB) |
|---|---|
| S1 | 325 |
| S2 | 640 |
| S3 | 260 |
CDN limits
| Resource | Default limit | Maximum limit |
|---|---|---|
| CDN profiles | 8 | 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 | Limit |
|---|---|
| Autoscale Settings | 100 per region per subscription |
| Metric Alerts | 100 active alert rules per subscription |
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 | Type | Behavior when exceeded | Value |
|---|---|---|---|---|
| Number of event hubs per namespace | Namespace | Static | Subsequent requests for creation of a new event hub will be rejected. | 10 |
| Number of partitions per event hub | Entity | Static | - | 32 |
| Number of consumer groups per event hub | Entity | Static | - | 20 |
| Number of AMQP connections per namespace | Namespace | Static | 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 | System-wide | Static | - | 256 KB |
| Maximum size of an event hub name | Entity | Static | - | 50 characters |
| Number of non-epoch receivers per consumer group | Entity | Static | - | 5 |
| Maximum retention period of event data | Entity | Static | - | 1-7 days |
| Maximum throughput units | Namespace | Static | 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 | Static | 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 | Type | Behavior when exceeded | Value |
|---|---|---|---|---|
| Maximum number of basic / standard namespaces per Azure subscription | Namespace | Static | Subsequent requests for additional basic / standard namespaces will be rejected by the portal. | 100 |
| Maximum number of premium namespaces per Azure subscription | Namespace | Static | Subsequent requests for additional premium namespaces will be rejected by the portal. | 10 |
| Queue/topic size | Entity | Defined upon creation of the queue/topic. | Incoming messages will be rejected and an exception will be received by the calling code. | 1, 2, 3, 4 or 5 GB. If partitioning is enabled, the maximum queue/topic size is 80 GB. |
| Number of concurrent connections on a namespace | Namespace | Static | Subsequent requests for additional connections will be rejected and an exception will be 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 | Static | Subsequent receive requests will be rejected and an exception will be 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 service namespace | System-wide | Static | Subsequent requests for creation of a new topic or queue on the service namespace will be rejected. As a result, if configured through the Azure portal, an error message will be generated. If called from the management API, an exception will be received by the calling code. | 10,000 The total number of topics plus queues in a service namespace must be less than or equal to 10,000. This is not applicable to Premium as all entities are partitioned. |
| Number of partitioned topics/queues per service namespace | System-wide | Static | Subsequent requests for creation of a new partitioned topic or queue on the service namespace will be rejected. As a result, if configured through the Azure portal, an error message will be generated. If called from the management API, a QuotaExceededException exception will be received by the calling code. | Basic and Standard Tiers - 100 Premium - 1,000 (per messaging unit) Each partitioned queue or topic counts towards the quota of 10,000 entities per namespace. |
| Maximum size of any messaging entity path: queue or topic | Entity | Static | - | 260 characters |
| Maximum size of any messaging entity name: namespace, subscription, or subscription rule | Entity | Static | - | 50 characters |
| Message size for a queue/topic/subscription entity | System-wide | Static | Incoming messages that exceed these quotas will be rejected and an exception will be received by the calling code. | Maximum message size: 256KB (Standard tier) / 1MB (Premium tier). Note Due to system overhead, this limit is usually slightly less. Maximum header size: 64KB 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 | System-wide | Static | A SerializationException exception is generated. | Maximum message property size for each property is 32K. Cumulative size of all properties cannot exceed 64K. This 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 | System-wide | Static | Subsequent requests for creating additional subscriptions for the topic will be rejected. As a result, if configured through the portal, an error message will be shown. If called from the management API an exception will be received by the calling code. | 2,000 |
| Number of SQL filters per topic | System-wide | Static | Subsequent requests for creation of additional filters on the topic will be rejected and an exception will be received by the calling code. | 2,000 |
| Number of correlation filters per topic | System-wide | Static | Subsequent requests for creation of additional filters on the topic will be rejected and an exception will be received by the calling code. | 100,000 |
| Size of SQL filters/actions | System-wide | Static | Subsequent requests for creation of additional filters will be rejected and an exception will be received by the calling code. | Maximum length of filter condition string: 1024 (1K). Maximum length of rule action string: 1024 (1K). Maximum number of expressions per rule action: 32. |
| Number of SharedAccessAuthorizationRule rules per namespace, queue, or topic | Entity, namespace | Static | Subsequent requests for creation of additional rules will be rejected and an exception will be 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. |
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 | 10 |
| Maximum free IoT hubs per Azure subscription | 1 |
| 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 | 256 KB |
| 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 | 512 bytes |
| Maximum depth of object in device twin | 5 |
| Maximum size of direct method payload | 8 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 10 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 | 3000/sec/unit (for S3), 60/sec/unit (for S2), 20/sec/unit (for S1) |
| 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 | 10,000 |
| Maximum number of registrations | 10,000 |
| Maximum number of enrollment groups | 100 |
| Maximum number of CAs | 10 |
Note
These limits are for public preview. Once the service is generally available, you can contact Microsoft Support to increase the number of instances in your subscription.
The Device Provisioning Service throttles requests when the following quotas are exceeded:
| Throttle | Per-service value |
|---|---|
| Operations | 100/min |
| Device registrations | 100/min |
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 |
| Pipelines within a data factory | 2500 | Contact support |
| Datasets within a data factory | 2500 | Contact support |
| Triggers within a data factory | 2500 | Contact support |
| Linked services within a data factory | 2500 | Contact support |
| Integration runtimes within a data factory 4 | 2500 | Contact support |
| Concurrent pipeline runs per pipeline | 20 | Contact support |
| Max activities per pipeline | 20 | 30 |
| Max parameters per pipeline | 20 | 30 |
| 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 |
| Cloud data movement units 3 | 32 | Contact support |
| Retry count for pipeline activity runs | 1 day(timeout) | 1 day (timeout) |
| 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 |
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 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 Cloud data movement unit (DMU) 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 Cloud data movement units section on details.
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. |
| Maximum script size for job submission | 3 MB |
Data Lake Store limits
Azure Data Lake Store is an enterprise-wide hyper-scale repository for big data analytic workloads. Data Lake Store 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 Store account.
| Resource | Default Limit | Comments |
|---|---|---|
| Max number of Data Lake Store 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 |
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 | 100 | Reference data blobs cannot be larger than 100 MB each. |
Active Directory limits
Here are the usage constraints and other service limits for the Azure Active Directory service.
| Category | Limits |
|---|---|
| Directories | A single user can only be associated with a maximum of 20 Azure Active Directory directories. Examples of possible combinations:
|
| Objects |
|
| Schema extensions |
|
| Applications | A maximum of 100 users can be owners of a single application. |
| Groups |
|
| Access Panel |
|
| 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
| Resource | Limit |
|---|---|
| Event Subscriptions per region | 1000 |
| Custom Topics per region | 20 |
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 |
|
| Restore and clone recover time for tiered volumes | < 2 minutes |
|
| Restore recover time for locally pinned volumes | < 2 minutes |
|
| 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
Note
Log Analytics was formerly known as Operational Insights.
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 |
The following limits apply to each Log Analytics workspace:
| Free | Standard | Premium | Standalone | OMS | |
|---|---|---|---|---|---|
| Data volume collected per day | 500 MB1 | None | None | None | None |
| Data retention period | 7 days | 1 month | 12 months | 1 month2 | 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 and OMS 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 measure command |
Backup limits
The following limits apply to Azure Backup.
| Limit Identifier | Default Limit |
|---|---|
| Number of servers/machines that can be registered against each vault | 50 for Windows Server/Client/SCDPM 200 for IaaS VMs |
| Size of a data source for data stored in Azure vault storage | 54400 GB max1 |
| Number of backup vaults that can be created in each Azure subscription | 25(Backup vaults) 25 Recovery Services vault per region |
| Number of times backup can be scheduled per day | 3 per day for Windows Server/Client 2 per day for SCDPM Once a day for IaaS VMs |
| Data disks attached to an Azure virtual machine for backup | 16 |
- 1The 54400 GB limit does not apply to IaaS VM backup.
Site Recovery limits
The following limits apply to Azure Site Recovery:
| LIMIT IDENTIFIER | DEFAULT LIMIT |
|---|---|
| Number of vaults per subscription | 25 |
| 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 | 500 GB | You can reduce data by setting a cap. If you need more, mail AIDataCap@microsoft.com. |
| Free data per month (Basic price plan) |
1 GB | Additional data is charged per gigabyte. |
| 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 | 10 | |
| Profiler data retention | 5 days | |
| Profiler data sent per day | 10GB |
For more information, see About pricing and quotas in Application Insights.
API Management limits
| Resource | Limit |
|---|---|
| API Calls (per unit of scale) | 32 million per day1 |
| Data transfer (per unit of scale) | 161 GB per day1 |
| Cache | 5 GB1 |
| Units of scale | Unlimited1 |
| Azure Active Directory Integration | Unlimited User Accounts1 |
1API Management limits are different for each pricing tier. To see the pricing tiers and their associated limits and scaling options, see API Management Pricing.
Azure Redis Cache limits
| Resource | Limit |
|---|---|
| Cache size | 530 GB |
| Databases | 64 |
| Max connected clients | 40,000 |
| Redis Cache replicas (for high availability) | 1 |
| Shards in a premium cache with clustering | 10 |
Azure Redis Cache limits and sizes are different for each pricing tier. To see the pricing tiers and their associated sizes, see Azure Redis Cache Pricing.
For more information on Azure Redis Cache configuration limits, see Default Redis server configuration.
Because configuration and management of Azure Redis Cache instances is done by Microsoft, not all Redis commands are supported in Azure Redis Cache. For more information, see Redis commands not supported in Azure Redis Cache.
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 |
Secrets, Managed Storage Account Keys, and vault transactions:
| Transactions Type | Max transactions allowed in 10 seconds, per vault per region1 |
|---|---|
| All transactions | 2000 |
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 |
|---|---|
| Max number of new jobs that can be submitted every 30 seconds per Automation Account (non Scheduled jobs) | 100 |
| Max number of concurrent running jobs at the same instance of time per Automation Account (non Scheduled jobs) | 200 |
| 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 memory given to a job | 400 MB |
| Max number of network sockets allowed per job | 1000 |
SQL Database limits
For SQL Database limits, see SQL Database Resource Limits.
See also
Understanding Azure Limits and Increases




