Share via

Azure API Management Gateway BasicV2 API Operation Limit, 100

Ryan Nichol 0 Reputation points
2026-04-15T06:40:08.7+00:00

Hi we are using the BasicV2 APIM, we successfully deployed our 160 operations to our single API. However noticed we cant do anymore deployments, or revisions, it keeps saying

Bad Request({"error":{"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"

The only way to get around it is if we delete our api completely then just redeploy it - which is not acceptable.

Same issue here but said it was resolved => https://learn.microsoft.com/en-us/answers/questions/5706204/azure-api-management-gateway-basicv2-to-standardv2?source=docs

Also where does this 100 limit come from I don't see it in any documents? I do see BasicV2 supports 10,000 operations so honestly im quite confused. Is this a bug on APIM side?

It says we can have 10000 operations and nothing to do with per api - thats only for workspaces. Really confused sorry https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#azure-api-management-limits

Thanks

Ryan

Azure API Management
Azure API Management

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


1 answer

Sort by: Most helpful
  1. Pravallika KV 14,235 Reputation points Microsoft External Staff Moderator
    2026-04-15T08:42:16.09+00:00

    Hi @Ryan Nichol ,

    Thanks for reaching out to Microsoft Q&A.

    what's happening here is that APIM enforces two different “operation” limits:

    1. A service-level limit (Basic v2 lets you have up to 10 000 operations across your entire service)
    2. A per-API limit (each individual API can only have up to 100 operations, including all its versions and revisions)

    You hit the second limit when you tried to deploy past 100 operations into a single API. It's by design.

    Here are your main options:

    1. Split your 160+ operations across multiple APIs
      • e.g. group related endpoints into separate APIs so none exceed 100 ops
    2. Consolidate or parameterize operations
      • combine paths where possible, use policies or templates to reduce the total count
    3. If you need more than 100 ops in one API, consider filing a support request from portal with existing support plan. Microsoft will be able to increase the limit.

    Hope this helps!


    If the resolution was helpful, kindly take a moment to click on User's imageand click on Yes for was this answer helpful. And, if you have any further query do let us know.


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.