PostgreSQL Flexible Server: all Burstable SKUs fail with SkuNotAvailable in West Europe since 2026-11-11 (General Purpose works)

Question

PostgreSQL Flexible Server: all Burstable SKUs fail with SkuNotAvailable in West Europe since 2026-11-11 (General Purpose works)

kic 0

Since 2026-11-11, every attempt to create a new Azure Database for PostgreSQL flexible server with a Burstable SKU in West Europe fails with `SkuNotAvailable`. The same configuration deployed successfully on 2026-11-09. General Purpose SKUs still deploy fine in the same subscription, region and zone.

Error (identical for every attempt; the create is accepted and fails about 3 minutes later):

{"status":"Failed","error":{"code":"ResourceOperationFailure","message":"The resource operation completed with terminal provisioning state 'Failed'.","details":[{"code":"SkuNotAvailable","message":"Specified SKU is not supported in this region. Please choose a different SKU."}]}}

Configuration

- Region: West Europe

- PostgreSQL 17 (CLI/automation) and 18 (portal)

- Storage 32 GiB, high availability disabled, geo-redundant backup disabled

- Created via Azure portal, Azure CLI 2.85.0 and Crossplane (Terraform provider)

Tests (2026-11-12)

| SKU | Tier | Zone | Subscription | Result |

|---|---|---|---|---|

| Standard_B1ms | Burstable | none | A | SkuNotAvailable |

| Standard_B1ms | Burstable | 1 | A | SkuNotAvailable |

| Standard_B1ms | Burstable | 2 | A | SkuNotAvailable |

| Standard_B1ms | Burstable | 3 | A | SkuNotAvailable |

| Standard_B2s | Burstable | none | A | SkuNotAvailable |

| Standard_B1ms | Burstable | none | B (different subscription, same tenant) | SkuNotAvailable |

| Standard_D2ds_v5 | General Purpose | none (placed in zone 2) | A | Succeeded |

Already checked

- Quota is not the issue: Burstable family 0 of 80 used, total cores 4 of 1536.

- `az postgres flexible-server list-skus --location westeurope` and the portal SKU picker still list Standard_B1ms and Standard_B2s, with zones 1, 2 and 3 and no restriction.

- Azure Service Health shows no active issue for PostgreSQL flexible server in West Europe.

- The Microsoft.DBforPostgreSQL resource provider is registered.

- A support case is open, but the answers so far have been AI-generated and only suggested retrying with zones or switching tiers.

Questions

1. Is the Burstable tier currently restricted for new PostgreSQL flexible server deployments in West Europe? Is anyone else seeing this?

2. Is it temporary? If so, is there an expected date when it will be lifted?

3. Is Burstable being phased out or capacity-restricted in West Europe long-term? If so, what is the recommended SKU for small, short-lived test servers?

4. Is there a way to request access to Burstable in West Europe for our subscriptions in the meantime?

Hemant Bharadwaj 370 Reputation points Microsoft Employee

2026-11-12T16:40:46.3733333+00:00
The error is consistent with temporary SKU capacity or a regional SKU restriction, but it does not show that Burstable is being retired. Microsoft’s PostgreSQL guidance says SkuNotAvailable can mean the SKU is unsupported in that region or temporarily unavailable; a SKU appearing in list-skus does not guarantee that a deployment can be placed at that moment. Your tests across zones and a second subscription make a single-zone or quota explanation less likely, but they cannot establish the exact capacity policy or an ETA.

Keep the support case open and share the failed deployment operation details, request/correlation IDs and UTC timestamps through the case (not in this public thread). Ask support to confirm whether West Europe Burstable placement is temporarily unavailable or whether a subscription/region restriction applies.

If you need a server before that is confirmed, use the General Purpose SKU you already verified succeeds, or evaluate another region. Check the different compute cost, latency and data-residency requirements before changing tier or region; don’t infer that a different zone will help when all three already failed.

Retry Burstable after support confirmation or a later availability check, and retain the operation error for comparison.

Reference: Resolve capacity errors for Azure Database for PostgreSQL Flexible Server (the SKU not available section describes regional support and temporary unavailability).

If you find this answer helpful, please upvote it. If this resolves your issue, please mark it as the accepted answer so that it can help others in the community.