Share via

Documentation Gap : Azure PostgreSQL Flexible Server Minor Version Not Reflecting in all MS Sites

Sai Pavan, Chalavadi 0 Reputation points
2026-03-09T12:04:24.46+00:00

https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/concepts-supported-versions

Above page, On 9 Mar, 2026 - Still listing older versions as latest Minor releases in respective versions.
(Refer attached image - ImageFromReleaseVersionsSite)

For Eg, In 16 Version, It is still listed as 16.11 is latest minor version, where as on in below page
https://learn.microsoft.com/en-us/azure/postgresql/release-notes-maintenance/2026-march
(Refer attached image - ImageFromLatestMSNotes)

MS officially announced that 16.12 is the available latest minor version in 16 series - Same situation for 17 & 18 Series too, thsi is causing confusion among the engineers,

It would be great, MS fixes these and ensure all of their sites are reflecting the same values all the time.

Azure Database for PostgreSQL

2 answers

Sort by: Most helpful
  1. Manoj Kumar Boyini 14,015 Reputation points Microsoft External Staff Moderator
    2026-03-10T12:43:12.2933333+00:00

    Hi Sai Pavan, Chalavadi

    thanks for flagging this discrepancy. You’re right—the “Supported versions” page is still showing 16.11 even though the March release notes list 16.12 (and similar for 17.x and 18.x). Here’s what’s happening:

    • Azure onboards new minor PostgreSQL versions into Flexible Server on a rolling basis, targeting completion within three months of the community release. • As soon as a version is onboarded, it appears in the release notes (that’s why you see 16.12 in the March update). • The Supported Versions doc is updated in a separate publishing cycle and can lag by a few days (rarely more than 1–2 weeks) while we verify and publish the new values.

    If you need to track minor versions in near real-time, consider one of these approaches:

    1. Subscribe to the PostgreSQL release-notes RSS feed or monitor the release-notes page directly.
    2. Query your server’s actual minor version via CLI/REST API (for example, az postgres flexible-server show –query “version”).
    3. Set up an Azure Service Health alert for “Azure Database for PostgreSQL” maintenance updates.

    Hope that helps clear up the timing—and we’ll raise an internal doc update to get the Supported Versions page aligned as soon as possible. Let me know if you have any other questions!

    References

    1. Release notes – Azure Database for PostgreSQL (March 2026) https://learn.microsoft.com/azure/postgresql/release-notes-maintenance/2026-march
    2. Supported versions of PostgreSQL in Azure Database for PostgreSQL (Flexible Server) https://learn.microsoft.com/azure/postgresql/configure-maintain/concepts-supported-versions
    3. How soon minor versions are onboarded to Flexible Server https://learn.microsoft.com/azure/postgresql/release-notes/release-notes#how-soon-can-i-expect-a-minor-version-on-boarded-on-flexible-server-after-it-has-been-released
    4. Azure Database for PostgreSQL version policy – minor version support https://learn.microsoft.com/azure/postgresql/configure-maintain/concepts-version-policy#minor-version-support
    5. Automatic minor version updates in Azure Database for PostgreSQL Flexible Server https://learn.microsoft.com/azure/postgresql/flexible-server/concepts-supported-versions#postgresql-minor-version-updates

    Was this answer helpful?


  2. Q&A Assist
    2026-03-09T12:04:42.2833333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The supported-versions article and the maintenance release notes are updated on different cadences, so short-lived mismatches can occur after a new minor version is announced.

    The current documented state is:

    • The supported versions page lists PostgreSQL 18, 17, 16, 15, 14, 13, 12, and 11, with minor versions that are periodically updated as part of the service’s automatic patching process.
    • The January 2026 and February 2026 release notes explicitly call out support for newer minor versions (18.1, 17.7, 16.11, 15.15, 14.20, 13.23) and indicate that new servers are onboarded to the latest engine version and existing servers are upgraded during their next maintenance window.

    When the release notes show a newer minor version than the supported-versions page, the release notes represent the most recent service behavior, and the supported-versions article is expected to be aligned shortly afterward. During that window:

    • New servers may already be created on the newer minor version mentioned in the release notes.
    • Existing servers are upgraded automatically during their scheduled maintenance, per the version policy.

    For engineering decisions during such discrepancies:

    1. Treat the release notes as the authoritative source for “what is rolling out now” (new minors, features, regions).
    2. Treat the supported-versions page as the baseline for “which major versions are supported” and the general minor-version policy (automatic upgrades during maintenance).
    3. If a specific minor version is critical for a workload and documentation appears inconsistent, open an Azure Support ticket so the product team can both confirm the rollout status for that region and correct any documentation drift.

    This behavior is consistent with the documented version policy:

    • Minor versions are automatically upgraded to the Azure-preferred PostgreSQL version during periodic maintenance.
    • New minor versions are announced in the release notes as they become available.

    References:

    Was this answer helpful?

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.