|
| 1 | +--- |
| 2 | +title: Understanding Azure API Management Service Limits |
| 3 | +description: Learn about service limits in Azure API Management, including their purpose, how they're enforced, and guidelines for managing your service. |
| 4 | +author: dlepow |
| 5 | +ms.service: azure-api-management |
| 6 | +ms.topic: concept-article |
| 7 | +ms.date: 09/09/2025 |
| 8 | +ms.author: danlep |
| 9 | +ai-usage: ai-assisted |
| 10 | +--- |
| 11 | + |
| 12 | +# Understanding Azure API Management service limits |
| 13 | + |
| 14 | +Azure API Management enforces various [limits on resources](/azure/azure-resource-manager/management/azure-subscription-service-limits?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=%2Fazure%2Fapi-management%2Fbreadcrumb%2Ftoc.json&branch=pr-en-us-304099#azure-api-management-limits) such as APIs, operations, and other entities. This article explains why they exist and how to use the service effectively within these constraints. |
| 15 | + |
| 16 | +## Why are there service limits? |
| 17 | + |
| 18 | +Service limits in Azure API Management exist, as they do for all Azure services, because even cloud services operate on physical infrastructure with finite resources. While Azure provides tremendous scalability and flexibility, the underlying hardware and system architecture have inherent constraints that we manage to ensure reliable performance for our customers. |
| 19 | + |
| 20 | +Service limits in Azure API Management aren't arbitrary constraints but are calibrated based on: |
| 21 | + |
| 22 | +* Azure platform capacity and performance characteristics |
| 23 | +* Service tier capabilities |
| 24 | +* Typical customer usage patterns |
| 25 | + |
| 26 | +Resource limits are interrelated and tuned to work together. They prevent any single aspect of the service from disrupting overall performance of the service. |
| 27 | + |
| 28 | +## Changes to service limits in Classic tiers |
| 29 | + |
| 30 | +Starting in July 2025, Azure API Management is updating the service limits in the Classic (Developer, Basic, Standard, and Premium) and Consumption tiers to better reflect the capabilities of the service and help customers make decisions when choosing an API Management tier for their needs. Limits for Classic tiers are published [here](/azure/azure-resource-manager/management/azure-subscription-service-limits?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=%2Fazure%2Fapi-management%2Fbreadcrumb%2Ftoc.json#limits---api-management-classic-tiers). |
| 31 | + |
| 32 | +### What's changing |
| 33 | + |
| 34 | +* New limits for Classic tier resources are more easily compared with the limits in the [V2 service tiers](/azure/azure-resource-manager/management/azure-subscription-service-limits?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=%2Fazure%2Fapi-management%2Fbreadcrumb%2Ftoc.json#limits---api-management-v2-tiers). |
| 35 | +* Previously, limits for certain resources in Classic tiers weren't defined explicitly or enforced. In practice, these resources were always constrained by service configuration, service capacity, number of scale units, policy configuration, and other factors. The new limits make these constraints explicit and predictable. |
| 36 | + |
| 37 | +### Limits policy for existing customers |
| 38 | + |
| 39 | +If your existing API Management instance already exceeds new Classic tier limits, you can continue using your resources without interruption. This means: |
| 40 | + |
| 41 | +* Existing services that already exceed published limits aren't impacted. |
| 42 | +* You're able to make changes to existing resources and add new resources up to a small threshold above your current usage. |
| 43 | + |
| 44 | +This approach ensures that existing workloads aren't disrupted while still encouraging alignment with the new limits over time. |
| 45 | + |
| 46 | +## Strategies to manage resources |
| 47 | + |
| 48 | +If you're approaching or have reached certain resource limits, consider these strategies: |
| 49 | + |
| 50 | +### Improve resource management |
| 51 | + |
| 52 | +* Implement a regular cleanup process for unused resources |
| 53 | +* Use tags effectively to identify resources that can be consolidated or removed |
| 54 | +* Review [capacity metrics](api-management-capacity.md) to understand resource utilization and identify potential bottlenecks. |
| 55 | + |
| 56 | +### Optimize API and operation organization |
| 57 | + |
| 58 | +When counting the number of APIs and API-related resource (such as API operations, backends, tags, and so on), API Management also includes API versions and revisions. Consider the following strategies when approaching limits for these resources: |
| 59 | + |
| 60 | +* Remove unused API versions or revisions |
| 61 | +* Consolidate or remove operations where appropriate |
| 62 | +* Reorganize APIs with large numbers of operations into multiple smaller, more focused APIs |
| 63 | +* Use API versions and revisions strategically |
| 64 | + |
| 65 | +### Evaluate your service tier |
| 66 | + |
| 67 | +If you're consistently hitting resource limits, it may be worth evaluating your current service tier. Certain limits such as for APIs vary by service tier. |
| 68 | + |
| 69 | +* Consider options to add units or upgrade your tier. |
| 70 | +* Consider deploying an additional API Management instance in the current tier. |
| 71 | + |
| 72 | +## Guidelines for limit increases |
| 73 | + |
| 74 | +In some cases, you may want to request an increase to certain service limits. Before doing so, note the following guidelines: |
| 75 | + |
| 76 | + |
| 77 | +* Explore strategies to address the issue proactively before requesting a limit increase. See the [Strategies to manage resources](#strategies-to-manage-resources) section for more information. |
| 78 | + |
| 79 | +* Consider potential impacts of the limit increase on overall service performance and stability. Increasing a limit might affect service capacity or cause increased latency in some service operations. |
| 80 | + |
| 81 | +### Requesting a limit increase |
| 82 | + |
| 83 | +To request a limit increase, create a support request from the Azure portal. For more information, see [Azure support plans](https://azure.microsoft.com/support/). |
| 84 | + |
| 85 | +Requests for limit increases are evaluated on a case-by-case basis and aren't guaranteed. We prioritize Premium tier customers for limit increases. |
| 86 | + |
| 87 | +## Related content |
| 88 | + |
| 89 | +* [Capacity of an API Management instance](api-management-capacity.md) |
| 90 | +* [Upgrade and scale an API Management instance](upgrade-and-scale.md) |
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments