Azure subscription and service limits, quotas, and constraints

• 11/18/2019
• 86 minutes to read
• • 
  • 
  • 
  • 
  • 
  • +89

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

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

Limits and Azure Resource Manager

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

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

Service-specific limits

• Active Directory
• API Management
• App Service
• Application Gateway
• Automation
• Azure Cache for Redis
• Azure Cloud Services
• Azure Cognitive Search
• Azure Cognitive Services
• Azure Cosmos DB
• Azure Database for MySQL
• Azure Database for PostgreSQL
• Azure DNS
• Azure Firewall
• Azure Functions
• Azure Kubernetes Service
• Azure Machine Learning
• Azure Maps
• Azure Monitor
• Azure Policy
• Azure SignalR Service
• Backup
• Batch
• BizTalk Services
• Container Instances
• Container Registry
• Content Delivery Network
• Data Factory
• Data Lake Analytics
• Data Lake Store
• Database Migration Service
• Event Grid
• Event Hubs
• Front Door Service
• Identity Manager
• IoT Central
• IoT Hub
• IoT Hub Device Provisioning Service
• Key Vault
• Media Services
• Mobile Services
• Multi-Factor Authentication
• Networking
  • Application Gateway
  • Azure Bastion
  • Azure DNS
  • Azure Front Door Service
  • Azure Firewall
  • ExpressRoute
  • Load Balancer
  • Network Watcher
  • Public IP address
  • Private Link
  • Traffic Manager
  • Virtual Network
  • Virtual WAN
• Notification Hubs
• Resource group
• Role-based access control
• Scheduler
• Service Bus
• Site Recovery
• SQL Database
• SQL Data Warehouse
• Storage
• StorSimple System
• Stream Analytics
• Subscription
• Virtual Machines
• Virtual machine scale sets

Subscription limits

Subscription limits - Azure Service Management (classic deployment model)

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

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

Subscription limits - Azure Resource Manager

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

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

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

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

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

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

Resource group limits

¹If you reach the limit of 800 deployments per resource group, delete deployments from the history that are no longer needed. Deleting an entry from the deployment history doesn't affect the deployed resources. For more information, see Resolve error when deployment count exceeds 800.

Template limits

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

Virtual Machines limits

Virtual Machines limits

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

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

Virtual Machines limits - Azure Resource Manager

The following limits apply when you use Azure Resource Manager and Azure resource groups.

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

Shared Image Gallery limits

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

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

Virtual machine scale sets limits

Container Instances limits

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

Container Registry limits

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

¹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 Azure Container Registry pricing.

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

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

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

Azure Kubernetes Service limits

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

Azure Machine Learning limits

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

Networking limits

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

Public IP address limits

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.

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

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

ExpressRoute limits

Number of virtual networks per ExpressRoute circuit

*100 Gbps ExpressRoute Direct Only

Virtual WAN limits

Application Gateway limits

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

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

Network Watcher limits

Private Link limits

The following limits apply to Azure private link:

Traffic Manager limits

Azure Bastion limits

*May vary due to other on-going RDP sessions or other on-going SSH sessions.
**May vary if there are existing RDP connections or usage from other on-going SSH sessions.

Azure DNS limits

Public DNS zones

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

Azure Firewall limits

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

Azure Front Door Service limits

Timeout values

Client to Front Door

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

Front Door to application back-end

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

Upload and download data limit

Other limits

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

Storage limits

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

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

² If you have Read-access enabled (RA-GRS/RA-GZRS), the egress targets for the secondary location are identical to those of the primary location. Azure Storage replication options include:

• Locally redundant storage (LRS)
• Zone-redundant storage (ZRS)
• Geo-redundant storage (GRS)
• Read-access geo-redundant storage (RA-GRS)
• Geo-zone-redundant storage (GZRS)
• Read-access geo-zone-redundant storage (RA-GZRS)

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

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

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

Storage resource provider limits

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

Azure Blob storage limits

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

Azure Files limits

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

* Not available in all regions, see Regional availability for a list of available regions.

Azure File Sync limits

Azure Queue storage limits

Azure Table storage limits

Virtual machine disk limits

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

For Azure managed disks:

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

Resource	Default limit	Maximum limit
Standard managed disks	50,000	50,000
Standard SSD managed disks	50,000	50,000
Premium managed disks	50,000	50,000
Standard_LRS snapshots	50,000	50,000
Standard_ZRS snapshots	50,000	50,000
Managed image	50,000	50,000

• For Standard storage accounts: A Standard storage account has a maximum total request rate of 20,000 IOPS. The total IOPS across all of your virtual machine disks in a Standard storage account should not exceed this limit.

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

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

For more information, see Virtual machine sizes.

Managed virtual machine disks

Standard HDD managed disks

Standard SSD managed disks

*Denotes a disk size that is currently in preview, for regional availability information see New disk sizes: Managed and unmanaged.

Premium SSD managed disks: Per-disk limits

*Denotes a disk size that is currently in preview, for regional availability information see New disk sizes: Managed and unmanaged.

**Denotes a feature that is currently in preview, see Disk bursting for more information.

Premium SSD managed disks: Per-VM limits

Unmanaged virtual machine disks

Standard unmanaged virtual machine disks: Per-disk limits

Premium unmanaged virtual machine disks: Per-account limits

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

Premium unmanaged virtual machine disks: Per-disk limits

Premium unmanaged virtual machine disks: Per-VM limits

Azure Cloud Services limits

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

Azure Cognitive Services limits

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

App Service limits

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

¹Apps and storage quotas are per App Service plan unless noted otherwise.
²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.
³Dedicated instances can be of different sizes. For more information, see App Service pricing.
⁴More are allowed upon request.
⁵The storage limit is the total content size across all apps in the same App service plan. The total content size of all apps across all App service plans in a single resource group and region cannot exceed 500GB.
⁶These resources are constrained by physical resources on the dedicated instances (the instance size and the number of instances).
⁷If you scale an app in the Basic tier to two instances, you have 350 concurrent connections for each of the two instances. For Standard tier and above, there are no theoretical limits to web sockets, but other factors can limit the number of web sockets. For example, maximum concurrent requests allowed (defined by maxConcurrentRequestsPerCpu) are: 7,500 per small VM, 15,000 per medium VM (7,500 x 2 cores), and 75,000 per large VM (18,750 x 4 cores).
⁸The maximum IP connections are per instance and depend on the instance size: 1,920 per B1/S1/P1V2 instance, 3,968 per B2/S2/P2V2 instance, 8,064 per B3/S3/P3V2 instance.
⁹The App Service Certificate quota limit per subscription can be increased via a support request to a maximum limit of 200.
¹⁰App Service Isolated SKUs can be internally load balanced (ILB) with Azure Load Balancer, so there's no public connectivity from the internet. As a result, some features of an ILB Isolated App Service must be used from machines that have direct access to the ILB network endpoint.
¹¹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's no predefined limit on the number of WebJobs that can run in an App Service instance. There are practical limits that depend on what the application code is trying to do.

Functions limits

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

Scheduler limits

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

Batch limits

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

BizTalk Services limits

The following table shows the limits for Azure BizTalk Services.

Azure Cosmos DB limits

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

Azure Database for MySQL

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

Azure Database for PostgreSQL

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

Azure Cognitive Search limits

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

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

Limits per subscription

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

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

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

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

Limits per search service

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

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

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

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

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

Media Services limits

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

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

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

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

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

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

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

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

The following table shows the limits on the media reserved units S1, S2, and S3. If your source file is larger than the limits defined in the table, your encoding job fails. If you encode 4K resolution sources of long duration, you're required to use S3 media reserved units to achieve the performance needed. If you have 4K content that's larger than the 260-GB limit on the S3 media reserved units, open a support ticket.

Content Delivery Network limits

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

Mobile Services limits

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

Azure Monitor limits

Alerts

Action groups

Log queries and language

Log Analytics workspaces

Data collection volume and retention

Number of workspaces per subscription.

Azure portal

Data Collector API

Search API

General workspace limits

Data ingestion volume rate

Azure Monitor is a high scale data service that serves thousands of customers sending terabytes of data each month at a growing pace. The default ingestion volume rate limit for data sent from Azure resources using diagnostic settings is approximately 6 GB/min per workspace. This is an approximate value since the actual size can vary between data types depending on the log length and its compression ratio. This limit does not apply to data that is sent from agents or Data Collector API.

If you send data at a higher rate to a single workspace, some data is dropped, and an event is sent to the Operation table in your workspace every 6 hours while the threshold continues to be exceeded. If your ingestion volume continues to exceed the rate limit or you are expecting to reach it sometime soon, you can request an increase to your workspace by opening a support request.

To be notified on such an event in your workspace, create a log alert rule using the following query with alert logic base on number of results grater than zero.

Operation
|where OperationCategory == "Ingestion"
|where Detail startswith "The rate of data crossed the threshold"

Application Insights

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

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

Notification Hubs limits

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

Event Hubs limits

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

The following limits are common across basic, standard, and dedicated tiers.

Event Hubs Basic and Standard - quotas and limits

Event Hubs Dedicated - quotas and limits

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

Service Bus limits

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

IoT Central limits

IoT Central limits the number of applications you can deploy in a subscription to 10. If you need to increase this limit, contact Microsoft support.

IoT Hub limits

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

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

IoT Hub throttles requests when the following quotas are exceeded.

IoT Hub Device Provisioning Service limits

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

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

Data Factory limits

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

Version 2

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

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

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

Version 1

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

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

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

Web service call limits

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

Data Lake Analytics limits

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

Data Lake Store limits

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

Database Migration Service Limits

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

Stream Analytics limits

Active Directory limits

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

Event Grid limits

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

The following limits apply to event domains only.

Azure Maps limits

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

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

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

Azure Policy limits

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

StorSimple System limits

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

Backup limits

The following limits apply to Azure Backup.

Azure SignalR Service limits

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.

API Management limits

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

Azure Cache for Redis limits

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

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

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

Key Vault limits

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

Secrets, managed storage account keys, and vault transactions:

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

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

Multi-Factor Authentication limits

Automation limits

Process automation

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

Change Tracking and Inventory

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

Update Management

The following table shows the limits for Update Management.

Identity Manager limits

Role-based access control limits

SQL Database limits

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

SQL Data Warehouse limits

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

See also

• Understand Azure limits and increases
• Virtual machine and cloud service sizes for Azure
• Sizes for Azure Cloud Services