| title | description | services | author | ms.service | ms.topic | ms.date | ms.author |
|---|---|---|---|---|---|---|---|
Feature-based comparison of Azure API Management tiers | Compare API Management tiers based on the features they offer. See a table that summarizes the key features available in each pricing tier. | api-management | dlepow | azure-api-management | concept-article | 10/15/2024 | danlep |
[!INCLUDE api-management-availability-all-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 US Government cloud or the Microsoft 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 | Basic v2 | Standard | Standard v2 | Premium | Premium v2 (preview) |
|---|---|---|---|---|---|---|---|---|
| Microsoft Entra integration1 | No | Yes | No | Yes | Yes | Yes | Yes | Yes |
| Virtual network injection support | No | Yes | No | No | No | No | Yes | Yes |
| Private endpoint support for inbound connections | No | Yes | Yes | No | Yes | Yes (preview) | Yes | No |
| Outbound virtual network integration support | No | No | No | No | No | Yes | No | Yes |
| Multi-region deployment | No | No | No | No | No | No | Yes | No |
| Availability zones | No | No | No | No | No | No | Yes | No |
| Multiple custom domain names for gateway | No | Yes | No | No | No | No | Yes | No |
| Developer portal2 | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Built-in cache | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| External cache | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Autoscaling | No | No | Yes | No | Yes | No | Yes | No |
| API analytics | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Self-hosted gateway3 | No | Yes | No | No | No | No | Yes | No |
| Workspaces | No | No | No | No | No | No | Yes | No |
| TLS settings | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Client certificate authentication | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Policies4 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Credential manager | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Backup and restore | No | Yes | Yes | No | Yes | No | Yes | No |
| Management over Git | No | Yes | Yes | No | Yes | No | Yes | No |
| Azure Monitor metrics | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Azure Monitor and Log Analytics request logs | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Application Insights request logs | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Static IP | No | Yes | Yes | No | Yes | No | Yes | No |
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, v2, consumption, and self-hosted gateways.
