Azure Database for PostgreSQL flexible server: SkuNotAvailable error during deployment — Region and SKU availability issues

Likely cause: this error is usually a capacity/placement mismatch (SKU + region + availability-zone/HA combination) rather than a template syntax issue, especially when behavior changed recently.

1. Verify the SKU is currently available in your target region for PostgreSQL Flexible Server. Use the region/SKU list first, then test with a smaller fallback SKU in the same region.
2. Test without optional constraints, then add them back. As a diagnostic branch, deploy with no zone pinning, no zone-redundant HA, and baseline storage settings. If that works, re-enable each setting one by one to find the blocking combination.
3. Validate ARM/Bicep parameters against current service constraints and supported combinations for the chosen region.
4. Check subscription-level limits and transient regional capacity. Even when a SKU appears generally available, deployment can still fail if capacity is constrained for that shape.
5. If it still fails, open a support request with correlation IDs (deployment operation ID, region, SKU, timestamp, template payload).

Validation checks

• A minimal deployment in the same region should succeed.
• • Retrying with a lower SKU or alternate region helps separate capacity from template issues.
• Official docs:
• • PostgreSQL compute options: https://learn.microsoft.com/en-us/azure/postgresql/compute-storage/concepts-compute
  • • Scale compute/storage: https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/how-to-scale-compute-storage
    • • ARM deployment error troubleshooting: https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/find-error-code
    • “If you find this answer helpful, please upvote it. If this resolves your issue, please mark it as the accepted answer so that it can help others in the community.”

Issue with posting answer

Issue with posting answer