Azure Database for PostgreSQL flexible server in East US unavailable

Question

Azure Database for PostgreSQL flexible server in East US has been unavailable for three days. I cannot find tracking online for this issue, only the message under the Resource Health stating "Unavailable : UnknownReason (Unplanned)" and "Your Azure Database for PostgreSQL - Flexible server is currently unavailable. We are working to resolve the problem.".

Could I get more information regarding when this will be solved?

Answer 1

Hello Ruben
We have looked into the issue and the team has confirmed that there is no capacity for the requested SKU in any zone. This issue is already affecting the EAST US region. The available workarounds are:

• Alternate Regions – Deploy the same VM SKUs in North Central US or West Central US regions.
• Alternate SKUs – Use D- or E-series v3 VMs in East US, or other options like ARM v5 SKUs or similar AMD sizes. You can also try deploying in different availability zones.

Answer 2

Hello Ruben,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that your Azure Database for PostgreSQL flexible server in East US unavailable.

First, confirm it’s a platform issue (not your app) by checking Service Health for region‑scoped incidents and correlating with your server’s Resource Health; then list what you can actually provision now in East US. Use the Resource Health Events REST API and az postgres flexible-server list-skus --location eastus to discover live SKU/AZ capacity before you touch production. https://learn.microsoft.com/en-us/rest/api/resourcehealth/events?view=rest-resourcehealth-2025-05-01, https://learn.microsoft.com/en-us/rest/api/resourcehealth/events/list-by-subscription-id?view=rest-resourcehealth-2025-05-01, https://learn.microsoft.com/en-us/cli/azure/postgres/flexible-server?view=azure-cli-latest

Least‑change recovery. If a workable size exists, scale in‑region or redeploy in another AZ; otherwise, create a replacement in a nearby region using General Purpose (D‑series) or Memory Optimized (E‑series) (avoid Burstable in prod). This mirrors Microsoft’s guidance for capacity blocks and ensures you land on a currently available generation/zone. https://learn.microsoft.com/en-us/azure/postgresql/troubleshoot/how-to-resolve-capacity-errors, https://learn.microsoft.com/en-us/azure/postgresql/compute-storage/concepts-compute

If you preferred read‑replica > promote for minimal downtime when replication is feasible; otherwise perform a PITR restore using Azure Backup CLI. See: Read replica (CLI) and PostgreSQL Flexible Server restore (CLI) for exact flags and prerequisites. - https://learn.microsoft.com/en-us/cli/azure/postgres/flexible-server/replica?view=azure-cli-latest

Lastly, update DNS/connection strings (or Private Endpoint + Private DNS) and validate resolution before reopening writes; then implement zone‑redundant HA and keep a secondary region plan. Manage Private Endpoints/DNS with CLI and review Flexible Server reliability recommendations. - https://learn.microsoft.com/en-us/cli/azure/postgres/flexible-server/private-endpoint-connection?view=azure-cli-latest, https://github.com/MicrosoftDocs/azure-databases-docs/blob/main/articles/postgresql/flexible-server/how-to-manage-virtual-network-private-endpoint-cli.md, https://docs.azure.cn/en-us/reliability/reliability-postgresql-flexible-server

For more resources and snippet on Bash + Azure CLI Runbook to resolve your issues, use the below:

• https://learn.microsoft.com/en-us/rest/api/resourcehealth/events/list-by-subscription-id?view=rest-resourcehealth-2025-05-01
• https://learn.microsoft.com/en-us/cli/azure/postgres/flexible-server?view=azure-cli-latest
• https://learn.microsoft.com/en-us/azure/postgresql/compute-storage/concepts-compute
• https://learn.microsoft.com/en-us/azure/backup/backup-azure-database-postgresql-flex-restore-cli

I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.

---

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.