You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In all tiers except the Consumption tier, Azure API Management provides a built-in gateway health check endpoint at path `/status-0123456789abcdef`. Reach this endpoint to help confirm that the API gateway is available and functioning correctly. It doesn't test backend APIs, only the gateway itself.
Copy file name to clipboardExpand all lines: articles/api-management/service-limits.md
+52-30Lines changed: 52 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,84 +4,106 @@ description: Learn about service limits in Azure API Management, including their
4
4
author: dlepow
5
5
ms.service: azure-api-management
6
6
ms.topic: concept-article
7
-
ms.date: 12/15/2025
7
+
ms.date: 02/17/2026
8
8
ms.author: danlep
9
9
ai-usage: ai-assisted
10
10
---
11
11
12
12
# Understanding Azure API Management service limits
13
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.
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#azure-api-management-limits) such as API operations and other entities. This article explains why these limits exist and how to use the service effectively within these constraints.
15
15
16
16
## Why are there service limits?
17
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:
18
+
Azure API Management operates on finite physical infrastructure. To ensure reliable performance for all customers, the service enforces limits calibrated based on:
21
19
22
20
* Azure platform capacity and performance characteristics
23
21
* Service tier capabilities
24
22
* Typical customer usage patterns
25
23
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.
24
+
Resource limits are interrelated and tuned to prevent any single aspect from disrupting overall service performance.
25
+
26
+
## Changes to service limits - 2026 update
27
27
28
-
## Changes to service limits in Classic tiers
28
+
Starting March 2026 and over the following several months, Azure API Management is introducing updated resource limits for instances across all tiers. The limits are shown in the following table.
29
29
30
-
Starting March 2026, Azure API Management will publish and apply updated limits to instances in the Classic tiers (Developer, Basic, Standard, and Premium) and the Consumption tier. These updates will align with each tier’s capabilities and help customers choose the right option for their needs.
* New limits for Classic tier resources will be 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 will make these constraints explicit and predictable.
34
+
* Limits in the classic tiers now align with those set in the v2 tiers.
35
+
* Limits are enforced for a smaller set of resource types that are directly related to service capacity and performance, such as API operations, tags, products, and subscriptions.
36
+
37
+
> [!NOTE]
38
+
> Resource limits could be adjusted over time to reflect the latest service capabilities.
39
+
40
+
### Rollout process
41
+
42
+
New limits roll out in a phased approach by tier as follows:
36
43
37
-
### Limits policy for existing customers
44
+
|Tier |Expected rollout date |
45
+
|---------|---------|
46
+
|Consumption<br/>Developer<br/>Basic<br/>Basic v2 | March 15, 2026 |
47
+
|Standard<br/>Standard v2 | April 15, 2026 |
48
+
|Premium<br/>Premium v2 | May 15, 2026 |
38
49
39
-
After the new Classic tier limits take effect, you can continue using your resources without interruption. This means:
50
+
### Limits policy for existing classic tier customers
40
51
41
-
* Existing Classic tier services that already exceed published limits won't be impacted.
42
-
* You'll be able to make changes to existing resources and add new resources up to a small threshold above your current usage.
52
+
After the new limits take effect, you can continue using your preexisting API Management resources without interruption.
43
53
44
-
This approach ensures that existing workloads aren't disrupted while still encouraging alignment with the new limits over time.
54
+
* Existing classic tier services, where current usage exceeds the new limits, are "grandfathered" when the new limits are introduced. (Instances in the v2 tiers are already subject to the new limits.)
55
+
* Limits in grandfathered services will be set 10% higher than the customer's observed usage at the time new limits take effect.
56
+
* Grandfathering applies per service and service tier.
57
+
* Other existing services and new services are subject to the new limits when they take effect.
45
58
46
-
## Strategies to manage resources
59
+
## Manage resources within limits
47
60
48
-
If you're approaching or have reached certain resource limits, consider these strategies:
61
+
If you're reaching resource limits, you might notice impacts such as being unable to create new resources or update existing ones. You might also experience degraded performance in some service operations.
62
+
63
+
The following are guidelines to help you manage your resources effectively in these cases.
49
64
50
65
### Improve resource management
51
66
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.
67
+
* Implement a regular cleanup process for unused resources.
68
+
* Use tags effectively to identify resources that you can consolidate or remove.
69
+
* Review [capacity metrics](api-management-capacity.md) to understand resource utilization and potential bottlenecks.
55
70
56
71
### Optimize API and operation organization
57
72
58
-
When counting the number of APIs and API-related resources (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:
73
+
When counting API-related resources (such as API operationsand tags), API Management also includes API versions and revisions. The following strategies can help when approaching limits for these resources:
59
74
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
75
+
* Remove unused API versions or revisions.
76
+
* Consolidate or remove operations where appropriate.
77
+
* Use API versions and revisions strategically.
64
78
65
79
### Evaluate your service tier
66
80
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.
81
+
If you consistently reach resource limits or capacity issues, evaluate your current service tier. Certain limits, such as those for API operations, vary by service tier.
68
82
69
83
* Consider options to add units or upgrade your tier.
70
84
* Consider deploying an additional API Management instance in the current tier.
71
85
86
+
To evaluate the costs associated with these options, see [Azure API Management pricing](https://azure.microsoft.com/pricing/details/api-management/).
87
+
72
88
## Guidelines for limit increases
73
89
74
-
In some cases, you may want to request an increase to certain service limits. Before doing so, note the following guidelines:
90
+
In some cases, you might want to increase a service limit. Before requesting a limit increase, note the following guidelines:
75
91
76
-
* Explore strategies to address the issue proactively before requesting a limit increase. See the preceding [Strategies to manage resources](#strategies-to-manage-resources) section for more information.
92
+
* Explore strategies to address the issue proactively before requesting a limit increase. See the preceding section [Manage resources within limits](#manage-resources-within-limits).
77
93
78
-
* Consider potential impacts of the limit increase on overall service performance and stability. Increasing a limit might affect your service's capacity or cause increased latency in some service operations.
94
+
* Consider potential impacts of the limit increase on overall service performance and stability. Increasing a limit might affect your service's capacity or increase latency in some service operations.
79
95
80
96
### Requesting a limit increase
81
97
98
+
The product team considers requests for limit increases only for customers using services in the following tiers that are designed for medium to large production workloads:
99
+
100
+
* Standard and Standard v2
101
+
* Premium and Premium v2
102
+
103
+
Requests for limit increases are evaluated on a case-by-case basis and aren't guaranteed. The product team prioritizes Premium and Premium v2 tier customers for limit increases.
104
+
82
105
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/).
83
106
84
-
Requests for limit increases are evaluated on a case-by-case basis and aren't guaranteed. We prioritize Premium tier customers for limit increases.
Copy file name to clipboardExpand all lines: articles/api-management/v2-service-tiers-overview.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: dlepow
6
6
7
7
ms.service: azure-api-management
8
8
ms.topic: concept-article
9
-
ms.date: 11/21/2025
9
+
ms.date: 02/05/2026
10
10
ms.author: danlep
11
11
ms.custom:
12
12
- references_regions
@@ -103,10 +103,10 @@ The following are currently unavailable in the v2 tiers.
103
103
104
104
## Resource limits
105
105
106
-
The following resource limits apply to the v2 tiers:
106
+
The following limits apply to the v2 tiers:
107
107
108
-
* [Resource limits for v2 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)
109
-
* [Developer portal limits for v2 tiers](/azure/azure-resource-manager/management/azure-subscription-service-limits?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=%2Fazure%2Fapi-management%2Fbreadcrumb%2Ftoc.json#limits---developer-portal-in-api-management-v2-tiers)
108
+
* [Resource limits for classic and v2 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-classic-and-v2-tiers)
109
+
* [Resource limits in developer portal in API Management v2 tiers](/azure/azure-resource-manager/management/azure-subscription-service-limits?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=%2Fazure%2Fapi-management%2Fbreadcrumb%2Ftoc.json#limits---developer-portal-in-api-management-v2-tiers)
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/management/azure-subscription-service-limits.md
+13-11Lines changed: 13 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Azure subscription and service limits, quotas, and constraints
3
3
description: Understand common Azure subscription and service limits, quotas, and constraints. This article includes information about how to increase limits along with maximum values.
4
4
ms.topic: article
5
-
ms.date: 01/23/2025
5
+
ms.date: 02/05/2026
6
6
ms.custom: ignite-2024
7
7
#customer intent: As a subscription owner or cloud operator, I want an authoritative list of subscription and service limits and guidance for requesting increases so that I can plan capacity and avoid service interruptions.
8
8
---
@@ -74,18 +74,16 @@ Note that subscription IDs must be non-empty GUIDs.
74
74
75
75
This section provides information about limits that apply to Azure API Management instances in different [service tiers](../../api-management/api-management-features.md), including the following:
The following limits are introduced starting March 2026. Services in the classic tiers that surpass the revised limits are allowed to keep their existing capacity. For more information, see [Understanding API Management service limits](../../api-management/service-limits.md).
@@ -520,7 +522,7 @@ See [VM Applications overview](/azure/virtual-machines/vm-applications) for more
520
522
521
523
#### Azure disk encryption sets
522
524
523
-
A limit of 5,000 disk encryption sets are allowed per region and per subscription. [Contact Azure support](../../communications-gateway/request-changes.md) to increase the quota.
525
+
A limit of 5,000 disk encryption sets is allowed per region and per subscription. [Contact Azure support](../../communications-gateway/request-changes.md) to increase the quota.
524
526
525
527
See the following documentation to learn more about encryption restrictions:
0 commit comments