Thanks for reaching out to Microsoft Q&A.
In both the classic tiers (Developer, Basic, Standard, Premium) and the v2 tiers (Basic v2, Standard v2, Premium v2), certain resource limits are imposed per API Management service instance.
These limits are built-in safeguards to maintain reliability, scalability, performance within a single API Management instance, cannot be exceeded within a single instance.
- For Backends and Named Values, exceeding 100 connections or configuration entries could sometimes increase memory consumption, complexity.
- V2 tiers focus on scalable units, throughput, and network isolation, rather than focusing on unlimited backend entries.
While the per-instance limits cannot be increased directly, try below:
- Scale-Out via Multiple Units-for v2 tiers: Each unit scales throughput and load capacity but does not increase the per-instance resource caps for backends or named values.
- Deploy Multiple API Management Instances: Create additional instances and distribute APIs or backends among them. Each instance gets its own separate quota of 100 backends and 100 named values.
- For large-scale needs, using Premium v2 allows multiple regions and multiple service units, giving higher effective limit across instances.
- Combine or parameterize settings to reduce the number of named values required.
- Use an External Configuration Store: For secrets, keys, or dynamic configuration that exceeds 100 items, integrate Azure Key Vault or Azure App Configuration rather than depending completely on named values in API Management.
Hope it helps!
Please do not forget to click "Accept the answer” and Yes, this can be beneficial to other community members.
If you have any other questions, let me know in the "comments" and I would be happy to help you.