Share via

Azure Api Management stuck at max 100 operations when we should have 300

Andrew Heinlein 20 Reputation points
2026-05-11T18:09:15.34+00:00

We are literally having the EXACT same issue as this guy:

https://learn.microsoft.com/en-us/answers/questions/5706204/azure-api-management-gateway-basicv2-to-standardv2

Back in December we moved from Basic V2 because of the 100 operation limitation to Standard V2 so we could have up to 300 operations.

We did a prod deployment and the entire pipeline failed because of the bug mentioned in the above thread.

"statusMessage": "{\"status\":\"Failed\",\"error\":{\"code\":\"ResourceOperationFailure\",\"message\":\"The resource operation completed with terminal provisioning state 'Failed'.\",\"details\":[{\"code\":\"ValidationError\",\"message\":\"You've reached the maximum number of Operations (100) in API. Please delete one or more Operation(s) from API to continue, or consider upgrading your plan to increase the limit. For more information see: https://learn.microsoft.com/en-us/azure/api-management/v2-service-tiers-overview#resource-limits\"}]}}"

I'd LOVE to open a support ticket about this, but for some reason, Azure loves to hide the button to start a ticket and I can't find it anywhere. It really just wants me to talk to all of you guys over here who really can't do anything about it. So here you all go.

Azure API Management
Azure API Management

An Azure service that provides a hybrid, multi-cloud management platform for APIs.

0 comments

Answer accepted by question author

Rakesh Mishra 9,340 Reputation points Microsoft External Staff Moderator
2026-05-11T23:27:48.0533333+00:00

Hi Andrew, I see you already shared that thread, thank you for doing the research. I reached out to you over private message regarding some information.

With details I reached out to backend team who applied the mitigation step, and you confirmed that issue is resolved.

Also, this is a known issue, and permanent fix is being worked upon. ETA is not defined yet. Will update once I hear something.

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Amira Bedhiafi 41,641 Reputation points MVP Volunteer Moderator
    2026-05-11T18:59:52.59+00:00

    Hi Andrew !

    Thank you for posting on MS Learn Q&A.

    I found this old thread that I am sharing the link below and what I understood it might be a bug and not a normal configuration issue.

    https://learn.microsoft.com/en-us/answers/questions/5706204/azure-api-management-gateway-basicv2-to-standardv2

    The workaround applied is a backend only custom setting:

    Microsoft.WindowsAzure.ApiManagement.MAPI.Limits.Entities.Apis.Operations.Count = 500

    and since this is not available in the Azure Portal you need to open an Azure support ticket.

    Standard or Standard v2 supports 50k API operations per service instance and APIM counts API versions and revisions as part of API related resources. So receiving a hard 100 operations per API error on Standard v2 is inconsistent with the expected Standard v2 behavior.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.