Azure Database for PostgreSQL: SkuNotAvailable Error in East US 2 When Scaling to Burstable Servers

Question

Azure Database for PostgreSQL: SkuNotAvailable Error in East US 2 When Scaling to Burstable Servers

TomislavMarkovski-3799 0

Problem description

I am trying to scale my Azure Database for PostgreSQL flexible server in East US 2 from a General Purpose tier (Standard_D2ds_v5) to a Burstable tier (Standard_B1ms). However, all attempts to use Burstable sizes result in a SkuNotAvailable error. The issue began on October 29, 2026, and persists despite multiple retries. The same request succeeds in other regions, indicating a regional capacity issue.

Environment

Service: Azure Database for PostgreSQL flexible server; Current compute tier: Standard_D2ds_v5; Target compute tier: Burstable (Standard_B1ms); Region: East US 2; No specific server settings documented.

What I've already tried

I verified that high availability is disabled before attempting to scale down to Burstable. I tried resizing the server to Standard_B1ms in East US 2, but the server went offline, and the resize operation timed out after 2.5 hours. I also checked the available SKUs in East US 2 using Azure CLI, and despite Standard_B1ms appearing in the list, all attempts to allocate it in the current placement failed with SkuNotAvailable. I confirmed that the server's current zone is Zone 2, which is not listed for Standard_B1ms, possibly explaining the failure. I attempted to create new servers in different zones within East US 2, but they also failed with SkuNotAvailable.

Current status

Currently, all attempts to allocate Burstable SKUs in East US 2 are failing with SkuNotAvailable, even though these SKUs are listed as available regionally. The issue appears to be specific to the region's capacity or allocation for the Burstable family. I am seeking guidance on why this regional unavailability occurs and whether Burstable SKUs can be enabled for my server in East US 2, preferably in Zone 2, or alternative solutions to achieve my scaling goals.

0 comments

1 answer

Your answer

Answer 1

Hi,

Unfortunately new deployments of PostgreSQL Flexible Server Burstable SKUs are blocked in some regions (East US 2 is one). You are attempting to change existing deployment to Burstable, which is basically the same and blocked as well.

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 East US 2 region.

Since you are already on General Purpose then I would suggest staying with existing SKU and possibly purchasing 3 year reservation to reduce cost.

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.

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

Thanks.

-TP