Consumption APIM still enforcing 1,000 operations while current documented limit is 3,000

Question

Consumption APIM still enforcing 1,000 operations while current documented limit is 3,000

Mohamed Farees M 25

We have an Azure API Management Azure API Management service using the Consumption tier.

Our ARM/Bicep deployment currently fails with:

You've reached the maximum number of Operations (1000) in Service. Please delete one or more Operation(s) from Service to continue.

However, the current Azure API Management service limits documentation lists:

Consumption: 3,000 API operations

The documentation also lists March 15, 2026 as the expected rollout date for Consumption, while noting that rollout occurs in phases over several months.

I also tried creating new APIM consumption plan and it still the same. 1st request success with 1003 Operations and seconda failing with same error

Region/location : eastus2

Could the Azure API Management product team please confirm:

Is 1,000 still an expected effective limit for some Consumption APIM instances during the 2026 rollout?
Has the 3,000-operation rollout completed for Consumption?
Is rollout dependent on region, APIM stamp, instance creation date, or another factor?
Is there any customer action required to move an existing Consumption APIM service from the 1,000-operation limit to 3,000?
If the service should already have 3,000, how can a customer without a paid technical support plan have the service corrected?

Official documentation: https://learn.microsoft.com/azure/api-management/service-limits

Mohamed Farees M 25 Reputation points

2026-08-27T12:47:01.68+00:00

To reproduce create APIM consumption plan in eastus2 location or centralus location. Import 1000 operations
Tejaswini Billakurthi 250 Reputation points Microsoft External Staff Moderator

2026-09-09T11:48:02.1866667+00:00
Hi @Mohamed Farees M ,

Thank you for reaching out to Microsoft Q & A !

Based on the current Azure API Management service limits documentation, the Consumption tier limit is documented as 3,000 API operations. However, your deployment error is still reporting the legacy 1,000-operation limit:

"You've reached the maximum number of Operations (1000) in Service."

Since you can reproduce the behavior on newly created Consumption instances and receive the same enforcement message, this appears inconsistent with the currently published service limits.

From the information provided, I could not find documentation indicating that the 3,000-operation limit depends on region, service creation date, or customer configuration. The published limits documentation describes 3,000 operations as the current Consumption-tier limit.

Because the behavior is reproducible on newly created services, it would be helpful to know whether the issue still occurs today and whether the affected APIM instances are all in the same region. If the behavior continues, this may require investigation by the Azure API Management product team to confirm whether a rollout is still in progress or whether a backend quota-enforcement issue exists for the affected services.

For reference:

Azure API Management service limits: https://learn.microsoft.com/azure/api-management/service-limits

Please let us know whether the issue is still reproducible and which regions have been tested.

Please "Upvote the Answer" if this information helped you. This will help us and others in the community as well.
Mohamed Farees M 25 Reputation points

2026-09-09T11:57:21.9633333+00:00

Some in centralus and some in eastus2 but On March as per Docs they said rolled out, which means global , In that case it should be reflected. Not sure why its still same
Tejaswini Billakurthi 250 Reputation points Microsoft External Staff Moderator

2026-09-10T07:27:20.1+00:00

Hi @Mohamed Farees M

Thank you for confirming the behavior in both Central US and East US 2.

The Azure API Management limits article describes March 15, 2026 as the expected rollout date and states that the updated limits were introduced starting in March 2026 and rolled out over several months using a phased approach. Based on the published documentation, that date indicates when the rollout began, rather than confirming that every Consumption instance has already transitioned to the 3,000-operation limit.

I have not found any public documentation that reports rollout-completion status by region, APIM stamp, or service instance. Therefore, I cannot determine from the documentation alone whether the behavior reflects an ongoing rollout or a quota-enforcement inconsistency.

Since newly created Consumption instances in both Central US and East US 2 are still enforcing the 1,000-operation limit, this would require validation from the Azure API Management product team.

A support request under the Service and subscription limits (quotas) category may be appropriate, as the issue appears to be an enforcement mismatch with the published service limit rather than a request for a quota increase. Please include the subscription ID, APIM service names, regions tested, exact error message, and reproduction details showing that the deployment succeeds up to approximately 1,003 operations before enforcing the 1,000-operation limit.

Reference: Understanding Azure API Management service limits.

1 answer

Your answer

Mohamed Farees M 25 Reputation points

2026-08-27T12:47:01.68+00:00

To reproduce create APIM consumption plan in eastus2 location or centralus location. Import 1000 operations
Tejaswini Billakurthi 250 Reputation points Microsoft External Staff Moderator

2026-09-09T11:48:02.1866667+00:00

Hi @Mohamed Farees M ,

Thank you for reaching out to Microsoft Q & A !

Based on the current Azure API Management service limits documentation, the Consumption tier limit is documented as 3,000 API operations. However, your deployment error is still reporting the legacy 1,000-operation limit:

"You've reached the maximum number of Operations (1000) in Service."

Since you can reproduce the behavior on newly created Consumption instances and receive the same enforcement message, this appears inconsistent with the currently published service limits.

From the information provided, I could not find documentation indicating that the 3,000-operation limit depends on region, service creation date, or customer configuration. The published limits documentation describes 3,000 operations as the current Consumption-tier limit.

Because the behavior is reproducible on newly created services, it would be helpful to know whether the issue still occurs today and whether the affected APIM instances are all in the same region. If the behavior continues, this may require investigation by the Azure API Management product team to confirm whether a rollout is still in progress or whether a backend quota-enforcement issue exists for the affected services.

For reference:

Azure API Management service limits: https://learn.microsoft.com/azure/api-management/service-limits

Please let us know whether the issue is still reproducible and which regions have been tested.

Please "Upvote the Answer" if this information helped you. This will help us and others in the community as well.
Mohamed Farees M 25 Reputation points

2026-09-09T11:57:21.9633333+00:00

Some in centralus and some in eastus2 but On March as per Docs they said rolled out, which means global , In that case it should be reflected. Not sure why its still same
Tejaswini Billakurthi 250 Reputation points Microsoft External Staff Moderator

2026-09-10T07:27:20.1+00:00

Hi @Mohamed Farees M

Thank you for confirming the behavior in both Central US and East US 2.

The Azure API Management limits article describes March 15, 2026 as the expected rollout date and states that the updated limits were introduced starting in March 2026 and rolled out over several months using a phased approach. Based on the published documentation, that date indicates when the rollout began, rather than confirming that every Consumption instance has already transitioned to the 3,000-operation limit.

I have not found any public documentation that reports rollout-completion status by region, APIM stamp, or service instance. Therefore, I cannot determine from the documentation alone whether the behavior reflects an ongoing rollout or a quota-enforcement inconsistency.

Since newly created Consumption instances in both Central US and East US 2 are still enforcing the 1,000-operation limit, this would require validation from the Azure API Management product team.

A support request under the Service and subscription limits (quotas) category may be appropriate, as the issue appears to be an enforcement mismatch with the published service limit rather than a request for a quota increase. Please include the subscription ID, APIM service names, regions tested, exact error message, and reproduction details showing that the deployment succeeds up to approximately 1,003 operations before enforcing the 1,000-operation limit.

Reference: Understanding Azure API Management service limits.

Answer 1

According to the Microsoft documentation, the result you see looks like a mismatch in service enforcement or rollout, not a normal Consumption‑tier limit. The documentation now says that the Consumption limit is 3,000 API operations. Nothing in the guidance says that East US 2, a specific APIM stamp, the date a service was created, or what a customer does should lock a Consumption service to 1,000 operations.

The fact that a new service can accept 1,003 operations and then stops with the message that says "maximum number of Operations (1000)" shows that some APIM Consumption instances are still running on a backend that enforces the old 1,000 limit. I would ask Microsoft to confirm that the rollout to 3,000 operations is finished. If it is finished, please fix the backend configuration for the Consumption services. This is a quota enforcement defect, not a request for a quota.

https://learn.microsoft.com/en-gb/azure/api-management/service-limits