PostgreSQL Flexible Server — SkuNotAvailable in East US 2

Deploy with a different SKU or region for immediate recovery, and open an Azure Database for PostgreSQL flexible server region-access request to determine whether East US 2 is temporarily capacity-constrained or restricted for this subscription.

The exact error you received is documented as meaning that the SKU is either unsupported in the region or temporarily unavailable; the SKU catalog alone cannot distinguish those conditions.^1^

What can be confirmed

• East US 2 is a supported PostgreSQL Flexible Server region, so this is not evidence that the service is generally unsupported there.^2^
• az postgres flexible-server list-skus --location eastus2 lists SKUs associated with that region.^3^
• A successful catalog lookup does not prove that capacity is currently allocatable to a particular subscription. Microsoft does not expose PostgreSQL Flexible Server’s real-time remaining regional capacity publicly.
• Because the provider is already registered, repeating provider registration is not indicated.
• The error is not the documented quota-exceeded error, which explicitly reports the current limit, current usage, and required quota. Do not treat this as a vCore quota problem unless a subsequent deployment returns that specific message.^1^

Only Azure Support can inspect the subscription-specific provisioning state and confirm whether the rejection is caused by temporary B-series capacity or a regional eligibility restriction.

Request the subscription-specific review

In the Azure portal:

1. Go to Help + support → Create a support request.
2. Select:
   • Issue type: Service and subscription limits (quotas)
   • Subscription: the affected Pay-As-You-Go subscription
   • Quota type: Azure Database for PostgreSQL flexible server
3. Request a Region access review and include:
   • Region: East US 2
   • SKUs: Standard_B1ms and Standard_B2s
   • Exact SkuNotAvailable message
   • Failed deployment timestamps, correlation IDs, and deployment operation IDs
   • Confirmation that Microsoft.DBforPostgreSQL is registered
   • Output showing that list-skus returns both sizes
   • Required capacity: 1 vCore for Standard_B1ms
4. Ask Support to confirm:
   • whether East US 2 is restricted for the subscription;
   • whether the two SKUs are temporarily capacity-constrained;
   • which region is currently provisionable for Standard_B1ms under that subscription.

Microsoft documents this support path for PostgreSQL Flexible Server quota and regional-access requests.^4^

Selecting an alternate region

No public source can guarantee which region currently has Standard_B1ms capacity for this subscription. The regional table shows that nearby regions including East US, Central US, North Central US, South Central US, and West Central US support PostgreSQL Flexible Server generally, but this is not a live capacity guarantee.^2^

For an immediate deployment:

1. Query candidate regions such as eastus, centralus, and northcentralus.
2. Attempt creation in the preferred candidate region using Standard_B1ms.
3. If deployment still returns SkuNotAvailable, try another SKU type or region as prescribed by the PostgreSQL capacity guidance.^1^
4. If the deployment pins an availability zone, retry with Availability zone: No preference or another zone; this is relevant only if the deployment also reports a zone-capacity restriction.

For production workloads, also consider whether a General Purpose SKU is more appropriate: Burstable compute is intended for low-cost, low-concurrency workloads that do not require continuous compute capacity.^2^

References

1. Resolve capacity errors for Azure Database for PostgreSQL flexible server
2. What is Azure Database for PostgreSQL flexible server?
3. az postgres flexible-server list-skus
4. Request quota increases for Azure Database for PostgreSQL flexible server