Microsoft recently brought zone redundancy to the Standard v2 tier of Azure API Management, continuing to move Premium capabilities down the v2 line. Availability zone support arrived on Premium v2 at its general availability in December, alongside inbound Private Link and custom CA certificates. What's changing now is the price.
Sreekanth Thirthala, announcing the change, describes zone redundancy as distributing service capacity across multiple availability zones within a supported region, with the platform managing capacity distribution, health monitoring, and recovery. The stated benefit is protection against a datacenter-level failure without moving to an enterprise tier.
Cost is the obvious comparison, and Standard v2 wins: it starts at $700 per month for one unit, versus $2,801 for Premium v2 and $2,795 for classic Premium. The SLA is where it stops being simple. Both Premium tiers carry 99.99%, and Microsoft's pricing page footnotes that figure as requiring deployment of at least one unit in two or more availability zones or regions. Standard v2 carries 99.95%. A team enabling zone redundancy on Standard v2 gets zone distribution at the lower commitment.
That also affects the price comparison. If the Premium SLA requires two units, the like-for-like figure is roughly $5,600 per month against $700, though the two are not equivalent in what they guarantee.
The second constraint is deployment timing. Stephen W. Thomas, an Azure integration architect and Microsoft MVP, flagged it in response to the announcement:
There is one limitation: you can't enable it on an existing APIM instance. Zone redundancy must be configured when you create a new Standard v2 instance.
Microsoft's documentation states the same restriction for Premium v2: configuring zone redundancy in an existing instance isn't supported. Teams already running Standard v2 need a new instance, which means re-importing APIs and policies, moving custom domains and certificates, repointing DNS, and handling subscription keys.
Microsoft's reliability guidance for API Management has not caught up. It still states that "you must use the Premium (classic) or Premium v2 tier to configure availability zone support" and that availability zones are not supported in Basic v2 and Standard v2.
Classic Premium behaves differently. There, availability zones are enabled automatically on creation in a supported region, and can also be configured on an existing location without downtime, with changes taking 15 to 45 minutes to apply while the gateway continues serving requests. The cost is addressing: changing the availability zone configuration of an existing Premium instance changes the public virtual IP address, and the private VIP as well when the instance runs in internal virtual network mode. Microsoft lists what needs updating afterward, including DNS records, private DNS zones, firewall rules, allowlists, routing rules, and Application Gateway backend settings.
Both routes therefore carry work. On v2, the instance is rebuilt; on Premium classic, the addressing changes underneath dependencies that reference it.
The mechanism does not require two units. Microsoft's reliability documentation describes automatic zone support distributing a single unit's two compute resources across two zones, with no downtime expected during a zone outage because the resource in the unaffected zone continues working. Two units are what the Premium SLA requires, not what zone distribution needs.
What zone redundancy does not guarantee is capacity. Microsoft states that in a zone-down scenario there is no guarantee that requests for more capacity in another availability zone succeed, and that backfilling lost units happens on a best-effort basis, recommending over-provisioning for teams that need guaranteed capacity. Some data loss is also expected: configuration changes replicate between zones in around ten seconds and unreplicated changes can be lost, internal cache data is volatile and may be lost during an outage, and rate limit counters may not be current in the surviving zones.
Teams evaluating a move down from Premium should check what else they lose. The pricing table lists multi-region deployment, the self-hosted gateway, VNET injection, multiple custom domain names, and workspaces as Premium capabilities absent from Standard v2. Standard v2 does provide VNet integration, allowing the instance to reach backends isolated in a connected virtual network, but not injection, which isolates inbound and outbound traffic completely.
The consumption numbers differ too. Standard v2 includes 50 million API requests per month with additional requests at $2.50 per million, and a 1 GB built-in cache. Premium v2 includes unlimited requests and 5 GB. Scale-out costs $500 per additional unit on Standard v2 against $1,401 on Premium v2.
Microsoft frames the release partly around AI workloads, noting that APIs increasingly connect models, agents, business systems, and data platforms, and that downtime at the API layer directly affects application availability.
Enabling zone redundancy is a portal option at creation time: choose Standard v2, select a region that supports availability zones, and enable Zone Redundancy in the Availability Zones section before review and create.
The announcement doesn't state whether the capability is generally available or in preview, and it doesn't list supported regions. When Premium v2 reached general availability in December, it was available in six public regions with more described as coming.
Thomas offers the practical framing:
If you're planning a highly available APIM deployment, compare Standard v2 with Premium before defaulting to the higher tier.
Microsoft's own guidance is to review overall resiliency architecture, including backend redundancy, traffic management, and disaster recovery requirements, rather than treating gateway zone redundancy as sufficient on its own.