Feature-based comparison of the Azure API Management tiers
APPLIES TO: All API Management tiers
Each API Management pricing tier offers a distinct set of features to meet the needs of different customers. The following table summarizes the key features available in each of the tiers. Some features might work differently or have different capabilities depending on the tier. In such cases the differences are called out in the documentation articles describing these individual features.
Important
- The Developer tier is for non-production use cases and evaluations. It doesn't offer SLA.
- The Consumption tier isn't available in the Azure operated by 21Vianet cloud.
- For information about APIs supported in the API Management gateway available in different tiers, see API Management gateways overview.
Feature | Consumption | Developer | Basic | Standard | Premium |
---|---|---|---|---|---|
Microsoft Entra integration1 | No | Yes | No | Yes | Yes |
Virtual network injection support | No | Yes | No | No | Yes |
Private endpoint support for inbound connections | No | Yes | Yes | Yes | Yes |
Multi-region deployment | No | No | No | No | Yes |
Availability zones | No | No | No | No | Yes |
Multiple custom domain names | No | Yes | No | No | Yes |
Developer portal2 | No | Yes | Yes | Yes | Yes |
Built-in cache | No | Yes | Yes | Yes | Yes |
Built-in analytics | No | Yes | Yes | Yes | Yes |
Self-hosted gateway3 | No | Yes | No | No | Yes |
TLS settings | Yes | Yes | Yes | Yes | Yes |
External cache | Yes | Yes | Yes | Yes | Yes |
Client certificate authentication | Yes | Yes | Yes | Yes | Yes |
Policies4 | Yes | Yes | Yes | Yes | Yes |
Backup and restore | No | Yes | Yes | Yes | Yes |
Management over Git | No | Yes | Yes | Yes | Yes |
Direct management API | No | Yes | Yes | Yes | Yes |
Azure Monitor metrics | Yes | Yes | Yes | Yes | Yes |
Azure Monitor and Log Analytics request logs | No | Yes | Yes | Yes | Yes |
Application Insights request logs | Yes | Yes | Yes | Yes | Yes |
Static IP | No | Yes | Yes | Yes | Yes |
1 Enables the use of Microsoft Entra ID (and Azure AD B2C) as an identity provider for user sign in on the developer portal.
2 Including related functionality such as users, groups, issues, applications, and email templates and notifications.
3 See Gateway overview for a feature comparison of managed versus self-hosted gateways. In the Developer tier, self-hosted gateways are limited to a single gateway node.
4 See Gateway overview for differences in policy support in the classic, consumption, and self-hosted gateways.