Azure Database for PostgreSQL flexible server - Upgrade unavailable due to regional capacity constraints

Question

We have this warning message: "Your server version will lose standard Azure support on March 31, 2026. Upgrade now to avoid extended support charges starting August 1, 2026."

But upgrading is not available to us as-is. The "Upgrade" option from the Overview blade is grayed out with this message on hover: "Upgrade unavailable due to regional capacity constraints. Contact support to discuss alternative options."

We have this same message for both our dev and prod PostgreSQL flexible servers.

Answer 1

Hi James Green

it looks like you’re hitting the “Upgrade unavailable due to regional capacity constraints” banner, which essentially means your Azure region doesn’t currently have the spare capacity to do an in-place major version upgrade of your PostgreSQL flexible servers. Here are a few paths you can explore:

Open a support ticket for a capacity‐availability exception

• Since the portal explicitly tells you to “contact support,” opening a support case is the fastest way to see if Microsoft can temporarily prioritize capacity in your region so you can proceed with the upgrade.

Move to a region/zone with available capacity

  - If you can’t wait, you could spin up a new flexible server in a region (or availability zone) that supports your target PostgreSQL version and migrate your data. • Use pg_dump/pg_restore or logical replication to migrate data • Update your app connection strings once cutover is complete
  
  Wait for capacity to free up
  
     - Azure regularly rotates in new capacity. If you’re not blocked by a hard deadline, you can keep an eye on the portal; the “Upgrade” button should become available again once capacity is replenished.
     
     Consider alternative upgrade paths
     
        - If an in-place upgrade isn’t critical, you can deploy a fresh flexible server on the newer PostgreSQL version in the same region (if capacity permits) and do a dump/restore to minimize downtime.
        

Next steps/questions for you • Which Azure region (and availability zone) are your dev and prod servers deployed in? • What major version are you running now, and which version are you trying to upgrade to? • Do you have any read replicas or other cross-region dependencies? • How critical is hitting the March 31, 2026 upgrade deadline for you (e.g. can you wait a few days or do you need it ASAP)?

That info will help us narrow down the best approach—whether it’s a support‐driven capacity request, a cross-region restore, or just waiting until Azure frees up capacity.

Reference docs

• Major version upgrades in Azure Database for PostgreSQL flexible server https://learn.microsoft.com/azure/postgresql/flexible-server/concepts-major-version-upgrade
• Resolve capacity errors for Azure Database for PostgreSQL flexible server https://learn.microsoft.com/azure/postgresql/troubleshoot/how-to-resolve-capacity-errors