Azure API Management enforces various limits on resources such as API operations and other entities. We are announcing new limits across these entities for classic and v2 tiers.
Azure API Management operates on finite physical infrastructure. To ensure reliable performance for all customers, the service enforces limits calibrated based on:
- Azure platform capacity and performance characteristics
- Service tier capabilities
- Typical customer usage patterns
Resource limits are interrelated and tuned to prevent any single aspect from disrupting overall service performance.
Changes to service limits - 2026 update
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.
| Entity/Resource | Consumption | Developer | Basic/ Basic v2 | Standard/ Standard v2 | Premium/ Premium v2 |
|---|---|---|---|---|---|
| API operations | 3,000 | 3,000 | 10,000 | 50,000 | 75,000 |
| API tags | 1,500 | 1,500 | 1,500 | 2,500 | 15,000 |
| Named values | 5,000 | 5,000 | 5,000 | 10,000 | 18,000 |
| Loggers | 100 | 100 | 100 | 200 | 400 |
| Products | 100 | 100 | 200 | 500 | 2,000 |
| Subscriptions | N/A | 10,000 | 15,000 | 25,000 | 75,000 |
| Users | N/A | 20,000 | 20,000 | 50,000 | 75,000 |
| Workspaces per workspace gateway | N/A | N/A | N/A | N/A | 30 |
| Self-hosted gateways | N/A | 5 | N/A | N/A | 1001 |
1 Applies to Premium tier only.
What's changing
- Limits in the classic tiers now align with those set in the v2 tiers.
- 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.
Rollout process
New limits roll out in a phased approach by tier as follows:
| Tier | Expected rollout date |
|---|---|
| Consumption Developer Basic Basic v2 | March 15, 2026 |
| Standard Standard v2 | April 15, 2026 |
| Premium Premium v2 | May 15, 2026 |
Limits policy for existing classic tier customers
After the new limits take effect, you can continue using your preexisting API Management resources without interruption.
- 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.)
- Limits in grandfathered services will be set 10% higher than the customer's observed usage at the time new limits take effect.
- Grandfathering applies per service and service tier.
- Other existing services and new services are subject to the new limits when they take effect.
Guidelines for limit increases
In some cases, you might want to increase a service limit. Before requesting a limit increase, note the following guidelines:
- Explore strategies to address the issue proactively before requesting a limit increase. See the article here Manage resources within limits.
- 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.
Requesting a limit increase
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:
- Standard and Standard v2
- Premium and Premium v2
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.
To request a limit increase, create a support request from the Azure portal. For more information, see Azure support plans.
Microsoft