Note: Azure Pricing changes constantly, so this is just a snapshot of what the pricing is like today, go to the links below to MS Azure website to get the latest pricing information

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.

Managing limits

 Note

Some services have adjustable limits.

When a service doesn’t have adjustable limits, the following tables use the header Limit. In those cases, the default and the maximum limits are the same.

When the limit can be adjusted, the tables include Default limit and Maximum limit headers. The limit can be raised above the default limit but not above the maximum limit.

If you want to raise the limit or quota above the default limit, open an online customer support request at no charge.

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

Some limits are managed at a regional level.

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

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

General limits

For limits on resource names, see Naming rules and restrictions for Azure resources.

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

Management group limits

The following limits apply to management groups.

ResourceLimit
Management groups per directory10,000
Subscriptions per management groupUnlimited.
Levels of management group hierarchyRoot level plus 6 levels1
Direct parent management group per management groupOne
Management group level deployments per location8002

1The 6 levels don’t include the subscription level.

2If you reach the limit of 800 deployments, delete deployments from the history that are no longer needed. To delete management group level deployments, use Remove-AzManagementGroupDeployment or az deployment mg delete.

Subscription limits

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

ResourceLimit
Subscriptions per Azure Active Directory tenantUnlimited.
Coadministrators per subscriptionUnlimited.
Resource groups per subscription980
Azure Resource Manager API request size4,194,304 bytes.
Tags per subscription150
Unique tag calculations per subscription110,000
Subscription-level deployments per location8002

1You can apply up to 50 tags directly to a subscription. However, the subscription can contain an unlimited number of tags that are applied to resource groups and resources within the 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.

2If 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 sub delete.

Resource group limits

ResourceLimit
Resources per resource groupResources aren’t limited by resource group. Instead, they’re limited by resource type in a resource group. See next row.
Resources per resource group, per resource type800 – Some resource types can exceed the 800 limit. See Resources not limited to 800 instances per resource group.
Deployments per resource group in the deployment history8001
Resources per deployment800
Management locks per unique scope20
Number of tags per resource or resource group50
Tag key length512
Tag value length256

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

Template limits

ValueLimit
Parameters256
Variables256
Resources (including copy count)800
Outputs64
Template expression24,576 chars
Resources in exported templates200
Template size4 MB
Parameter file size64 KB

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

Active Directory limits

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

CategoryLimit
DirectoriesA single user can belong to a maximum of 500 Azure AD directories as a member or a guest.
A single user can create a maximum of 200 directories.
DomainsYou can add no more than 900 managed domain names. If you set up all of your domains for federation with on-premises Active Directory, you can add no more than 450 domain names in each directory.
ResourcesA maximum of 50,000 Azure AD resources can be created in a single directory by users of the Free edition of Azure Active Directory by default. If you have at least one verified domain, the default Azure AD service quota for your organization is extended to 300,000 Azure AD resources. This service limit is unrelated to the pricing tier limit of 500,000 resources on the Azure AD pricing page. To go beyond the default quota, you must contact Microsoft Support.A non-admin user can create no more than 250 Azure AD resources. Both active resources and deleted resources that are available to restore count toward this quota. Only deleted Azure AD resources that were deleted fewer than 30 days ago are available to restore. Deleted Azure AD resources that are no longer available to restore count toward this quota at a value of one-quarter for 30 days. If you have developers who are likely to repeatedly exceed this quota in the course of their regular duties, you can create and assign a custom role with permission to create a limitless number of app registrations.
Schema extensionsString-type extensions can have a maximum of 256 characters.Binary-type extensions are limited to 256 bytes.Only 100 extension values, across all types and all applications, can be written to any single Azure AD resource.Only User, Group, TenantDetail, Device, Application, and ServicePrincipal entities can be extended with string-type or binary-type single-valued attributes.Schema extensions are available only in the Graph API version 1.21 preview. The application must be granted write access to register an extension.
ApplicationsA maximum of 100 users can be owners of a single application.
Application ManifestA maximum of 1200 entries can be added in the Application Manifest.
GroupsA user can create a maximum of 250 groups in an Azure AD organization.An Azure AD organization can have a maximum of 5000 dynamic groups.A maximum of 100 users can be owners of a single group.Any number of Azure AD resources can be members of a single group.A user can be a member of any number of groups.The number of members in a group that you can synchronize from your on-premises Active Directory to Azure Active Directory by using Azure AD Connect is limited to 50,000 members.Nested Groups in Azure AD are not supported within all scenarios
At this time the following are the supported scenarios with nested groups.One group can be added as a member of another group and you can achieve group nesting.Group membership claims (when an app is configured to receive group membership claims in the token, nested groups the signed-in user is a member of are included)Conditional access (when scoping a conditional access policy to a group)Restricting access to self-serve password resetRestricting which users can do Azure AD Join and device registration
The following scenarios DO NOT supported nested groups:App role assignment (assigning groups to an app is supported, but groups nested within the directly assigned group will not have access), both for access and for provisioningGroup-based licensing (assigning a license automatically to all members of a group)Office 365 Groups.
Application ProxyA maximum of 500 transactions per second per App Proxy applicationA maximum of 750 transactions per second for the Azure AD organization
A transaction is defined as a single http request and response for a unique resource. When throttled, clients will receive a 429 response (too many requests).
Access PanelThere’s no limit to the number of applications that can be seen in the Access Panel per user. This applies to users assigned licenses for Azure AD Premium or the Enterprise Mobility Suite.A maximum of 10 app tiles can be seen in the Access Panel for each user. This limit applies to users who are assigned licenses for Azure AD Free license plan. Examples of app tiles include Box, Salesforce, or Dropbox. This limit doesn’t apply to administrator accounts.
ReportsA maximum of 1,000 rows can be viewed or downloaded in any report. Any additional data is truncated.
Administrative unitsAn Azure AD resource can be a member of no more than 30 administrative units.
Admin roles and permissionsA group cannot be added as an owner.A group cannot be assigned to a role.Users’ ability to read other users’ directory information cannot be restricted outside of the Azure AD organization-wide switch to disable all non-admin users’ access to all directory information (not recommended). More information on default permissions here.It may take up to 15 minutes or signing out/signing in before admin role membership additions and revocations take effect.

API Management limits

ResourceLimit
Maximum number of scale units10 per region1
Cache size5 GiB per unit2
Concurrent back-end connections3 per HTTP authority2,048 per unit4
Maximum cached response size2 MiB
Maximum policy document size256 KiB5
Maximum custom gateway domains per service instance620
Maximum number of CA certificates per service instance710
Maximum number of service instances per subscription820
Maximum number of subscriptions per service instance8500
Maximum number of client certificates per service instance850
Maximum number of APIs per service instance850
Maximum number of API operations per service instance81,000
Maximum total request duration830 seconds
Maximum buffered payload size82 MiB
Maximum request URL size94096 bytes
Maximum number of self-hosted gateways1025

1Scaling limits depend on the pricing tier. For details on the pricing tiers and their scaling limits, see API Management pricing.
2Per unit cache size depends on the pricing tier. To see the pricing tiers and their scaling limits, see API Management pricing.
3Connections are pooled and reused unless explicitly closed by the back end.
4This limit is per unit of the Basic, Standard, and Premium tiers. The Developer tier is limited to 1,024. This limit doesn’t apply to the Consumption tier.
5This limit applies to the Basic, Standard, and Premium tiers. In the Consumption tier, policy document size is limited to 4 KiB.
6Multiple custom domains are supported in the Developer and Premium tiers only.
7CA certificates are not supported in the Consumption tier.
8This resource applies to the Consumption tier only.
9Applies to the Consumption tier only. Includes an up to 2048 bytes long query string.
10Self-hosted gateways are supported in the Developer and Premium tiers only. The limit applies to the number of self-hosted gateway resources. To raise this limit please contact support. Note, that the number of nodes (or replicas) associated with a self-hosted gateway resource is unlimited in the Premium tier and capped at a single node in the Developer tier.

App Service limits

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

ResourceFreeSharedBasicStandardPremium (v2)Isolated
Web, mobile, or API apps per Azure App Service plan110100Unlimited2Unlimited2Unlimited2Unlimited2
App Service plan10 per region10 per resource group100 per resource group100 per resource group100 per resource group100 per resource group
Compute instance typeSharedSharedDedicated3Dedicated3Dedicated3Dedicated3
Scale out (maximum instances)1 shared1 shared3 dedicated310 dedicated330 dedicated3100 dedicated4
Storage51 GB51 GB510 GB550 GB5250 GB51 TB5
CPU time (5 minutes)63 minutes3 minutesUnlimited, pay at standard ratesUnlimited, pay at standard ratesUnlimited, pay at standard ratesUnlimited, pay at standard rates
CPU time (day)660 minutes240 minutesUnlimited, pay at standard ratesUnlimited, pay at standard ratesUnlimited, pay at standard ratesUnlimited, pay at standard rates
Memory (1 hour)1,024 MB per App Service plan1,024 MB per appN/AN/AN/AN/A
Bandwidth165 MBUnlimited, data transfer rates applyUnlimited, data transfer rates applyUnlimited, data transfer rates applyUnlimited, data transfer rates applyUnlimited, data transfer rates apply
Application architecture32-bit32-bit32-bit/64-bit32-bit/64-bit32-bit/64-bit32-bit/64-bit
Web sockets per instance7535350UnlimitedUnlimitedUnlimited
IP connections600600Depends on instance size8Depends on instance size8Depends on instance size816,000
Concurrent debugger connections per application111555
App Service Certificates per subscription9Not supportedNot supported10101010
Custom domains per app0 (azurewebsites.net subdomain only)500500500500500
Custom domain SSL supportNot supported, wildcard certificate for *.azurewebsites.net available by defaultNot supported, wildcard certificate for *.azurewebsites.net available by defaultUnlimited SNI SSL connectionsUnlimited SNI SSL and 1 IP SSL connections includedUnlimited SNI SSL and 1 IP SSL connections includedUnlimited SNI SSL and 1 IP SSL connections included
Hybrid connections per plan525200200
Integrated load balancerXXXXX10
Always OnXXXX
Scheduled backupsScheduled backups every 2 hours, a maximum of 12 backups per day (manual + scheduled)Scheduled backups every hour, a maximum of 50 backups per day (manual + scheduled)Scheduled backups every hour, a maximum of 50 backups per day (manual + scheduled)
AutoscaleXXX
WebJobs11XXXXXX
Endpoint monitoringXXXX
Staging slots per app52020
SLA99.95%99.95%99.95%99.95%

1Apps and storage quotas are per App Service plan unless noted otherwise.
2The actual number of apps that you can host on these machines depends on the activity of the apps, the size of the machine instances, and the corresponding resource utilization.
3Dedicated instances can be of different sizes. For more information, see App Service pricing.
4More are allowed upon request.
5The storage limit is the total content size across all apps in the same App service plan. The total content size of all apps across all App service plans in a single resource group and region cannot exceed 500GB.
6These resources are constrained by physical resources on the dedicated instances (the instance size and the number of instances).
7If you scale an app in the Basic tier to two instances, you have 350 concurrent connections for each of the two instances. For Standard tier and above, there are no theoretical limits to web sockets, but other factors can limit the number of web sockets. For example, maximum concurrent requests allowed (defined by maxConcurrentRequestsPerCpu) are: 7,500 per small VM, 15,000 per medium VM (7,500 x 2 cores), and 75,000 per large VM (18,750 x 4 cores).
8The 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.
9The App Service Certificate quota limit per subscription can be increased via a support request to a maximum limit of 200.
10App 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.
11Run 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. 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.

Automation limits

Process automation

ResourceLimitNotes
Maximum number of new jobs that can be submitted every 30 seconds per Azure Automation account (nonscheduled jobs)100When this limit is reached, the subsequent requests to create a job fail. The client receives an error response.
Maximum number of concurrent running jobs at the same instance of time per Automation account (nonscheduled jobs)200When this limit is reached, the subsequent requests to create a job fail. The client receives an error response.
Maximum storage size of job metadata for a 30-day rolling period10 GB (approximately 4 million jobs)When this limit is reached, the subsequent requests to create a job fail.
Maximum job stream limit1MBA single stream cannot be larger than 1 MB.
Maximum number of modules that can be imported every 30 seconds per Automation account5
Maximum size of a module100 MB
Job run time, Free tier500 minutes per subscription per calendar month
Maximum amount of disk space allowed per sandbox11 GBApplies to Azure sandboxes only.
Maximum amount of memory given to a sandbox1400 MBApplies to Azure sandboxes only.
Maximum number of network sockets allowed per sandbox11,000Applies to Azure sandboxes only.
Maximum runtime allowed per runbook13 hoursApplies to Azure sandboxes only.
Maximum number of Automation accounts in a subscriptionNo limit
Maximum number of Hybrid Worker Groups per Automation Account4,000
Maximum number of concurrent jobs that can be run on a single Hybrid Runbook Worker50
Maximum runbook job parameter size512 kilobits
Maximum runbook parameters50If you reach the 50-parameter limit, you can pass a JSON or XML string to a parameter and parse it with the runbook.
Maximum webhook payload size512 kilobits
Maximum days that job data is retained30 days
Maximum PowerShell workflow state size5 MBApplies to PowerShell workflow runbooks when checkpointing workflow.

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

Change Tracking and Inventory

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

ResourceLimitNotes
File500
Registry250
Windows software250Doesn’t include software updates.
Linux packages1,250
Services250
Daemon250

Update Management

The following table shows the limits for Update Management.

ResourceLimitNotes
Number of machines per update deployment1000

Azure Cache for Redis limits

ResourceLimit
Cache size1.2 TB
Databases64
Maximum connected clients40,000
Azure Cache for Redis replicas, for high availability1
Shards in a premium cache with clustering10

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.

Azure Cloud Services limits

ResourceLimit
Web or worker roles per deployment125
Instance input endpoints per deployment25
Input endpoints per deployment25
Internal endpoints per deployment25
Hosted service certificates per deployment199

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

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

ResourceFree1BasicS1S2S3S3 HDL1L2
Maximum services1161686666
Maximum scale in search units (SU)2N/A3 SU36 SU36 SU36 SU36 SU36 SU36 SU

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

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

Limits per search service

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

ResourceFreeBasic1S1S2S3S3 HD2L1L2
Service level agreement (SLA)3NoYesYesYesYesYesYesYes
Storage per partition50 MB2 GB25 GB100 GB200 GB200 GB1 TB2 TB
Partitions per serviceN/A112121231212
Partition sizeN/A2 GB25 GB100 GB200 GB200 GB1 TB2 TB
ReplicasN/A3121212121212

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

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

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

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

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.

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

Azure Cosmos DB limits

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

Azure Data Explorer limits

The following table describes the maximum limits for Azure Data Explorer clusters.

ResourceLimit
Clusters per region per subscription20
Instances per cluster1000
Number of databases in a cluster10,000
Number of attached database configurations in a cluster70

The following table describes the limits on management operations performed on Azure Data Explorer clusters.

ScopeOperationLimit
Clusterread (for example, get a cluster)500 per 5 minutes
Clusterwrite (for example, create a database)1000 per hour

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 Functions limits

ResourceConsumption planPremium planApp Service plan1
Scale outEvent drivenEvent drivenManual/autoscale
Max instances20010010-20
Default timeout duration (min)530302
Max timeout duration (min)10unbounded8unbounded3
Max outbound connections (per instance)600 active (1200 total)unboundedunbounded
Max request size (MB)4100100100
Max query string length4409640964096
Max request URL length4819281928192
ACU per instance100210-840100-840
Max memory (GB per instance)1.53.5-141.75-14
Function apps per plan100100unbounded5
App Service plans100 per region100 per resource group100 per resource group
Storage61 GB250 GB50-1000 GB
Custom domains per app5007500500
Custom domain SSL supportunbounded SNI SSL connection includedunbounded SNI SSL and 1 IP SSL connections includedunbounded SNI SSL and 1 IP SSL connections included

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

Azure Kubernetes Service limits

ResourceLimit
Maximum clusters per subscription100
Maximum nodes per cluster with Virtual Machine Availability Sets and Basic Load Balancer SKU100
Maximum nodes per cluster with Virtual Machine Scale Sets and Standard Load Balancer SKU1000 (100 nodes per node pool)
Maximum pods per node: Basic networking with Kubenet110
Maximum pods per node: Advanced networking with Azure Container Networking InterfaceAzure CLI deployment: 301
Azure Resource Manager template: 301
Portal deployment: 30

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

Azure Machine Learning limits

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

Azure Maps limits

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

ResourceS0 pricing tier limit
Maximum request rate per subscription50 requests per second

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

ResourceLimit
Maximum size of data50 MB

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

Azure Monitor limits

Alerts

ResourceDefault limitMaximum limit
Metric alerts (classic)100 active alert rules per subscription.Call support.
Metric alerts2,000 active alert rules per subscription in Azure public, Azure China 21Vianet and Azure Government clouds.Call support.
Activity log alerts100 active alert rules per subscription.Same as default.
Log alerts512 active alert rules per subscription. 200 active alert rules per resource.Call support.
Action groups2,000 action groups per subscription.Call support.
Autoscale settings100 per region per subscription.Same as default.

Action groups

ResourceDefault limitMaximum limit
Azure app push10 Azure app actions per action group.Call support.
Email1,000 email actions in an action group.
No more than 100 emails in an hour.
Also see the rate limiting information.
Call support.
ITSM10 ITSM actions in an action group.Call support.
Logic app10 logic app actions in an action group.Call support.
Runbook10 runbook actions in an action group.Call support.
SMS10 SMS actions in an action group.
No more than 1 SMS message every 5 minutes.
Also see the rate limiting information.
Call support.
Voice10 voice actions in an action group.
No more than 1 voice call every 5 minutes.
Also see the rate limiting information.
Call support.
Webhook10 webhook actions in an action group. Maximum number of webhook calls is 1500 per minute per subscription. Other limits are available at action-specific information.Call support.

Log queries and language

General query limits

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

User query throttling

Azure Monitor has several throttling limits to protect against users sending an excessive number of queries. Such behavior can potentially overload the system backend resources and jeopardize service responsiveness. The following limits are designed to protect customers from interruptions and ensure consistent service level. The user throttling and limits are designed to impact only extreme usage scenario and should not be relevant for typical usage.

MeasureLimit per userDescription
Concurrent queries5If there are already 5 queries running for the user, any new queries are placed in a per-user concurrency queue. When one of the running queries ends, the next query will be pulled from the queue and started. This does not include queries from alert rules.
Time in concurrency queue2.5 minutesIf a query sits in the queue for more than 2.5 minutes without being started, it will be terminated with an HTTP error response with code 429.
Total queries in concurrency queue40Once the number of queries in the queue reaches 40, any additional queries will by rejected with an HTTP error code 429. This number is in addition to the 5 queries that can be running simultaneously.
Query rate200 queries per 30 secondsThis is the overall rate that queries can be submitted by a single user to all workspaces. This limit applies to programmatic queries or queries initiated by visualization parts such as Azure dashboards and the Log Analytics workspace summary page.
  • Optimize your queries as described in Optimize log queries in Azure Monitor.
  • Dashboards and workbooks can contain multiple queries in a single view that generate a burst of queries every time they load or refresh. Consider breaking them up into multiple views that load on demand.
  • In Power BI, consider extracting only aggregated results rather than raw logs.

Log Analytics workspaces

Data collection volume and retention

TierLimit per dayData retentionComment
Current Per GB pricing tier
(introduced April 2018)
No limit30 – 730 daysData retention beyond 31 days is available for additional charges. Learn more about Azure Monitor pricing.
Legacy Free tiers
(introduced April 2016)
500 MB7 daysWhen your workspace reaches the 500 MB per day limit, data ingestion stops and resumes at the start of the next day. A day is based on UTC. Note that data collected by Azure Security Center is not included in this 500 MB per day limit and will continue to be collected above this limit.
Legacy Standalone Per GB tier
(introduced April 2016)
No limit30 to 730 daysData retention beyond 31 days is available for additional charges. Learn more about Azure Monitor pricing.
Legacy Per Node (OMS)
(introduced April 2016)
No limit30 to 730 daysData retention beyond 31 days is available for additional charges. Learn more about Azure Monitor pricing.
Legacy Standard tierNo limit30 daysRetention can’t be adjusted
Legacy Premium tierNo limit365 daysRetention can’t be adjusted

Number of workspaces per subscription.

Pricing tierWorkspace limitComments
Free tier10This limit can’t be increased.
All other tiersNo limitYou’re limited by the number of resources within a resource group and the number of resource groups per subscription.

Azure portal

CategoryLimitComments
Maximum records returned by a log query10,000Reduce results using query scope, time range, and filters in the query.

Data Collector API

CategoryLimitComments
Maximum size for a single post30 MBSplit larger volumes into multiple posts.
Maximum size for field values32 KBFields longer than 32 KB are truncated.

Search API

CategoryLimitComments
Maximum records returned in a single query500,000
Maximum size of data returned64,000,000 bytes (~61 MiB)
Maximum query running time10 minutesSee Timeouts for details.
Maximum request rate200 requests per 30 seconds per AAD user or client IP addressSee Rate limits for details.

General workspace limits

CategoryLimitComments
Maximum columns in a table500
Maximum characters for column name500
Data exportNot currently availableUse Azure Function or Logic App to aggregate and export data.

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 sending an email to LAIngestionRate@microsoft.com or 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.KustoCopy

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

 Note

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

Application Insights

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

ResourceLimitNote
Total data per day100 GBYou can reduce data by setting a cap. If you need more data, you can increase the limit in the portal, up to 1,000 GB. For capacities greater than 1,000 GB, send email to AIDataCap@microsoft.com.
Throttling32,000 events/secondThe limit is measured over a minute.
Data retention90 daysThis resource is for SearchAnalytics, and Metrics Explorer.
Availability multi-step test detailed results retention90 daysThis resource provides detailed results of each step.
Maximum event size64,000,000 bytes
Property and metric name length150See type schemas.
Property value string length8,192See type schemas.
Trace and exception message length32,768See type schemas.
Availability tests count per app100
Profiler data retention5 days
Profiler data sent per day10 GB

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

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.

WhereWhatMaximum count
ScopePolicy definitions500
ScopeInitiative definitions100
TenantInitiative definitions1,000
ScopePolicy or initiative assignments100
Policy definitionParameters20
Initiative definitionPolicies100
Initiative definitionParameters100
Policy or initiative assignmentsExclusions (notScopes)400
Policy ruleNested conditionals512
Remediation taskResources500

Azure SignalR Service limits

ResourceDefault limitMaximum limit
Azure SignalR Service units per instance for Free tier11
Azure SignalR Service units per instance for Standard tier100100
Azure SignalR Service units per subscription per region for Free tier55
Total Azure SignalR Service unit counts per subscription per region150Unlimited
Connections per unit per day for Free tier2020
Connections per unit per day for Standard tier1,0001,000
Included messages per unit per day for Free tier20,00020,000
Included messages per unit per day for Standard tier1,000,0001,000,000

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

Backup limits

For a summary of Azure Backup support settings and limitations, see Azure Backup Support Matrices.

Batch limits

ResourceDefault limitMaximum limit
Azure Batch accounts per region per subscription1-350
Dedicated cores per Batch account90-900Contact support
Low-priority cores per Batch account10-100Contact support
Active jobs and job schedules per Batch account (completed jobs have no limit)100-3001,0001
Pools per Batch account20-1005001

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

 Note

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

 Important

To help us better manage capacity during the global health pandemic, the default core quotas for new Batch accounts in some regions and for some types of subscription have been reduced from the above range of values, in some cases to zero cores. When you create a new Batch account, check your core quota and request a core quota increase, if required.

Classic deployment model limits

If you use classic deployment model instead of the Azure Resource Manager deployment model, the following limits apply.

ResourceDefault limitMaximum limit
vCPUs per subscription12010,000
Coadministrators per subscription200200
Storage accounts per subscription2100100
Cloud services per subscription20200
Local networks per subscription10500
DNS servers per subscription9100
Reserved IPs per subscription20100
Affinity groups per subscription256256
Subscription name length (characters)6464

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

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

Container Instances limits

ResourceLimit
Standard sku container groups per region per subscription1001
Dedicated sku container groups per region per subscription01
Number of containers per container group60
Number of volumes per container group20
Ports per IP5
Container instance log size – running instance4 MB
Container instance log size – stopped instance16 KB or 1,000 lines
Container creates per hour3001
Container creates per 5 minutes1001
Container deletes per hour3001
Container deletes per 5 minutes1001

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

Container Registry limits

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

ResourceBasicStandardPremium
Storage110 GiB100 GiB500 GiB
Maximum image layer size200 GiB200 GiB200 GiB
ReadOps per minute2, 31,0003,00010,000
WriteOps per minute2, 41005002,000
Download bandwidth MBps23060100
Upload bandwidth MBps2102050
Webhooks210500
Geo-replicationN/AN/ASupported
Content trustN/AN/ASupported
Virtual network accessN/AN/APreview
Private link integrationN/AN/APreview
Customer-managed keysN/AN/APreview
Repository-scoped permissionsN/AN/APreview
• TokensN/AN/A20,000
• Scope mapsN/AN/A20,000
• Repositories per scope mapN/AN/A500

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

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

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

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

Content Delivery Network limits

ResourceLimit
Azure Content Delivery Network profiles25
Content Delivery Network endpoints per profile25
Custom domains per endpoint25

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.

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

ResourceDefault limitMaximum limit
Data factories in an Azure subscription800Contact support.
Total number of entities, such as pipelines, data sets, triggers, linked services, and integration runtimes, within a data factory5,000Contact support.
Total CPU cores for Azure-SSIS Integration Runtimes under one subscription256Contact support.
Concurrent pipeline runs per data factory that’s shared among all pipelines in the factory10,000Contact support.
Concurrent External activity runs per subscription per Azure Integration Runtime region
External activities are managed on integration runtime but execute on linked services, including Databricks, stored procedure, HDInsights, Web, and others.
3000Contact support.
Concurrent Pipeline activity runs per subscription per Azure Integration Runtime region
Pipeline activities execute on integration runtime, including Lookup, GetMetadata, and Delete.
1000Contact support.
Concurrent authoring operations per subscription per Azure Integration Runtime region
Including test connection, browse folder list and table list, preview data.
200Contact support.
Concurrent Data Integration Units1 consumption per subscription per Azure Integration Runtime regionRegion group 12: 6000
Region group 22: 3000
Region group 32: 1500
Contact support.
Maximum activities per pipeline, which includes inner activities for containers4040
Maximum number of linked integration runtimes that can be created against a single self-hosted integration runtime100Contact support.
Maximum parameters per pipeline5050
ForEach items100,000100,000
ForEach parallelism2050
Maximum queued runs per pipeline100100
Characters per expression8,1928,192
Minimum tumbling window trigger interval15 min15 min
Maximum timeout for pipeline activity runs7 days7 days
Bytes per object for pipeline objects3200 KB200 KB
Bytes per object for dataset and linked service objects3100 KB2,000 KB
Data Integration Units1 per copy activity run256Contact support.
Write API calls1,200/h

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

This limit is imposed by Azure Resource Manager, not Azure Data Factory.
Contact support.
Monitoring queries per minute1,000Contact support.
Entity CRUD operations per minute50Contact support.
Maximum time of data flow debug session8 hrs8 hrs
Concurrent number of data flows per factory50Contact support.
Concurrent number of data flow debug sessions per user per factory33
Data Flow Azure IR TTL limit4 hrsContact support.

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

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

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

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

Version 1

ResourceDefault limitMaximum limit
Pipelines within a data factory2,500Contact support.
Data sets within a data factory5,000Contact support.
Concurrent slices per data set1010
Bytes per object for pipeline objects1200 KB200 KB
Bytes per object for data set and linked service objects1100 KB2,000 KB
Azure HDInsight on-demand cluster cores within a subscription260Contact support.
Cloud data movement units per copy activity run332Contact support.
Retry count for pipeline activity runs1,000MaxInt (32 bit)

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

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

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

ResourceDefault lower limitMinimum limit
Scheduling interval15 minutes15 minutes
Interval between retry attempts1 second1 second
Retry timeout value1 second1 second

Web service call limits

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

Data Lake Analytics limits

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

ResourceLimitComments
Maximum number of concurrent jobs20
Maximum number of analytics units (AUs) per account250Use any combination of up to a maximum of 250 AUs across 20 jobs. To increase this limit, contact Microsoft Support.
Maximum script size for job submission3 MB
Maximum number of Data Lake Analytics accounts per region per subscription5To increase this limit, contact Microsoft Support.

Data Lake Store limits

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

ResourceLimitComments
Maximum number of Data Lake Storage Gen1 accounts, per subscription, per region10To request an increase for this limit, contact support.
Maximum number of access ACLs, per file or folder32This is a hard limit. Use groups to manage access with fewer entries.
Maximum number of default ACLs, per file or folder32This is a hard limit. Use groups to manage access with fewer entries.

Data Share limits

Azure Data Share enables organizations to simply and securely share data with their customers and partners.

ResourceLimit
Maximum number of Data Share resources per Azure subscription50
Maximum number of sent shares per Data Share resource100
Maximum number of received shares per Data Share resource100
Maximum number of invitations per sent share100
Maximum number of share subscriptions per sent share100
Maximum number of datasets per share100
Maximum number of snapshot schedules per share1

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.

ResourceLimitComments
Maximum number of services per subscription, per region2To request an increase for this limit, contact support.

Event Grid limits

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

ResourceLimit
Custom topics per Azure subscription100
Event subscriptions per topic500
Publish rate for a custom topic (ingress)5,000 events per second per topic
Publish requests250 per second
Event size1 MB. Operations are charged in 64 KB increments though. So, events over 64 KB will incur operations charges as though they were multiple events. For example, an event that is 130 KB would incur operations as though it were 3 separate events.

The following limits apply to event domains only.

ResourceLimit
Topics per event domain100,000
Event subscriptions per topic within a domain500
Domain scope event subscriptions50
Publish rate for an event domain (ingress)5,000 events per second
Publish requests250 per second
Event Domains per Azure Subscription100

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.

LimitScopeNotesValue
Number of Event Hubs namespaces per subscriptionSubscription100
Number of event hubs per namespaceNamespaceSubsequent requests for creation of a new event hub are rejected.10
Number of partitions per event hubEntity32
Maximum size of an event hub nameEntity50 characters
Number of non-epoch receivers per consumer groupEntity5
Maximum throughput unitsNamespaceExceeding the throughput unit limit causes your data to be throttled and generates a server busy exception. To request a larger number of throughput units for a Standard tier, file a support requestAdditional throughput units are available in blocks of 20 on a committed purchase basis.20
Number of authorization rules per namespaceNamespaceSubsequent requests for authorization rule creation are rejected.12
Number of calls to the GetRuntimeInformation methodEntity50 per second
Number of virtual network (VNet) and IP Config rulesEntity128

Event Hubs Basic and Standard – quotas and limits

LimitScopeNotesBasicStandard
Maximum size of Event Hubs eventEntity 256 KB1 MB
Number of consumer groups per event hubEntity 120
Number of AMQP connections per namespaceNamespaceSubsequent requests for additional connections are rejected, and an exception is received by the calling code.1005,000
Maximum retention period of event dataEntity 1 day1-7 days
Apache Kafka enabled namespaceNamespaceEvent Hubs namespace streams applications using Kafka protocolNoYes
CaptureEntityWhen enabled, micro-batches on the same streamNoYes

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.

FeatureLimits
Bandwidth20 CUs
Namespaces50 per CU
Event Hubs1000 per namespace
Ingress eventsIncluded
Message Size1 MB
Partitions2000 per CU
Consumer groupsNo limit per CU, 1000 per event hub
Brokered connections100 K included
Message Retention90 days, 10 TB included per CU
CaptureIncluded

Identity Manager limits

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

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.

ResourceS1 StandardS2 StandardS3 StandardF1 Free
Messages/day400,0006,000,000300,000,0008,000
Maximum units200200101

 Note

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

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

ResourceLimit
Maximum paid IoT hubs per Azure subscription50
Maximum free IoT hubs per Azure subscription1
Maximum number of characters in a device ID128
Maximum number of device identities
returned in a single call
1,000
IoT Hub message maximum retention for device-to-cloud messages7 days
Maximum size of device-to-cloud message256 KB
Maximum size of device-to-cloud batchAMQP and HTTP: 256 KB for the entire batch
MQTT: 256 KB for each message
Maximum messages in device-to-cloud batch500
Maximum size of cloud-to-device message64 KB
Maximum TTL for cloud-to-device messages2 days
Maximum delivery count for cloud-to-device
messages
100
Maximum cloud-to-device queue depth per device50
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 twin8 KB for tags section, and 32 KB for desired and reported properties sections each
Maximum length of device twin string key1 KB
Maximum length of device twin string value4 KB
Maximum depth of object in device twin10
Maximum size of direct method payload128 KB
Job history maximum retention30 days
Maximum concurrent jobs10 (for S3), 5 for (S2), 1 (for S1)
Maximum additional endpoints10 (for S1, S2, and S3)
Maximum message routing rules100 (for S1, S2, and S3)
Maximum number of concurrently connected device streams50 (for S1, S2, S3, and F1 only)
Maximum device stream data transfer300 MB per day (for S1, S2, S3, and F1 only)

 Note

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

 Note

Currently, the total number of devices plus modules that can be registered to a single IoT hub is capped at 1,000,000. If you want to increase this limit, contact Microsoft Support.

IoT Hub throttles requests when the following quotas are exceeded.

ThrottlePer-hub value
Identity registry operations
(create, retrieve, list, update, and delete),
individual or bulk import/export
83.33/sec/unit (5,000/min/unit) (for S3).
1.67/sec/unit (100/min/unit) (for S1 and S2).
Device connections6,000/sec/unit (for S3), 120/sec/unit (for S2), 12/sec/unit (for S1).
Minimum of 100/sec.
Device-to-cloud sends6,000/sec/unit (for S3), 120/sec/unit (for S2), 12/sec/unit (for S1).
Minimum of 100/sec.
Cloud-to-device sends83.33/sec/unit (5,000/min/unit) (for S3), 1.67/sec/unit (100/min/unit) (for S1 and S2).
Cloud-to-device receives833.33/sec/unit (50,000/min/unit) (for S3), 16.67/sec/unit (1,000/min/unit) (for S1 and S2).
File upload operations83.33 file upload initiations/sec/unit (5,000/min/unit) (for S3), 1.67 file upload initiations/sec/unit (100/min/unit) (for S1 and S2).
10,000 SAS URIs can be out for an Azure Storage account at one time.
10 SAS URIs/device can be out at one time.
Direct methods24 MB/sec/unit (for S3), 480 KB/sec/unit (for S2), 160 KB/sec/unit (for S1).
Based on 8-KB throttling meter size.
Device twin reads500/sec/unit (for S3), Maximum of 100/sec or 10/sec/unit (for S2), 100/sec (for S1)
Device twin updates250/sec/unit (for S3), Maximum of 50/sec or 5/sec/unit (for S2), 50/sec (for S1)
Jobs operations
(create, update, list, and delete)
83.33/sec/unit (5,000/min/unit) (for S3), 1.67/sec/unit (100/min/unit) (for S2), 1.67/sec/unit (100/min/unit) (for S1).
Jobs per-device operation throughput50/sec/unit (for S3), maximum of 10/sec or 1/sec/unit (for S2), 10/sec (for S1).
Device stream initiation rate5 new streams/sec (for S1, S2, S3, and F1 only).

IoT Hub Device Provisioning Service limits

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

ResourceLimit
Maximum device provisioning services per Azure subscription10
Maximum number of enrollments1,000,000
Maximum number of registrations1,000,000
Maximum number of enrollment groups100
Maximum number of CAs25
Maximum number of linked IoT hubs50
Maximum size of message96 KB

 Note

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

 Note

Increasing the maximum number of CAs is not supported.

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

ThrottlePer-unit value
Operations200/min/service
Device registrations200/min/service
Device polling operation5/10 sec/device

Key Vault limits

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

Key typeHSM key
CREATE key
HSM key
All other transactions
Software key
CREATE key
Software key
All other transactions
RSA 2,048-bit51,000102,000
RSA 3,072-bit525010500
RSA 4,096-bit512510250
ECC P-25651,000102,000
ECC P-38451,000102,000
ECC P-52151,000102,000
ECC SECP256K151,000102,000

 Note

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

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

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

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

Secrets, managed storage account keys, and vault transactions:

Transactions typeMaximum transactions allowed in 10 seconds, per vault per region1
All transactions2,000

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

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

ResourceLimit
Private endpoints per key vault64
Key vaults with private endpoints per subscription64

Media Services limits

 Note

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

Account limits

ResourceDefault Limit
Media Services accounts in a single subscription25 (fixed)

Asset limits

ResourceDefault Limit
Assets per Media Services account1,000,000

Storage (media) limits

ResourceDefault Limit
File sizeIn some scenarios, there is a limit on the maximum file size supported for processing in Media Services. (1)
Storage accounts100(2) (fixed)

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

Media reserved unit typeMaximum input size (GB)
S126
S260
S3260

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

Jobs (encoding & analyzing) limits

ResourceDefault Limit
Jobs per Media Services account500,000 (3) (fixed)
Job inputs per Job50 (fixed)
Job outputs per Job20 (fixed)
Transforms per Media Services account100 (fixed)
Transform outputs in a Transform20 (fixed)
Files per job input10 (fixed)

3 This number includes queued, finished, active, and canceled Jobs. It does not include deleted Jobs.

Any Job record in your account older than 90 days will be automatically deleted, even if the total number of records is below the maximum quota.

Live streaming limits

ResourceDefault Limit
Live Events (4) per Media Services account5
Live Outputs per Live Event(5)
Max Live Output duration25 hours

4 For detailed information about Live Event limitations, see Live Event types comparison and limitations.

5 Live Outputs start on creation and stop when deleted.

Packaging & delivery limits

ResourceDefault Limit
Streaming Endpoints (stopped or running) per Media Services account2 (fixed)
Dynamic Manifest Filters100
Streaming Policies100 (6)
Unique Streaming Locators associated with an Asset at one time100(7) (fixed)

6 When using a custom Streaming Policy, you should design a limited set of such policies for your Media Service account, and re-use them for your StreamingLocators whenever the same encryption options and protocols are needed. You should not be creating a new Streaming Policy for each Streaming Locator.

7 Streaming Locators are not designed for managing per-user access control. To give different access rights to individual users, use Digital Rights Management (DRM) solutions.

Protection limits

ResourceDefault Limit
Options per Content Key Policy30
Licenses per month for each of the DRM types on Media Services key delivery service per account1,000,000

Support ticket

For resources that are not fixed, you may ask for the quotas to be raised, by opening a support ticket. Include detailed information in the request on the desired quota changes, use-case scenarios, and regions required.
Do not create additional Azure Media Services accounts in an attempt to obtain higher limits.

Media Services v2 (legacy)

For limits specific to Media Services v2 (legacy), see Media Services v2 (legacy)

Mobile Services limits

TierFreeBasicStandard
API calls500,0001.5 million per unit15 million per unit
Active devices500UnlimitedUnlimited
ScaleN/AUp to 6 unitsUnlimited units
Push notificationsAzure Notification Hubs Free tier included, up to 1 million pushesNotification Hubs Basic tier included, up to 10 million pushesNotification Hubs Standard tier included, up to 10 million pushes
Real-time messaging/
Web Sockets
Limited350 per mobile serviceUnlimited
Offline synchronizationsLimitedIncludedIncluded
Scheduled jobsLimitedIncludedIncluded
Azure SQL Database (required)
Standard rates apply for additional capacity
20 MB included20 MB included20 MB included
CPU capacity60 minutes per dayUnlimitedUnlimited
Outbound data transfer165 MB per day (daily rollover)IncludedIncluded

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

Multi-Factor Authentication limits

ResourceDefault limitMaximum limit
Maximum number of trusted IP addresses or ranges per subscription050
Remember my devices, number of days1460
Maximum number of app passwords0No limit
Allow X attempts during MFA call199
Two-way text message timeout seconds60600
Default one-time bypass seconds3001,800
Lock user account after X consecutive MFA denialsNot set99
Reset account lockout counter after X minutesNot set9,999
Unlock account after X minutesNot set9,999

Networking limits

Networking limits – Azure Resource Manager

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

 Note

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

ResourceLimit
Virtual networks1,000
Subnets per virtual network3,000
Virtual network peerings per virtual network500
Virtual network gateways (VPN gateways) per virtual network1
Virtual network gateways (ExpressRoute gateways) per virtual network1
DNS servers per virtual network20
Private IP addresses per virtual network65,536
Private IP addresses per network interface256
Private IP addresses per virtual machine256
Public IP addresses per network interface256
Public IP addresses per virtual machine256
Concurrent TCP or UDP flows per NIC of a virtual machine or role instance500,000
Network interface cards65,536
Network Security Groups5,000
NSG rules per NSG1,000
IP addresses and ranges specified for source or destination in a security group4,000
Application security groups3,000
Application security groups per IP configuration, per NIC20
IP configurations per application security group4,000
Application security groups that can be specified within all security rules of a network security group100
User-defined route tables200
User-defined routes per route table400
Point-to-site root certificates per Azure VPN Gateway20
Virtual network TAPs100
Network interface TAP configurations per virtual network TAP100

Public IP address limits

ResourceDefault limitMaximum limit
Public IP addresses110 for Basic.Contact support.
Static Public IP addresses110 for Basic.Contact support.
Standard Public IP addresses110Contact support.
Public IP Prefixeslimited by number of Standard Public IPs in a subscriptionContact support.
Public IP prefix length/28Contact support.

1Default limits for Public IP addresses vary by offer category type, such as Free Trial, Pay-As-You-Go, CSP. For example, the default for Enterprise Agreement subscriptions is 1000.

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.

Standard Load Balancer

ResourceLimit
Load balancers1,000
Rules per resource1,500
Rules per NIC (across all IPs on a NIC)300
Frontend IP configurations600
Backend pool size1,000 IP configurations, single virtual network
Backend resources per Load Balancer 1150
High-availability ports1 per internal frontend
Outbound rules per Load Balancer600
TCP idle timeout4 minutes/30 minutes

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

Basic Load Balancer

ResourceLimit
Load balancers1,000
Rules per resource250
Rules per NIC (across all IPs on a NIC)300
Frontend IP configurations200
Backend pool size300 IP configurations, single availability set
Availability sets per Load Balancer150

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.

ResourceDefault limitMaximum limit
Virtual networks100100
Local network sites2050
DNS servers per virtual network2020
Private IP addresses per virtual network4,0964,096
Concurrent TCP or UDP flows per NIC of a virtual machine or role instance500,000, up to 1,000,000 for two or more NICs.500,000, up to 1,000,000 for two or more NICs.
Network Security Groups (NSGs)200200
NSG rules per NSG1,0001,000
User-defined route tables200200
User-defined routes per route table400400
Public IP addresses (dynamic)500500
Reserved public IP addresses500500
Public VIP per deployment5Contact support
Private VIP (internal load balancing) per deployment11
Endpoint access control lists (ACLs)5050

ExpressRoute limits

ResourceLimit
ExpressRoute circuits per subscription10
ExpressRoute circuits per region per subscription, with Azure Resource Manager10
Maximum number of routes advertised to Azure private peering with ExpressRoute Standard4,000
Maximum number of routes advertised to Azure private peering with ExpressRoute Premium add-on10,000
Maximum number of routes advertised from Azure private peering from the VNet address space for an ExpressRoute connection200
Maximum number of routes advertised to Microsoft peering with ExpressRoute Standard200
Maximum number of routes advertised to Microsoft peering with ExpressRoute Premium add-on200
Maximum number of ExpressRoute circuits linked to the same virtual network in the same peering location4
Maximum number of ExpressRoute circuits linked to the same virtual network in different peering locations4
Number of virtual network links allowed per ExpressRoute circuitSee the Number of virtual networks per ExpressRoute circuit table.

Number of virtual networks per ExpressRoute circuit

Circuit sizeNumber of virtual network links for StandardNumber of virtual network links with Premium add-on
50 Mbps1020
100 Mbps1025
200 Mbps1025
500 Mbps1040
1 Gbps1050
2 Gbps1060
5 Gbps1075
10 Gbps10100
40 Gbps*10100
100 Gbps*10100

*100 Gbps ExpressRoute Direct Only

 Note

Global Reach connections count against the limit of virtual network connections per ExpressRoute Circuit. For example, a 10 Gbps Premium Circuit would allow for 5 Global Reach connections and 95 connections to the ExpressRoute Gateways or 95 Global Reach connections and 5 connections to the ExpressRoute Gateways or any other combination up to the limit of 100 connections for the circuit.

Virtual WAN limits

ResourceLimit
Virtual WAN hubs per region1
Virtual WAN hubs per virtual wanAzure regions
VPN (branch) connections per hub1,000
VNet connections per hub500
Point-to-Site users per hub10,000
Aggregate throughput per Virtual WAN VPN gateway20 Gbps
Throughput per Virtual WAN VPN connection (2 tunnels)2 Gbps with 1 Gbps/IPsec tunnel
Aggregate throughput per Virtual WAN ExpressRoute gateway20 Gbps

Application Gateway limits

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

ResourceLimitNote
Azure Application Gateway1,000 per subscription
Front-end IP configurations21 public and 1 private
Front-end ports1001
Back-end address pools1001
Back-end servers per pool1,200
HTTP listeners2001Limited to 100 active listeners that are routing traffic. Active listeners = total number of listeners – listeners not active.
If a default configuration inside a routing rule is set to route traffic (for example, it has a listener, a backend pool, and HTTP settings) then that also counts as a listener.
HTTP load-balancing rules1001
Back-end HTTP settings1001
Instances per gatewayV1 SKU – 32
V2 SKU – 125
SSL certificates10011 per HTTP listener
Maximum SSL certificate sizeV1 SKU – 10 KB
V2 SKU – 16 KB
Authentication certificates100
Trusted root certificates100
Request timeout minimum1 second
Request timeout maximum24 hours
Number of sites10011 per HTTP listener
URL maps per listener1
Maximum path-based rules per URL map100
Redirect configurations1001
Concurrent WebSocket connectionsMedium gateways 20k
Large gateways 50k
Maximum URL length32KB
Maximum header size for HTTP/24KB
Maximum file upload size, Standard2 GB
Maximum file upload size WAFV1 Medium WAF gateways, 100 MB
V1 Large WAF gateways, 500 MB
V2 WAF, 750 MB
WAF body size limit, without files128 KB
Maximum WAF custom rules100
Maximum WAF exclusions100

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

Network Watcher limits

ResourceLimitNote
Azure Network Watcher1 per regionNetwork Watcher is created to enable access to the service. Only one instance of Network Watcher is required per subscription per region.
Packet capture sessions10,000 per regionNumber of sessions only, not saved captures.

The following limits apply to Azure private link:

ResourceLimit
Number of private endpoints per virtual network1000
Number of private endpoints per subscription     64000
Number of private link service per subscription      800
Number of IP Configurations on a private link service   8 (This number is for the NAT IP addresses used per PLS)
Number of private endpoints on the same private link service 1000
Number of private endpoints per key vault64
Number of key vaults with private endpoints per subscription64

Traffic Manager limits

ResourceLimit
Profiles per subscription200
Endpoints per profile200

Azure Bastion limits

ResourceLimit
Concurrent RDP connections25*
Concurrent SSH connections50**

*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

ResourceLimit
Public DNS Zones per subscription250 1
Record sets per public DNS zone10,000 1
Records per record set in public DNS zone20
Number of Alias records for a single Azure resource20
Private DNS zones per subscription1000
Record sets per private DNS zone25000
Records per record set for private DNS zones20
Virtual Network Links per private DNS zone1000
Virtual Networks Links per private DNS zones with auto-registration enabled100
Number of private DNS zones a virtual network can get linked to with auto-registration enabled1
Number of private DNS zones a virtual network can get linked1000
Number of DNS queries a virtual machine can send to Azure DNS resolver, per second500 2
Maximum number of DNS queries queued (pending response) per virtual machine200 2

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

2These limits are applied to every individual virtual machine and not at the virtual network level. DNS queries exceeding these limits are dropped.

Azure Firewall limits

ResourceLimit
Data throughput30 Gbps1
Rules10,000. All rule types combined.
Maximum DNAT rules298
If a rule’s protocol is configured for both TCP and UDP, it counts as two rules.
Minimum AzureFirewallSubnet size/26
Port range in network and application rules1 – 65535
Public IP addresses100 maximum (Currently, SNAT ports are added only for the first five public IP addresses.)
IP Groups IP addresses50 IP Groups or less: maximum 5000 individual IP addresses each per firewall instance.
51 – 100 IP Groups: 500 individual IP address each per firewall instance.

For more information see IP Groups (preview) in Azure Firewall
Route tableBy default, AzureFirewallSubnet has a 0.0.0.0/0 route with the NextHopType value set to Internet.

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

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

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

Azure Front Door Service limits

ResourceLimit
Azure Front Door resources per subscription100
Front-end hosts, which includes custom domains per resource500
Routing rules per resource500
Back-end pools per resource50
Back ends per back-end pool100
Path patterns to match for a routing rule25
URLs in a single cache purge call100
Custom web application firewall rules per policy100
Web application firewall policy per subscription100
Web application firewall match conditions per custom rule10
Web application firewall IP address ranges per match condition600
Web application firewall string match values per match condition10
Web application firewall string match value length256
Web application firewall POST body parameter name length256
Web application firewall HTTP header name length256
Web application firewall cookie name length256
Web application firewall HTTP request body size inspected128 KB
Web application firewall custom response body length2 KB

Timeout values

Client to Front Door

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

Front Door to application back-end

  • If the response is a chunked response, a 200 is returned if or when the first chunk is received.
  • After the HTTP request is forwarded to the back end, Front Door waits for 30 seconds for the first packet from the back end. Then it returns a 503 error to the client. This value is configurable via the field sendRecvTimeoutSeconds in the API.
    • For caching scenarios, this timeout is not configurable and so, if a request is cached and it takes more than 30 seconds for the first packet from Front Door or from the backend, then a 504 error is returned 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. This timeout value is not configurable.
  • Front Door to the back-end TCP session timeout is 90 seconds.

Upload and download data limit

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

Other limits

  • Maximum URL size – 8,192 bytes – Specifies maximum length of the raw URL (scheme + hostname + port + path + query string of the URL)
  • Maximum Query String size – 4,096 bytes – Specifies the maximum length of the query string, in bytes.
  • Maximum HTTP response header size from health probe URL – 4,096 bytes – Specified the maximum length of all the response headers of health probes.

Notification Hubs limits

TierFreeBasicStandard
Included pushes1 million10 million10 million
Active devices500200,00010 million
Tag quota per installation or registration606060

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

Role-based access control limits

ResourceLimit
Role assignments for Azure resources per Azure subscription2,000
Role assignments for Azure resources per management group500
Custom roles for Azure resources per tenant5,000
Custom roles for Azure resources per tenant
(for Azure Germany and Azure China 21Vianet)
2,000

Service Bus limits

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

Quota nameScopeNotesValue
Maximum number of Basic or Standard namespaces per Azure subscriptionNamespaceSubsequent requests for additional Basic or Standard namespaces are rejected by the Azure portal.100
Maximum number of Premium namespaces per Azure subscriptionNamespaceSubsequent requests for additional Premium namespaces are rejected by the portal.100
Queue or topic sizeEntityDefined upon creation of the queue or topic.

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

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

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

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

Partitioned entities aren’t supported in the Premium tier.

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

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

Maximum header size: 64 KB.

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

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

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

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

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

For both Send() and SendAsync() operations.
Number of virtual network and IP filter rulesNamespace 128

Site Recovery limits

The following limits apply to Azure Site Recovery.

Limit identifierLimit
Number of vaults per subscription500
Number of servers per Azure vault250
Number of protection groups per Azure vaultNo limit
Number of recovery plans per Azure vaultNo limit
Number of servers per protection groupNo limit
Number of servers per recovery plan50

SQL Database limits

For SQL Database limits, see SQL Database resource limits for single databasesSQL 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.

Storage limits

The following table describes default limits for Azure general-purpose v1, v2, Blob storage, block blob storage, and Data Lake Storage Gen2 enabled storage accounts. The ingress limit refers to all data that is sent to a storage account. The egress limit refers to all data that is received from a storage account.

ResourceLimit
Number of storage accounts per region per subscription, including standard, premium, and Data Lake Storage Gen2 enabled storage accounts.3250
Maximum storage account capacity5 PiB 1
Maximum number of blob containers, blobs, file shares, tables, queues, entities, or messages per storage accountNo limit
Maximum request rate1 per storage account20,000 requests per second
Maximum ingress1 per storage account (US, Europe regions)25 Gbps
Maximum ingress1 per storage account (regions other than US and Europe)5 Gbps if RA-GRS/GRS is enabled, 10 Gbps for LRS/ZRS2
Maximum egress for general-purpose v2 and Blob storage accounts (all regions)50 Gbps
Maximum egress for general-purpose v1 storage accounts (US regions)20 Gbps if RA-GRS/GRS is enabled, 30 Gbps for LRS/ZRS2
Maximum egress for general-purpose v1 storage accounts (non-US regions)10 Gbps if RA-GRS/GRS is enabled, 15 Gbps for LRS/ZRS2
Maximum number of virtual network rules per storage account200
Maximum number of IP address rules per storage account200

1 Azure Storage standard accounts support higher capacity limits and higher limits for ingress by request. To request an increase in account limits, contact Azure Support.

2 If your storage account has read-access enabled with geo-redundant storage (RA-GRS) or geo-zone-redundant storage (RA-GZRS), then the egress targets for the secondary location are identical to those of the primary location. Azure Storage replication options include:

3 Azure Data Lake Storage Gen2 is a set of capabilities dedicated to big data analytics, built on Azure Blob storage. Azure Storage and blob storage limitations apply to Data Lake Storage Gen2.

 Note

Microsoft recommends that you use a general-purpose v2 storage account for most scenarios. You can easily upgrade a general-purpose v1 or an Azure Blob storage account to a general-purpose v2 account with no downtime and without the need to copy data. For more information, see Upgrade to a general-purpose v2 storage account.

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 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 limits for standard storage accounts, see Scalability targets for standard storage accounts.

Storage resource provider limits

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

ResourceLimit
Storage account management operations (read)800 per 5 minutes
Storage account management operations (write)10 per second / 1200 per hour
Storage account management operations (list)100 per 5 minutes

Azure Blob storage limits

ResourceTarget
Maximum size of single blob containerSame as maximum storage account capacity
Maximum number of blocks in a block blob or append blob50,000 blocks
Maximum size of a block in a block blob100 MiB
Maximum size of a block blob50,000 X 100 MiB (approximately 4.75 TiB)
Maximum size of a block in an append blob4 MiB
Maximum size of an append blob50,000 x 4 MiB (approximately 195 GiB)
Maximum size of a page blob8 TiB
Maximum number of stored access policies per blob container5
Target request rate for a single blobUp to 500 requests per second
Target throughput for a single page blobUp to 60 MiB per second
Target throughput for a single block blobUp to storage account ingress/egress limits1

1 Throughput for a single blob 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 the performance enhancements of high-throughput block blobs, upload larger blobs or blocks. Specifically, call the Put Blob or Put Block operation with a blob or block size that is greater than 4 MiB for standard storage accounts. For premium block blob or for Data Lake Storage Gen2 storage accounts, use a block or blob size that is greater than 256 KiB.

Azure Files limits

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

ResourceStandard file sharesPremium file shares
Minimum size of a file shareNo minimum; pay as you go100 GiB; provisioned
Maximum size of a file share100 TiB*, 5 TiB100 TiB
Maximum size of a file in a file share1 TiB1 TiB
Maximum number of files in a file shareNo limitNo limit
Maximum IOPS per share10,000 IOPS*, 1,000 IOPS100,000 IOPS
Maximum number of stored access policies per file share55
Target throughput for a single file shareup to 300 MiB/sec*, Up to 60 MiB/sec ,See premium file share ingress and egress values
Maximum egress for a single file shareSee standard file share target throughputUp to 6,204 MiB/s
Maximum ingress for a single file shareSee standard file share target throughputUp to 4,136 MiB/s
Maximum open handles per file2,000 open handles2,000 open handles
Maximum number of share snapshots200 share snapshots200 share snapshots
Maximum object (directories and files) name length2,048 characters2,048 characters
Maximum pathname component (in the path \A\B\C\D, each letter is a component)255 characters255 characters

* Default on standard file shares is 5 TiB, see Enable and create large file shares for the details on how to increase the standard file shares scale up to 100 TiB.

Azure File Sync limits

ResourceTargetHard limit
Storage Sync Services per region20 Storage Sync ServicesYes
Sync groups per Storage Sync Service100 sync groupsYes
Registered servers per Storage Sync Service99 serversYes
Cloud endpoints per sync group1 cloud endpointYes
Server endpoints per sync group50 server endpointsNo
Server endpoints per server30 server endpointsYes
File system objects (directories and files) per sync group100 million objectsNo
Maximum number of file system objects (directories and files) in a directory5 million objectsYes
Maximum object (directories and files) security descriptor size64 KiBYes
File size100 GiBNo
Minimum file size for a file to be tieredV9: Based on file system cluster size (double file system cluster size). For example, if the file system cluster size is 4kb, the minimum file size will be 8kb.
V8 and older: 64 KiB
Yes

 Note

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

Azure Queue storage limits

ResourceTarget
Maximum size of a single queue500 TiB
Maximum size of a message in a queue64 KiB
Maximum number of stored access policies per queue5
Maximum request rate per storage account20,000 messages per second, which assumes a 1-KiB message size
Target throughput for a single queue (1-KiB messages)Up to 2,000 messages per second

Azure Table storage limits

The following table describes capacity, scalability, and performance targets for Table storage.

ResourceTarget
Number of tables in an Azure storage accountLimited only by the capacity of the storage account
Number of partitions in a tableLimited only by the capacity of the storage account
Number of entities in a partitionLimited only by the capacity of the storage account
Maximum size of a single table500 TiB
Maximum size of a single entity, including all property values1 MiB
Maximum number of properties in a table entity255 (including the three system properties, PartitionKeyRowKey, and Timestamp)
Maximum total size of an individual property in an entityVaries by property type. For more information, see Property Types in Understanding the Table Service Data Model.
Size of the PartitionKeyA string up to 1 KiB in size
Size of the RowKeyA string up to 1 KiB in size
Size of an entity group transactionA transaction can include at most 100 entities and the payload must be less than 4 MiB in size. An entity group transaction can include an update to an entity only once.
Maximum number of stored access policies per table5
Maximum request rate per storage account20,000 transactions per second, which assumes a 1-KiB entity size
Target throughput for a single table partition (1 KiB-entities)Up to 2,000 entities per second

Virtual machine disk limits

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

 Important

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

For Azure managed disks:

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

ResourceLimit
Standard managed disks50,000
Standard SSD managed disks50,000
Premium managed disks50,000
Standard_LRS snapshots50,000
Standard_ZRS snapshots50,000
Managed image50,000
  • For Standard storage accounts: A Standard storage account has a maximum total request rate of 20,000 IOPS. The total IOPS across all of your virtual machine disks in a Standard storage account should not exceed this limit.You can roughly calculate the number of highly utilized disks supported by a single Standard storage account based on the request rate limit. For example, for a Basic tier VM, the maximum number of highly utilized disks is about 66, which is 20,000/300 IOPS per disk. The maximum number of highly utilized disks for a Standard tier VM is about 40, which is 20,000/500 IOPS per disk.
  • For Premium storage accounts: A Premium storage account has a maximum total throughput rate of 50 Gbps. The total throughput across all of your VM disks should not exceed this limit.

For more information, see Virtual machine sizes.

Managed virtual machine disks

Standard HDD managed disks

Standard Disk TypeS4S6S10S15S20S30S40S50S60S70S80
Disk size in GiB32641282565121,0242,0484,0968,19216,38432,767
IOPS per diskUp to 500Up to 500Up to 500Up to 500Up to 500Up to 500Up to 500Up to 500Up to 1,300Up to 2,000Up to 2,000
Throughput per diskUp to 60 MiB/secUp to 60 MiB/secUp to 60 MiB/secUp to 60 MiB/secUp to 60 MiB/secUp to 60 MiB/secUp to 60 MiB/secUp to 60 MiB/secUp to 300 MiB/secUp to 500 MiB/secUp to 500 MiB/sec

Standard SSD managed disks

Standard SSD sizesE1E2E3E4E6E10E15E20E30E40E50E60E70E80
Disk size in GiB481632641282565121,0242,0484,0968,19216,38432,767
IOPS per diskUp to 120Up to 120Up to 120Up to 120Up to 240Up to 500Up to 500Up to 500Up to 500Up to 500Up to 500Up to 2,000Up to 4,000Up to 6,000
Throughput per diskUp to 25 MiB/secUp to 25 MiB/secUp to 25 MiB/secUp to 25 MiB/secUp to 50 MiB/secUp to 60 MiB/secUp to 60 MiB/secUp to 60 MiB/secUp to 60 MiB/secUp to 60 MiB/secUp to 60 MiB/secUp to 400 MiB/secUp to 600 MiB/secUp to 750 MiB/sec

Premium SSD managed disks: Per-disk limits

Premium SSD sizes P1P2P3P4P6P10P15P20P30P40P50P60P70P80
Disk size in GiB481632641282565121,0242,0484,0968,19216,38432,767
Provisioned IOPS per disk1201201201202405001,1002,3005,0007,5007,50016,00018,00020,000
Provisioned Throughput per disk25 MiB/sec25 MiB/sec25 MiB/sec25 MiB/sec50 MiB/sec100 MiB/sec125 MiB/sec150 MiB/sec200 MiB/sec250 MiB/sec250 MiB/sec500 MiB/sec750 MiB/sec900 MiB/sec
Max burst IOPS per disk3,5003,5003,5003,5003,5003,5003,5003,500
Max burst throughput per disk170 MiB/sec170 MiB/sec170 MiB/sec170 MiB/sec170 MiB/sec170 MiB/sec170 MiB/sec170 MiB/sec
Max burst duration30 min30 min30 min30 min30 min30 min30 min30 min
Eligible for reservationNoNoNoNoNoNoNoNoYes, up to one yearYes, up to one yearYes, up to one yearYes, up to one yearYes, up to one yearYes, up to one year

Premium SSD managed disks: Per-VM limits

ResourceLimit
Maximum IOPS Per VM80,000 IOPS with GS5 VM
Maximum throughput per VM2,000 MB/s with GS5 VM

Unmanaged virtual machine disks

Standard unmanaged virtual machine disks: Per-disk limits

VM tierBasic tier VMStandard tier VM
Disk size4,095 GB4,095 GB
Maximum 8-KB IOPS per persistent disk300500
Maximum number of disks that perform the maximum IOPS6640

Premium unmanaged virtual machine disks: Per-account limits

ResourceLimit
Total disk capacity per account35 TB
Total snapshot capacity per account10 TB
Maximum bandwidth per account (ingress + egress)1<=50 Gbps

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

Premium unmanaged virtual machine disks: Per-disk limits

Premium storage disk typeP10P20P30P40P50
Disk size128 GiB512 GiB1,024 GiB (1 TB)2,048 GiB (2 TB)4,095 GiB (4 TB)
Maximum IOPS per disk5002,3005,0007,5007,500
Maximum throughput per disk100 MB/sec150 MB/sec200 MB/sec250 MB/sec250 MB/sec
Maximum number of disks per storage account2807035178

Premium unmanaged virtual machine disks: Per-VM limits

ResourceLimit
Maximum IOPS per VM80,000 IOPS with GS5 VM
Maximum throughput per VM2,000 MB/sec with GS5 VM

StorSimple System limits

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

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

Stream Analytics limits


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

Virtual Machines limits

Virtual Machines limits

ResourceLimit
Virtual machines per cloud service150
Input endpoints per cloud service2150

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

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

Virtual Machines limits – Azure Resource Manager

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

ResourceLimit
VMs per subscription25,0001 per region.
VM total cores per subscription201 per region. Contact support to increase limit.
Azure Spot VM total cores per subscription201 per region. Contact support to increase limit.
VM per series, such as Dv2 and F, cores per subscription201 per region. Contact support to increase limit.
Availability sets per subscription2,000 per region.
Virtual machines per availability set200
Certificates per subscriptionUnlimited2

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

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

 Note

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

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

ResourceLimit
Maximum number of VMs in a scale set1,000
Maximum number of VMs based on a custom VM image in a scale set600
Maximum number of scale sets in a region2,000

See also

Add to Del.cio.us RSS Feed Add to Technorati Favorites Stumble It! Digg It!
    BuziTweet


Gerry Reid

Gerry Reid

“Technology leader with 20+ years experience in Agile IT Development, consulting, operations, delivery, project management in CRM, robotics, automation, cloud in financial services, telecoms & consulting sector",
https://crmanalytics.net/wp-content/uploads/2020/04/Azure-VM-Pricing.pnghttps://crmanalytics.net/wp-content/uploads/2020/04/Azure-VM-Pricing-150x150.pngGerry ReidAzureAZ-900,Azure PricingNote: Azure Pricing changes constantly, so this is just a snapshot of what the pricing is like today, go to the links below to MS Azure website to get the latest pricing information To learn more about Azure pricing, see Azure pricing overview. There, you can estimate your costs by using...CRM consulting and technology for Ireland and Europe, in the Public and private sector