A cloud-based coding platform connects servers and developer hubs across a glowing world map.
Azure API Management Premium v2 is now available in 35 Azure regions, according to Microsoft's Ignite 2026 announcement on November 17. The Azure Updates entry carries a "Generally Available" label, but this is not the tier's first launch. It is a regional expansion of a tier that has been generally available for a year.

A cloud-based coding platform connects servers and developer hubs across a glowing world map. What actually happened​

Microsoft first announced Premium v2 general availability in November 2025, in six public regions: Australia East, East US 2, Germany West Central, Korea Central, Norway East and UK South, with more regions "coming soon." That rollout followed a preview that was limited to the same six regions and required creating a new service instance.

Microsoft's Ignite 2026 API Management post says that Premium v2 is now offered in 35 regions. The stated goal is to let organizations deploy enterprise APIs closer to applications and users while meeting regional deployment requirements. The post says customers can provision instances through the Azure portal, REST APIs, Bicep or Azure Resource Manager templates. That post is my only source for the 35-region figure. I could not retrieve the Azure Updates page itself, so the count is not independently confirmed elsewhere.

Reading the regional footprint​

The Microsoft Learn availability table is the authoritative list, and the announcement text does not enumerate the 35 regions. The table is updated regularly, and capacity availability in Azure regions might vary. The Learn page was last updated November 11, 2026. A snapshot of that page lists Premium v2 in locations well beyond the original six. Examples include Canada Central, Central US, Brazil South, Japan East, Sweden Central, Spain Central, West Europe and West US 3.

One caution applies even to a headline of "35 regions." Microsoft marks some regions with a warning icon for temporary unavailability. Existing instances are not affected, and customers are told to consider an alternative region or a different tier in the meantime. In the November 11 snapshot, UK South was flagged for new instance creation, as was North Europe for Premium v2. Treat the count as a footprint, not a guarantee that you can create an instance in every listed region today.

Regional availability is not multi-region deployment​

This is the point most likely to trip up architects. Having Premium v2 in many regions does not mean a single instance can span them. Premium v2 and Standard v2 support multiple units distributed across availability zones, but they don't currently support multiregion deployments. Multiregion deployments are supported only in the classic Premium tier.

The practical options differ:

  • Classic Premium can run one logical instance across several regions.
  • Premium v2 gives you zone redundancy within a region. For geographic spread you would deploy separate instances and manage them yourself.

Microsoft's tier overview also lists several capabilities that are currently unavailable in v2 tiers. These include multi-region deployment, self-hosted gateway, back up and restore, and upgrade to v2 from classic tiers. The 2025 announcement's comment thread shows customers asking about multiple custom domains, multi-region, self-hosted gateways and static IP. A Microsoft representative said in that thread that these were on the roadmap. I found no announcement in the sources that these have shipped.

What the expansion does not change​

  • No migration path. Microsoft Learn says there is currently no automated tooling to migrate an existing instance from Consumption or a classic tier to a v2 instance. The v2 tiers are available for newly created instances only. A new region means a new deployment, not an in-place move.
  • Classic tiers stay. Microsoft says there are no changes to the classic Developer, Basic, Standard and Premium tiers. A Microsoft representative said in the thread that there are no plans to retire classic tiers at this time.
  • No stated price or feature change. The announcement does not say pricing, limits or features changed with the expansion.

Premium v2 context for planners​

These details are existing product facts, not part of the November 17 announcement:

  • Scale: a Premium v2 instance can scale up to 30 units.
  • Networking: Standard v2 and Premium v2 support virtual network integration for reaching isolated backends. In that mode, the gateway, management plane and developer portal remain publicly accessible. Premium v2 adds virtual network injection for full isolation of inbound and outbound gateway traffic, without route tables or service endpoints. The virtual network must be in the same region and subscription as the instance.
  • Private Link: inbound private endpoints to the gateway are supported, and the 2025 announcement said each instance supports at most 100 Private Link connections.
  • Compute: the Premium v2 gateway runs on a dedicated App Service Environment.
  • SLA: the Azure pricing page lists 99.99% for Premium v2. It requires at least one unit deployed in two or more availability zones or regions.

A practical checklist​

  1. Open the Microsoft Learn v2 availability table and confirm your target region shows Premium v2 without a temporary-unavailability marker.
  2. Decide whether you need true multi-region resilience. If so, compare classic Premium against multiple Premium v2 instances.
  3. Check the v2 "currently unavailable" feature list against your requirements, including self-hosted gateways, backup and restore, and Git-based configuration.
  4. Choose your network model: integration if you only need to reach private backends, injection if you need full isolation.
  5. Plan a new deployment, since existing instances can't be upgraded in place. Provision through the portal, REST API, Bicep or ARM templates. Microsoft's tier documentation also lists Terraform.
  6. If you want the zone-redundancy SLA, enable zone redundancy and deploy units across zones. This works only in regions that support availability zones.

Bottom line​

For teams that held back on Premium v2 because their region wasn't covered, this removes a real blocker. It matters most to enterprises with data-residency or latency requirements. The expansion does not close the feature gaps with classic Premium. Those gaps, along with the lack of automated migration, are the things to verify before committing a production API gateway to a new region.

 

References

  1. (Launched) Generally Available: Azure API Management Premium v2 Azure Updates 2026-11-17T20:00:32Z
  2. API Management pricing | Microsoft Azure azure.microsoft.com
  3. Announcing the General Availability (GA) of the Premium v2 tier of Azure API Management | Microsoft Community Hub techcommunity.microsoft.com