Azure Database for PostgreSQL flexible server: SKU support issue in this region — Deployment failure

Mabbe-6332 0 Reputation points
2026-11-06T15:08:15.73+00:00

Problem description

I am trying to create or modify an Azure Database for PostgreSQL flexible server in the swedencentral region, but I keep encountering the error: "Specified SKU is not supported in this region. Please choose a different SKU." This issue has persisted since around 2026-10-30, and attempting deployment via Azure CLI, template-based deployment, and the Azure Portal (including incognito mode) all result in the same failure.

Environment

Azure Database for PostgreSQL flexible server in the swedencentral region, attempted through Azure CLI, template deployment, Azure Portal, and incognito session.

What I've already tried

I have tried creating the server with SKU 'Standard_B2s' and tested all availability zones 1-2-3 without success. I also reviewed the usage and quotas, noting that a burstable SKU previously worked. I confirmed the resource provider 'Microsoft.DBforPostgreSQL' is registered and that no Azure Policy or deny assignments are blocking the deployment. Additionally, I verified the SKU exists in the region via list-skus and that the resource provider is registered as 'Registered'.

Current status

The issue persists across all deployment methods, and the error "Specified SKU is not supported in this region" continues to appear. I am seeking guidance on identifying regional capacity or placement issues, and how to determine the supported SKUs and availability in my region to proceed with deployment.

Azure Database for PostgreSQL
0 comments No comments

1 answer

Sort by: Most helpful
  1. TP 165.1K Reputation points Volunteer Moderator
    2026-11-06T15:29:41.7033333+00:00

    Hi,

    Unfortunately new deployments of PostgreSQL Flexible Server Burstable SKUs are blocked in some regions. The only way around it in my experience is to use a different SKU such as General Purpose or deploy in a different region that isn't blocked yet. It isn't only your subscription, or only Sweden Central.

    Below is excerpt from documentation on how to resolve this error:

    SKU not available

    If you encounter the following error, select a different SKU type. Availability of SKU may differ across regions, either the specific SKU isn't supported in the region or temporarily unavailable. Specified SKU is not supported in this region. Please choose a different SKU.

    To provide more context, the underlying VM sizes for PostgreSQL Flexible Burstable SKUs are being retired, and they are currently subject to growth restrictions and capacity limitations. Many subscriptions are blocked from creating these sizes at all, whereas others that already have them are unable to get additional quota and/or may see failures if they deallocate and try to start VM later.

    Please see Quotas screenshot below. Note how Burstable (standardBSFamily) is End of Life:

    User's image

    There hasn't been official guidance that I am aware of as to what will happen and when with these Burstable SKUs. For instance, there are Bsv2 burstable VM sizes that are supposed to replace the retiring ones. Will they switch PostgreSQL Flexible to use these as the underlying VMs for Burstable SKUs at some point? By the way, these Bsv2 series sizes can be difficult to obtain quota for, even though they are not deprecated.

    Recently I was able to create PostgreSQL Burstable SKU in West US 2, which is in part why I know that not all regions are blocking them (yet). In months past I've created them in other regions as well, but I don't remember specific regions.

    One option to consider would be to use General Purpose v5 SKU with a 3 year reservation. That way you can get the monthly cost down as low as possible.

    Please click Accept Answer and upvote if the above was helpful.

    Thanks.

    -TP

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.