Azure Database for PostgreSQL: Region Not Working for Selected Database — Deployment Failure

Question

Azure Database for PostgreSQL: Region Not Working for Selected Database — Deployment Failure

CurtMeeuwsen-7127 0

Problem description

I am attempting to create an Azure Database for PostgreSQL flexible server via an ARM template. However, the deployment fails during provisioning with the error code 'ResourceDeploymentFailure' and the underlying cause 'SkuNotAvailable'. The deployment is intended for a specific region, but the error indicates that the SKU is not available in that region at the time of deployment. I want to understand why this error occurs and how to resolve it.

Environment

Azure Database for PostgreSQL flexible server; deployment via ARM template; target resource: flexible server; region not specified in the case notes.

What I've already tried

I have attempted deployment using ARM templates with various SKU configurations and disabled high availability to see if capacity constraints were the issue. I also validated that the resource provider 'Microsoft.DBforPostgreSQL' is registered. Despite these efforts, the deployment still fails with 'SkuNotAvailable'. I checked the available SKUs in the region using CLI commands, and the SKUs I requested are listed as available, but the deployment continues to fail.

Current status

Confirmed environment

Subscription: 58b09078-d707-42e8-b133-27fd4f10e47f
Resource group: rg-nexsignals-rtb-test
Target region: East US 2 (**eastus2**)
PostgreSQL version: 18
Storage: 32 GiB
Public network access: Disabled

Completed troubleshooting

ARM deployment using Burstable Standard_B2s, 2 vCores, failed. HA was explicitly Disabled, and availability zone and standby zone were empty. ARM API version: 2025-08-01.
A subsequent Azure CLI attempt using Burstable Standard_B1ms, 1 vCore, also failed. No availability zone or HA option was supplied.
Azure’s regional list-skus output lists both SKUs.
Microsoft.DBforPostgreSQL registration was verified as Registered.

Full error returned by both attempts SkuNotAvailable: Specified SKU is not supported in this region. Please choose a different SKU.

The ARM deployment name was CustomDeployment-20261025174111, with attempted server name nex-singals-rtb-test. The CLI retry used the corrected name nex-signals-rtb-test.

Please:

Confirm these details have been added to this case.
Have an engineer investigate the subscription’s provisioning eligibility, regional capacity, and compatibility of the requested configuration.
Identify a supported configuration we can successfully provision in East US or East US 2, preferably within the Burstable tier.
Provide a specific next action based on that investigation.

0 comments

1 answer

Your answer

Answer 1

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

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.

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. 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.

Thanks.

-TP