Azure Database for PostgreSQL: Region Availability Issue in Sweden Central — SkuNotAvailable

Question

Problem description

I am trying to create an Azure Database for PostgreSQL flexible server in Sweden Central with a Burstable 2-vCore SKU (B2s/B2ms). The deployment fails during creation with an error indicating that the SKU is not supported in this region, specifically returning a 'SkuNotAvailable' message.

Environment

Service: Azure Database for PostgreSQL flexible server; Region: Sweden Central; Requested compute: Burstable 2 vCores (B2s/B2ms).

What I've already tried

I have attempted to deploy the server using Terraform with the specified SKU in the region. I also checked SKU availability via Azure Portal and CLI, ensuring the correct SKU names and configurations. Additionally, I verified that the resource provider is registered and that no subscription-level quotas or policies are restricting deployment.

Current status

Currently, the deployment continues to fail with the same 'SkuNotAvailable' error, suggesting capacity restrictions or regional unavailability. I am seeking guidance on whether this SKU can be enabled in Sweden Central for my subscription or if alternative sizes or regions are recommended.

Answer 1

Hi Leonel Franchelli

Sweden Central supports Azure Database for PostgreSQL Flexible Server, but SkuNotAvailable can occur when a specific SKU is temporarily unavailable due to regional capacity constraints or subscription restrictions, even if it appears in Azure Portal or CLI.

Since you've already verified quotas, policies, and resource provider registration, I recommend the following:

1. Verify Terraform configuration

For the azurerm_postgresql_flexible_server resource, use:

sku_name = "B_Standard_B2s"
# or "B_Standard_B2ms"

If you've specified zone = "1", try removing it to let Azure select an availability zone. Burstable SKUs do not support high availability.

2. Test an alternative SKU

az postgres flexible-server list-skus \
  --location swedencentral -o table

Try another listed SKU, such as Standard_B1ms (if sufficient) or a General Purpose 2-vCore SKU. In Terraform, use the appropriate tier prefix (B_ or GP_).

However list-skus does not guarantee real-time deployment capacity.

3. Request a capacity review

If B2s/B2ms continue to fail, open an Azure Support request:

Issue type: Service and subscription limits (quotas)

• Service: Azure Database for PostgreSQL Flexible Server
• Request: Region/SKU capacity review for Sweden Central, specifically Standard_B2s and Standard_B2ms.
• Include your subscription ID, exact error message, deployment timestamp, and correlation ID.

Increasing quotas alone will not resolve a regional capacity shortage and Microsoft Support must confirm whether the requested SKUs can be provisioned for your subscription. Alternatively, use another available SKU or region.

References:

• Microsoft Learn – Resolve PostgreSQL capacity errors
• Request PostgreSQL quota/region access
• Terraform PostgreSQL Flexible Server resource