APIM standard_v2 and premium_v2 availability in uksouth

Question

APIM standard_v2 and premium_v2 availability in uksouth

ADM Mahnaz Akhtar 0

Hello Team,

We are designing an enterprise Agentic AI platform and are evaluating Azure API Management (APIM) Standard_v2 and Premium_v2 in the UK South region.

Could someone help clarify the following:

Are APIM Standard_v2 and APIM Premium_v2 currently generally available in UK South?
Are there any known regional limitations, feature gaps, or capacity constraints for these SKUs in UK South?
Does UK South support all major networking features for these SKUs, including:
- Virtual Network Integration
  - Virtual Network Injection (Premium_v2)
    - Private Endpoints
      - Availability Zones
        
        Multi-region deployment
        
        If the service is not currently available for new deployments, is there a published roadmap or expected availability timeline?
        
        Have any customers experienced deployment failures or quota restrictions when provisioning APIM Standard_v2 or Premium_v2 in UK South?
        
        For a production enterprise workload, would Microsoft recommend UK South as a primary region for APIM v2, or are there any considerations that should be evaluated before committing to this region?

Any official Microsoft guidance, documentation references, or field experience would be greatly appreciated.

Thank you.

0 comments

1 answer

Your answer

Answer 1

APIM Standard v2 and Premium v2 are generally available products, but new instances of both tiers are currently unavailable in UK South because of a temporary regional capacity limitation; use another supported region or a different APIM tier for a new production deployment today.^1^

Current UK South status

Microsoft’s region table currently marks all of these UK South offerings with a warning:

Basic v2
Standard v2
Premium v2
Premium workspace gateway

The warning means new instance creation is temporarily unavailable. Existing instances are unaffected, and Microsoft says it is working to restore availability. This is a capacity restriction rather than an indication that Standard v2 or Premium v2 has not reached general availability.^1^

The published page does not provide a restoration date. It is updated regularly and should be treated as the authoritative status check before deployment. No committed public UK South roadmap or ETA is documented there.

Networking and resilience matrix

These capabilities apply once the selected v2 tier can be provisioned in a supported region:

Capability	Standard v2	Premium v2	Important condition
Outbound virtual network integration	Yes	Yes	VNet must be in the same region and subscription
Inbound private endpoint to gateway	Yes	Yes	Supported for the gateway
Full virtual network injection	No	Yes	Configured when creating the Premium v2 instance
Availability zones	Yes	Yes	Region must support both the tier and availability zones
Native APIM multiregion deployment	No	No	Only Premium classic supports it

Standard v2 and Premium v2 virtual network integration provides outbound access to isolated backends, while the gateway, management plane, and developer portal remain publicly accessible. Premium v2 injection provides private inbound and outbound gateway connectivity and full gateway isolation.^2^^3^

Availability-zone support requires a region that supports both the selected APIM tier and availability zones.^4^ For Standard v2 and Premium v2, Microsoft recommends at least two units for sufficient capacity during a zone outage, although zone distribution is best effort and no particular unit count is technically required.^5^

Multiregion deployment is not currently available in any v2 tier. If a single APIM instance with Microsoft-managed regional gateways is mandatory, Premium classic is the supported tier.^2^

Other current v2 gaps relevant to enterprise planning include:

Backup and restore
Resource move
Upgrade from a classic tier to a v2 tier
APIM configuration through Git
Event Grid events
Direct Management API access
Self-hosted gateway

Review the complete v2 feature comparison before selecting the tier.^2^

Capacity failures versus quota restrictions

A public Microsoft Q&A report specifically records failure to create Standard v2 in UK South, but it has no accepted or recommended answer.^6^ The official region table is therefore the stronger evidence: new APIM v2 creation is regionally capacity-blocked at present.

A quota increase should not be assumed to resolve that condition. Subscription quota controls how much a subscription may consume; it does not guarantee physical SKU capacity in a region. Capture the exact deployment error and correlation ID if provisioning is attempted after the warning is removed.

Production recommendation

Do not make a new UK South APIM v2 deployment a committed production dependency while the warning remains:

Select another region where the required tier has a green availability status. Revalidate latency, data residency, networking, and compliance requirements.
If UK geography is mandatory, evaluate UK West—but note that the current table lists Standard v2 there and does not list Premium v2.^1^
If native multiregion resilience is mandatory, evaluate Premium classic rather than Standard v2 or Premium v2.
If UK South and a v2 tier are both mandatory, open an Azure support request with the subscription, intended SKU and unit count, zone requirement, and production date. Support can assess subscription-specific deployment eligibility, but the public documentation gives no restoration commitment.
Recheck the live availability table before architecture approval and again immediately before deployment.

References