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

Bołoz Dawid 0 Reputation points
2025-10-24T09:30:17.55+00:00

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.

Azure Database for PostgreSQL
{count} votes

2 answers

Sort by: Most helpful
  1. Mahesh Kurva 9,725 Reputation points Microsoft External Staff Moderator
    2025-10-27T13:26:11.8866667+00:00

    Hi Bołoz Dawid,

    Greetings!!

    Could you please check

    1. 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.
    2. Try updating to a newer API version (for example @2025-08-01 as documented) for Microsoft.DBforPostgreSQL/flexibleServers.
    3. See if the allowed ‘version’ values change when you change the apiVersion.

    For more information, please refer the document:

    https://free.blessedness.top/en-us/azure/templates/microsoft.dbforpostgresql/flexibleservers?pivots=deployment-language-arm-template#sku-1

    I hope this information helps. Please do let us know if you have any further queries.

    0 comments No comments

  2. Bołoz Dawid 0 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.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.