Azure service and component limits

Every Azure service has a set of physical limitations by design. When planning and designing Microsoft Azure-based solutions, these Azure service physical limits should always be taken into account.

More specifically, Azure has a number of subscription and service limits as well as default quotas and constraints. The following Microsoft article describes all these limitations organized by service: The following Azure concepts and services are listed in this article:

  • Subscriptions and management groups
  • Resource groups
  • Templates
  • Active Directory service
  • API management
  • App service
  • Automation
  • Azure App Configuration
  • Azure API for FHIR
  • Azure Cache for Redis
  • Azure Cloud Services
  • Azure Cognitive Services
  • Azure Cosmos DB
  • Azure Data Explorer
  • Azure Database for MySQL
  • Azure Database for PostgreSQL
  • Azure Functions
  • Azure Kubernetes Service
  • Azure Machine Learning
  • Azure Maps
  • Azure Monitor
  • Alerts API
  • Action groups
  • Autoscale
  • Log queries and language
  • Log Analytics workspaces
  • Application Insights
  • Azure Policy
  • Azure Quantum
  • Azure role-based access control
  • Azure SignalR Service
  • Azure VMware Solution
  • Azure Backup
  • Azure Batch
  • Classic deployment model (instead of Azure Resource Manager – ARM)
  • Container Instances
  • Container Registry
  • Content Delivery Network
  • Data Factory
  • ARM API limits
  • Data Lake Analytics
  • Data Lake Storage
  • Data Share
  • Database Migration Service
  • Digital Twins
  • Event Grid
  • Event Hubs
  • IoT Central
  • IoT Hub
  • IoT Hub Device Provisioning Service
  • Key Vault
  • Managed identity
  • Media Services
  • Mobile Services
  • Multi-Factor Authentication
  • Azure Networking limits (public IP addresses, load balancer, express route, virtual network gateway, NAT gateway, virtual WAN, application gateway, network watcher, private link, Azure Purview, Traffic Manager, Azure Bastion, Azure DNS, Azure Firewall, Azure Front Door Service)
  • Notification Hubs
  • Service Bus
  • Site Recovery
  • SQL Database
  • Azure Synapse Analytics
  • Web service call limits (ARM)
  • Azure Files and Azure File Sync
  • Azure Storage limits (Storage resource provider, Azure Blob storage, Azure Queue storage, Azure Table storage, Virtual machine disks, Disk encryption sets, Managed virtual machine disks, Unmanaged virtual machine disks, StorSimple System)
  • Stream Analytics
  • Azure Virtual Machines
  • Virtual machine scale sets (VMSS)

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. The terms soft limit and hard limit often are used informally to describe the current, adjustable limit (soft limit) and the maximum limit (hard limit). If a limit isn’t adjustable, there won’t be a soft limit, only a hard limit. 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. Also bear in mind that some limits are managed at a regional level.

The following article provides guidance on how to request quota increases in Azure:

On top of the above limitations, there are known Azure Resource Manager throttling limits at tenant and subscription level, as described in the following article:

There are also a number of Azure resource naming limits per each Azure resource provider, as described in the following article:

On top of the above articles, it is important to always perform a Web search for “[Azure service] resource limits“, where [Azure services] is the service you are planning and designing, e.g. Azure Virtual Machines.

As a conclusion, taking into account the above Azure service and component limits at an early stage is critical when planning or designing Azure solutions.