Why arm template for postres flexible server fails with version 14 in west europe location?

Question

Why arm template for postres flexible server fails with version 14 in west europe location?

Bołoz Dawid 20

Hi All,
I am using ARM templates with Azure Pipelines to maintain the Infrastructure as Code approach in my project. I was using PostgreSQL v11, but because this is deprecated in Azure now, I upgraded it via the Azure Portal to version 14. Upgrade finished successfully.
To adapt to the version change, I modified the PostgreSQL ARM template's property version from 11 to 14. Unfortunately, during the deployment, I'm getting the error:

The value of the 'Version' should be in: [15,16,17]. Verify that the specified parameter value is correct. (Code: ParameterOutOfRange)

I want to ask why this is a problem? The server is already using version 14.18; there was no other change. The WestEurope location is supporting version 14, according to the output of az postgres flexible-server list-skus command.

 "supportedServerVersions": [
      {
        "name": "11",
        "reason": null,
        "status": null,
        "supportedFeatures": [],
        "supportedVersionsToUpgrade": [
          "12",
          "13",
          "14",
          "15",
          "16",
          "17"
        ]
      },
      {
        "name": "12",
        "reason": null,
        "status": null,
        "supportedFeatures": [],
        "supportedVersionsToUpgrade": [
          "13",
          "14",
          "15",
          "16",
          "17"
        ]
      },
      {
        "name": "13",
        "reason": null,
        "status": null,
        "supportedFeatures": [],
        "supportedVersionsToUpgrade": [
          "14",
          "15",
          "16",
          "17"
        ]
      },
      {
        "name": "14",
        "reason": null,
        "status": null,
        "supportedFeatures": [],
        "supportedVersionsToUpgrade": [
          "15",
          "16",
          "17"
        ]
      },
      {
        "name": "15",
        "reason": null,
        "status": null,
        "supportedFeatures": [],
        "supportedVersionsToUpgrade": [
          "16",
          "17"
        ]
      },
      {
        "name": "16",
        "reason": null,
        "status": null,
        "supportedFeatures": [],
        "supportedVersionsToUpgrade": [
          "17"
        ]
      },
      {
        "name": "17",
        "reason": null,
        "status": null,
        "supportedFeatures": [],
        "supportedVersionsToUpgrade": []
      }
    ],

Azure PostgreSQL 14 version is still supported until November 2026.

Mahesh Kurva 9,880 Reputation points Microsoft External Staff Moderator

2025-10-28T04:41:09.9033333+00:00

Hi Bołoz Dawid,

Sorry for the inconvenience caused.

I kindly request you to please share the details requested in the private message for further investigation.

Answer accepted by question author

1 additional answer

Your answer

Mahesh Kurva 9,880 Reputation points Microsoft External Staff Moderator

2025-10-28T04:41:09.9033333+00:00

Hi Bołoz Dawid,

Sorry for the inconvenience caused.

I kindly request you to please share the details requested in the private message for further investigation.

Answer 1

Mahesh Kurva 9,880 Microsoft External Staff Moderator

Hi Bołoz Dawid,

Greetings!!

A temporary solution provided by internal team that the 'version' value in the given api version and region is allowed.

'11','12','13','14','15','16','17','18'.

Hope this helps. Do let us know if you have any further queries.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 2

Mahesh Kurva 9,880 Microsoft External Staff Moderator

Hi Bołoz Dawid,

Greetings!!

Could you please check

If your ARM template resource type is using an older API version (say @2022-12-01 or earlier) it might have constraints baked in or no longer allow version 14 for new creations.
Try updating to a newer API version (for example @2025-08-01 as documented) for Microsoft.DBforPostgreSQL/flexibleServers.
See if the allowed ‘version’ values change when you change the apiVersion.

For more information, please refer the document:

https://video2.skills-academy.com/en-us/azure/templates/microsoft.dbforpostgresql/flexibleservers?pivots=deployment-language-arm-template#sku-1

Hope this helps. Do let us know if you have any further queries.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Bołoz Dawid 20 Reputation points

2025-10-27T22:38:01.4566667+00:00
Hi @Mahesh Kurva

Thank you for the answer!

I have already tried your suggestion. I changed the version from @2024-08-01 to @2025-08-01, and later, because I had no clue, I also tried the older version @2023-06-01. None of these attempts has solved my issue.

In the meantime, I was able to upgrade the Azure PostgreSQL server to version 15, but when I tried to deploy the ARM template again, I am getting the error with the shrank list of allowed versions to [16,17]:

{ "code": "ParameterOutOfRange", "message": "The value of the 'Version' should be in: [16,17]. Verify that the specified parameter value is correct." }

This makes no sense.

I appreciate any additional suggestions you might have.
Bołoz Dawid 20 Reputation points

2025-11-04T15:10:39.37+00:00

A temporary solution provided by Microsoft Support is to omit the version parameter from the ARM template. It allows me to proceed with the deployment for now.

Share via

Why arm template for postres flexible server fails with version 14 in west europe location?

1 additional answer

Your answer