An Azure service that provides a hybrid, multi-cloud management platform for APIs.
Hi @Ryan Nichol ,
Thanks for reaching out to Microsoft Q&A.
what's happening here is that APIM enforces two different “operation” limits:
- A service-level limit (Basic v2 lets you have up to 10 000 operations across your entire service)
- 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:
- Split your 160+ operations across multiple APIs
- e.g. group related endpoints into separate APIs so none exceed 100 ops
- Consolidate or parameterize operations
- combine paths where possible, use policies or templates to reduce the total count
- 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 and click on Yes for was this answer helpful. And, if you have any further query do let us know.