An Azure managed PostgreSQL database service for app development and deployment.
Run the PostgreSQL Flexible Server SKU query against the affected subscription, deploy with a SKU returned for centralindia, or submit an Azure PostgreSQL Flexible Server Region access request if Standard_B1ms is absent and Central India is mandatory.
Check the SKUs currently available
Set the exact subscription used by the failed deployment, then list its PostgreSQL Flexible Server SKUs:
az account set --subscription "<subscription-id>"
az postgres flexible-server list-skus \
--location centralindia \
--output table
az postgres flexible-server list-skus lists the available Flexible Server SKUs in the specified region.^1^
Review the output for:
-
Standard_B1ms - Another SKU under the Burstable tier
- If no Burstable SKU is listed, an available GeneralPurpose SKU
The exact equivalent cannot be determined without this subscription-specific output. Do not use az vm list-skus for the final selection: that command reports Microsoft Compute SKUs, whereas this deployment is governed by PostgreSQL Flexible Server capabilities.
Deploy using a returned SKU
Replace the SKU and tier in the existing command while retaining the current VNet, delegated subnet, private DNS, PostgreSQL 16, and 32-GB storage arguments.
For example, if the query returns an available General Purpose SKU:
az postgres flexible-server create \
--resource-group "<resource-group>" \
--name "<server-name>" \
--location centralindia \
--version 16 \
--tier GeneralPurpose \
--sku-name "<available-sku>" \
--storage-size 32 \
--vnet "<vnet-name-or-id>" \
--subnet "<delegated-subnet-name-or-id>" \
--private-dns-zone "<private-dns-zone-name-or-id>"
The tier and SKU must correspond: supported CLI tiers include Burstable, GeneralPurpose, and MemoryOptimized.^2^
The reported error specifically means that the selected SKU is unsupported in that region or temporarily unavailable; Microsoft’s PostgreSQL guidance is to select a different SKU type.^3^
Request access when Central India and Burstable are required
This Q&A forum cannot enable capacity or modify subscription-level regional access. If Standard_B1ms and other acceptable Burstable SKUs are absent from the command output:
- In Azure portal, open Help + support.
- Select Create a support request.
- Choose the affected subscription.
- Select the support topic for Azure Database for PostgreSQL Flexible Server.
- Create a Region access request under Service and subscription limits (quotas).
- Include:
- Region:
Central India - Requested SKU:
Standard_B1ms - Tier:
Burstable - Requested capacity: 1 vCore
- PostgreSQL version: 16
- Deployment type: private access with VNet integration
- Full
SkuNotAvailableerror and failed deployment timestamp - The output of
az postgres flexible-server list-skus --location centralindia
- Region:
- Ask Support to confirm whether the SKU is unsupported, temporarily capacity-constrained, or restricted for the subscription, and to identify the currently enabled equivalent.
The PostgreSQL capacity documentation directs unresolved provisioning cases to a Region access request under the Azure PostgreSQL Flexible Server support topic, specifying the required vCores.^3^ SKU restrictions that do not meet deployment requirements can also be escalated through an Azure Support SKU request.^4^
Registering Microsoft.DBforPostgreSQL is not the primary fix for this exact error: provider-registration failures have different documented messages. Only investigate registration if a subsequent deployment reports that the namespace is not registered.
References