An Azure managed PostgreSQL database service for app development and deployment.
There is no published date for Burstable v2 availability in UK South; the current PostgreSQL Flexible Server regional table marks Burstable as unavailable in UK South, so use a supported General Purpose SKU in UK South or deploy Burstable v2 in a region explicitly showing Basv2 support.
Current status
- Burstable v2 is generally available as a PostgreSQL Flexible Server compute family, with SKUs including
B2ats_v2,B2afs_v2,B2als_v2, andB2as_v2.^1^ - General availability does not mean availability in every region. The official regional table currently shows:
- UK South: Burstable
❌ - UK West: Burstable
❌ - Some other regions, such as West Europe, explicitly show
✅ (Basv2).^2^
- UK South: Burstable
- The GA announcement does not publish a UK South rollout commitment or region-by-region schedule.^3^
Therefore, there is currently no public date that can be supplied for UK South.
Why the CLI result does not establish v2 availability
Standard_B1ms is a Burstable v1 SKU, while B2ats_v2 belongs to the separate Burstable v2/Basv2 family.^1^ Seeing Standard_B1ms in list-skus consequently does not indicate that any v2 SKU has reached UK South.
The CLI command is intended to list regional SKU capabilities,^4^ but the provisioning response shows whether that SKU can actually be allocated for the requested deployment. Microsoft documents your exact error as meaning that the SKU is either unsupported in the region or temporarily unavailable there.^5^
That leaves two distinct findings:
- Burstable v2: Not currently advertised as supported in UK South, with no public rollout date.
-
Standard_B1msv1: Listed by the capability query but rejected during provisioning, which can indicate current capacity or availability differing from the advertised capability.
Available paths
- Keep UK South: Change the Terraform configuration to a General Purpose SKU shown as available in that region. This is the direct supported alternative; existing General Purpose servers continuing to run does not establish capacity for a new
B1msallocation. - Keep Burstable v2: Select a region whose PostgreSQL regional table explicitly lists
Basv2, subject to your latency, residency, networking, and disaster-recovery requirements. Do not use UK West as the presumed fallback because it is also currently marked without Burstable support.^2^ - Require UK South Burstable: Open an Azure support request under Azure Database for PostgreSQL flexible server → Region/Service and subscription limits. Include:
- Region: UK South
- PostgreSQL version: 16
- Subscription type
- Failed SKU:
Standard_B1ms - Requested family:
Basv2, particularlyB2ats_v2 - Full deployment timestamp, correlation/request ID, and Terraform error
- The contradictory
list-skusoutput
Ask Microsoft to confirm separately:
- whether
Standard_B1msis temporarily capacity-constrained for the subscription; and - whether there is a private rollout estimate for Basv2 in UK South.
The public capacity guidance directs unresolved provisioning issues to a Region access request and recommends selecting a different SKU for this specific error.^5^
References
- Compute options in Azure Database for PostgreSQL flexible server
- What Is Azure Database for PostgreSQL flexible server? - Azure Database for PostgreSQL | Microsoft Learn
- Azure updates | Microsoft Azure
- az postgres flexible-server list-skus
- Resolve capacity errors for Azure Database for PostgreSQL flexible server