Skip Navigation
Azure
Sign In
  1. Home
  2. Azure pricing
  3. API Management pricing

API Management pricing

Publish APIs to developers, partners, and employees securely and at scale

Azure API Management allows organisations to publish APIs hosted on Azure, on-premises and in other clouds more securely, reliably and at scale. Use API Management to drive API consumption among internal teams, partners and developers while benefiting from business and log analytics available in the admin portal. This service helps provide the tools your organisation needs for end-to-end API management—everything from provisioning user roles, creating usage plans and quotas, applying policies for transforming payloads, throttling, analytics, monitoring and alerts.

Explore pricing options

Apply filters to customise pricing options to your needs.

Prices are estimates only and are not intended as actual price quotes. Actual pricing may vary depending on the type of agreement entered with Microsoft and the currency exchange rate. Prices are calculated based on US dollars and converted using Thomson Reuters benchmark rates refreshed on the first day of each calendar month. Sign in to the Azure pricing calculator to see pricing based on your current programme/offer with Microsoft. Contact an Azure sales specialist for more information on pricing or to request a price quote. See frequently asked questions about Azure pricing.

  Consumption Developer Basic Standard Premium IsolatedPreview
Purpose Lightweight and serverless version of API Management service, billed per execution Non-production use cases and evaluations Entry-level production use cases Medium-volume production use cases High-volume or enterprise production use cases Enterprise production use cases requiring high degree of isolation
Price (per unit) $- $- $- $-
Unit cost of incremental units (>1) of the same service instance charged at 50% of the first unit purchased. 		TBA7
Cache (per unit) External only 10 MB 50 MB 1 GB 5 GB 5 GB
Scale-out (units) N/A (automatic scaling) 1 2 4 12 per region
(call support to add more) 		12 per region
(call support to add more)
SLA 99.95% No 99.95% 99.95% 99.99%1 99.99%
Isolation Shared Private Private Private Private Private
Usage limits Limits apply No No No No No
Cache, external3 Yes Yes Yes Yes Yes Yes
Developer portal No Yes Yes Yes Yes Yes
Multiple custom domain names4 No Yes No No Yes Yes
Azure Active Directory integration in developer portal No Yes No Yes Yes Yes
Availability Zone support No No No No Yes No
Virtual Network support No Yes No No Yes Yes
Multi-region deployment No No No No Yes Yes
Self-hosted gateway No Yes5 No No Yes6 Yes
Estimated maximum throughput2
(per unit) 		N/A (automatic scaling) 500 requests/sec 1,000 requests/sec 2,500 requests/sec 4,000 requests/sec 4,000 requests/sec
Compute isolation No No No No No Yes

1 Requires deployment of at least one unit in two or more availability zones or regions.

2 Throughput figures are presented for information only and must not be relied upon for capacity and budget planning. Load test reflecting anticipated production conditions must be conducted to determine expected throughput accurately. Throughput is affected by the number and rate of concurrent client connections, the kind and number of configured policies, payload sizes, backend API performance, and other factors. The numbers presented in the table were obtained by testing with 1000 concurrent persistent client secure HTTP connections, minimal payload sizes, no policies configured, and a low latency backend API.

3 Bring your own Redis-compatible cache, e.g. Azure Redis Cache.

4 Available for gateway only. Limit of 20 domain names per instance. Call support to add more.

5 In the Developer tier, the self-hosted gateway feature is available at no additional cost. The number of gateway deployments is not limited, but each deployment is limited to a single gateway replica (instance).

6 In the Premium tier, the self-hosted gateway feature is available at an additional cost (see below). The number of gateway replicas (instances) in each deployment is not limited.

7 To find out the price or get provision Isolated tier service please call support.

Self-hosted gateway

The self-hosted gateway feature expands API Management support for hybrid and multi-cloud environments. Deploying the self-hosted gateway provides a consistent and unified experience, including on Kubernetes or anywhere with Azure Arc. With the self-hosted gateway feature, organisations can deploy a containerised version of the API Management gateway component to the same environments where they host their APIs, while managing them from an associated API Management service in Azure.

Price $-
Billing applies only for Premium tier deployments. Developer tier deployments are free of charge.

Azure pricing and purchasing options

Connect with us directly

Get a walkthrough of Azure pricing. Understand pricing for your cloud solution, learn about cost optimisation and request a custom proposal.

Talk to a sales specialist

See ways to purchase

Purchase Azure services through the Azure website, a Microsoft representative or an Azure partner.

Explore your options

Additional resources

API Management

Learn more about API Management features and capabilities.

Pricing calculator

Estimate your expected monthly costs for using any combination of Azure products.

SLA

Review the Service Level Agreement for API Management.

Documentation

Review technical tutorials, videos and more API Management resources.

Frequently asked questions

Frequently asked questions about Azure pricing

  • The Developer tier does not offer an SLA. Therefore, it is not suitable for production use. The Developer tier should be used for evaluations, development and test.

  • Yes. The new self-hosted gateway feature enables on-premises as well as multi-cloud deployments. The feature is available for production use in the Premium tier and evaluation purposes in the Developer tier. Please see the product page as well as the pricing section above for more details.

  • Customers can scale API Management by adding and removing units. Each unit has certain request processing capacity that depends on the service’s tier. For example, a unit of the Standard tier has an estimated maximum throughput of approximately 2,500 requests per second. As you add or remove units, capacity scales proportionately. For example, two units of the Standard tier provide an estimated throughput of approximately 5,000 requests per second.

  • All nodes within the gateway deployment share the location properties and configuration, for example, the custom domain name(s) and assigned APIs. Each gateway deployment corresponds to a gateway resource that can be created either via the Azure portal on the Gateways blade inside an API Management service or programmatically via management API.
  • The purpose of the Isolated tier is to enable use of all the features of API Management Premium tier in highly-regulated industries where compute environment isolation is a requirement.

Talk to a sales specialist for a walk-through of Azure pricing. Understand pricing for your cloud solution.

Request a pricing quote

Get free cloud services and a $200 credit to explore Azure for 30 days.

Try Azure for free
Added to estimate. Press 'v' to view on calculator
Can we help you?