I am unable to upgrade my Postgres version on a Azure DB Flexible Server

Question

I am unable to upgrade my Postgres version on a Azure DB Flexible Server

Brad Siefert 0

Attempting the upgrade the soon to EOL v13 from the Azure portal from the Overview tab. I receive the following error: {

"code": "ParameterOutOfRange",

"message": "The value of the 'Version' should be in: []. Verify that the specified parameter value is correct."

}

Swapnesh Panchal 1,380 Reputation points Microsoft External Staff Moderator

2025-11-07T00:49:08.2266667+00:00

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

2025-11-07T16:20:23.66+00:00

Thank you for the response, Swapnesh. The Prerequisites look to be satisfied. We will try the CLI method and provide an update soon.
Brad Siefert 0 Reputation points

2025-11-07T17:11:28.7033333+00:00

list-skus does indeed show no versions. So, the CLI result matches what we have observed on the Azure portal. What is strange is that we have a similar Dev instance (B1MS tier) in the westus location that we were able to perform a Postgres upgrade from v13 to v16. Why would Azure publish in one location and not another?
Swapnesh Panchal 1,380 Reputation points Microsoft External Staff Moderator

2025-11-11T20:14:08.0733333+00:00
The behavior you’re observing is expected because Azure PostgreSQL Flexible Server version availability can differ by region. Microsoft introduces new major versions (such as PostgreSQL v16) through a phased rollout across data centers. This approach ensures stability, compliance, and capacity readiness before global availability.

Why is v16 available in West US but not in your region?

Staged rollout: New versions are deployed gradually to selected regions first.

Compliance and infrastructure readiness: Some regions require additional validation before enabling new SKUs.

Demand-based prioritization: Regions with higher usage often receive updates earlier.

How to confirm version availability

Run the following command for your region:

az postgres flexible-server list-skus --location <region>

If v16 is not listed, it means the upgrade option isn’t yet published there.

Options if upgrade is urgent

Create a new server in a region where v16 is available and migrate using:

pg_dump / pg_restore

Azure Database Migration Service

Monitor <https://azure.microsoft.com/updates/> for announcements on regional availability.

References:

https://learn.microsoft.com/azure/postgresql/flexible-server/concepts-supported-versions
Brad Siefert 0 Reputation points

2025-11-12T00:33:32.8833333+00:00

We are not seeing any versions available, not just the latest version. We have also not been able to scale up the Flexible server to a higher tier to see if that helps.

Attached you will find some info regarding the environment. Prag Flex Svr Info.pdf
Manoj Kumar Boyini 1,330 Reputation points Microsoft External Staff Moderator

2025-11-12T14:46:02.7166667+00:00

Hi Brad Siefert,

The issue occurs because the East US region isn’t yet publishing any available PostgreSQL versions for your current SKU (Standard B1ms), which causes the error “The value of the ‘Version’ should be in: []”.Azure rolls out new PostgreSQL versions in phases, so regions like West US may receive updates earlier. Since your West US instance upgraded successfully, this confirms it’s a regional availability difference rather than a configuration issue.

As a workaround, please create a new PostgreSQL Flexible Server in West US3 (or another region where v16 is available) and migrate your data using pg_dump/pg_restore or Azure Database Migration Service.

Hope this helps. Do let us know if you have any further queries.
Manoj Kumar Boyini 1,330 Reputation points Microsoft External Staff Moderator

2025-11-13T08:21:17.2766667+00:00

Hi Brad Siefert,

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
Brad Siefert 0 Reputation points

2025-11-13T18:56:28.1766667+00:00

Thank you, Manoj. Unfortunately, moving the database alone is problematic since the app service was provisioned within a secure by default resource group. All resources would need to be moved.
VRISHABHANATH PATIL 2,070 Reputation points Microsoft External Staff Moderator

2025-11-14T03:55:01.0166667+00:00

Hi,

To ensure a smooth deployment, please avoid deploying in the East US region for now, including all dependent services, and proceed with any healthy region instead.
Brad Siefert 0 Reputation points

2025-11-14T16:39:01.35+00:00

Has Microsoft indicated how long before the East US is retired to health? Thank you.
Swapnesh Panchal 1,380 Reputation points Microsoft External Staff Moderator

2025-11-15T02:13:54.9633333+00:00

Thank you for your question! We’ll share an update as soon as possible.

For the most accurate and up-to-date information, please visit https://status.azure.com or check your Service Health dashboard in the Azure portal. These resources provide real-time updates and official communications regarding regional health.

1 answer

Your answer

Swapnesh Panchal 1,380 Reputation points Microsoft External Staff Moderator

2025-11-07T00:49:08.2266667+00:00

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

2025-11-07T16:20:23.66+00:00

Thank you for the response, Swapnesh. The Prerequisites look to be satisfied. We will try the CLI method and provide an update soon.
Brad Siefert 0 Reputation points

2025-11-07T17:11:28.7033333+00:00

list-skus does indeed show no versions. So, the CLI result matches what we have observed on the Azure portal. What is strange is that we have a similar Dev instance (B1MS tier) in the westus location that we were able to perform a Postgres upgrade from v13 to v16. Why would Azure publish in one location and not another?
Swapnesh Panchal 1,380 Reputation points Microsoft External Staff Moderator

2025-11-11T20:14:08.0733333+00:00

The behavior you’re observing is expected because Azure PostgreSQL Flexible Server version availability can differ by region. Microsoft introduces new major versions (such as PostgreSQL v16) through a phased rollout across data centers. This approach ensures stability, compliance, and capacity readiness before global availability.

Why is v16 available in West US but not in your region?

Staged rollout: New versions are deployed gradually to selected regions first.

Compliance and infrastructure readiness: Some regions require additional validation before enabling new SKUs.

Demand-based prioritization: Regions with higher usage often receive updates earlier.

How to confirm version availability

Run the following command for your region:

az postgres flexible-server list-skus --location <region>

If v16 is not listed, it means the upgrade option isn’t yet published there.

Options if upgrade is urgent

Create a new server in a region where v16 is available and migrate using:

pg_dump / pg_restore

Azure Database Migration Service

Monitor <https://azure.microsoft.com/updates/> for announcements on regional availability.

References:

https://learn.microsoft.com/azure/postgresql/flexible-server/concepts-supported-versions
Brad Siefert 0 Reputation points

2025-11-12T00:33:32.8833333+00:00

We are not seeing any versions available, not just the latest version. We have also not been able to scale up the Flexible server to a higher tier to see if that helps.

Attached you will find some info regarding the environment. Prag Flex Svr Info.pdf
Manoj Kumar Boyini 1,330 Reputation points Microsoft External Staff Moderator

2025-11-12T14:46:02.7166667+00:00

Hi Brad Siefert,

The issue occurs because the East US region isn’t yet publishing any available PostgreSQL versions for your current SKU (Standard B1ms), which causes the error “The value of the ‘Version’ should be in: []”.Azure rolls out new PostgreSQL versions in phases, so regions like West US may receive updates earlier. Since your West US instance upgraded successfully, this confirms it’s a regional availability difference rather than a configuration issue.

As a workaround, please create a new PostgreSQL Flexible Server in West US3 (or another region where v16 is available) and migrate your data using pg_dump/pg_restore or Azure Database Migration Service.

Hope this helps. Do let us know if you have any further queries.
Manoj Kumar Boyini 1,330 Reputation points Microsoft External Staff Moderator

2025-11-13T08:21:17.2766667+00:00

Hi Brad Siefert,

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
Brad Siefert 0 Reputation points

2025-11-13T18:56:28.1766667+00:00

Thank you, Manoj. Unfortunately, moving the database alone is problematic since the app service was provisioned within a secure by default resource group. All resources would need to be moved.
VRISHABHANATH PATIL 2,070 Reputation points Microsoft External Staff Moderator

2025-11-14T03:55:01.0166667+00:00

Hi,

To ensure a smooth deployment, please avoid deploying in the East US region for now, including all dependent services, and proceed with any healthy region instead.
Brad Siefert 0 Reputation points

2025-11-14T16:39:01.35+00:00

Has Microsoft indicated how long before the East US is retired to health? Thank you.
Swapnesh Panchal 1,380 Reputation points Microsoft External Staff Moderator

2025-11-15T02:13:54.9633333+00:00

Thank you for your question! We’ll share an update as soon as possible.

For the most accurate and up-to-date information, please visit https://status.azure.com or check your Service Health dashboard in the Azure portal. These resources provide real-time updates and official communications regarding regional health.

Answer 1

Hi Brad Siefert,
Welcome to Microsoft Q&A and thank you for posting your question.

That error means the portal isn’t being offered any valid target versions for an in-place major upgrade on this server right now (the service returns an empty list, so you see Version should be in: []). A few quick checks and a CLI fallback usually resolve it:

1) Verify upgrade prerequisites (common blockers)

Remove read replicas, logical replication slots, unsupported extensions (timescaledb, dblink, orafce, postgres_fdw; re-add later if supported).
Ensure ~10–20% free storage; HA will be toggled during upgrade; SSD v2 storage isn’t eligible.
If upgrading from PG11 first enable SCRAM; otherwise not required. Docs list all prechecks/limits and what the upgrade does under the hood.

2) Confirm target versions available in your region

az postgres flexible-server list-skus --location <your-region> -o table

This shows versions/SKUs the service currently advertises for your region.

3) Start the upgrade from CLI (skips the portal dropdown) You can upgrade directly to a supported later major (e.g., 16 or 17):

az postgres flexible-server upgrade -g <rg> -n <server> --version 16 --yes

The CLI command and supported targets are documented; Flexible Server supports in-place major upgrades and can skip versions.

4) If the CLI also returns ParameterOutOfRange or list-skus shows no versions This points to a regional/SKU gating or capacity issue rather than your configuration. Capture the server resource ID, region, current version, and the failing command output and open a support request so the service team can enable the proper targets for your server. (We’ve seen the same empty-list symptom reported publicly.)

References

Major version upgrade (concepts, prechecks, limits):
https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-major-version-upgrade
How to perform a major version upgrade (step-by-step): https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/how-to-perform-major-version-upgrade
Azure CLI – Flexible Server (upgrade, list-skus):
https://learn.microsoft.com/en-us/cli/azure/postgres/flexible-server?view=azure-cli-latest
Similar symptom (“Version should be in: []”) reported by users: https://learn.microsoft.com/en-us/answers/questions/5596420/not-able-to-upgrade-postgres-flexible-server-from

If you share your region/SKU, current PG version, and any extensions in use, I can suggest the exact precheck fixes and a target version to use.

Share via

I am unable to upgrade my Postgres version on a Azure DB Flexible Server

1 answer

Your answer