If you run PostgreSQL 11, 12 or 13 on Azure Database for PostgreSQL Flexible Server, a quiet billing change went live on September 1. Azure automatically enrolled servers on unsupported PostgreSQL versions in Extended Support when standard support ended on July 31. A one-month grace period covered August at no charge. The meter started running this month.
Extended Support is Microsoft’s paid bridge for database versions the PostgreSQL community has retired. The community ended support for PostgreSQL 11 in November 2023, version 12 in November 2024, and version 13 in November 2025. Azure kept those versions running with free support through July 2026, which was already more than the community gives you. Extended Support adds up to three more years of critical security patches and technical assistance after that.
The timing is not an accident. Community retirement for PostgreSQL 14 lands in November 2026, which means a large share of Azure PostgreSQL estates are approaching the same cliff over the next few months. Microsoft is setting up the billing machinery now so that the transition is automatic rather than a fire drill. From the operator side, the practical effect is that doing nothing has a price tag attached from this month onward, and the invoice line item will show up whether or not anyone consciously decided to keep the old version.
The dates that matter
Each version gets its own window. PostgreSQL 11 runs under Extended Support until March 31, 2027. PostgreSQL 12 until November 13, 2027. PostgreSQL 13 until November 12, 2028. And PostgreSQL 14, which the community retires on November 12, 2026, moves into Extended Support on December 12, 2026 and runs until November 11, 2029.
Enrollment is automatic. You do nothing, and your unsupported servers land in Extended Support. The only way out is to upgrade to a supported version, at which point the charges stop. Billing is prorated: if you upgrade mid-month, you pay only for the days the server ran on the old version.
Two cost details worth knowing. Charges apply only to servers in a running state; stopped, deleted or failed servers do not accrue Extended Support fees. And the price is per vCore-hour, listed on the Flexible Server pricing page alongside the standard compute and storage line items.
What you get, and what you do not
The package is deliberately narrow. Extended Support includes critical security patches, critical bug fixes maintained by Microsoft, and technical support through your existing Azure support plan. It does not include new features, performance enhancements, minor version upgrades, or backporting of improvements. Your database stops aging in place but stops improving too.
Microsoft’s own guidance calls Extended Support a temporary bridge, not a destination. That is the right framing. The economics only work if the extra years buy you time for a planned migration. If they become how you run production forever, you are paying a premium per vCore for an engine version that gets nothing but survival patches.
Upgrading is the actual task
The escape hatch is a major version upgrade to PostgreSQL 15, 16, 17 or 18. Flexible Server supports in-place major version upgrades through the portal and CLI, with downtime during the cutover. The upgrade path from 13 to 16 or 17 is well trodden by now, and Azure documents the supported paths and limitations on the major version upgrade page.
Before starting: check extension compatibility, since old deployments often carry extensions that lag on newer engines. Test against a restore of production rather than a dev dataset, because planner behavior and collation changes between major versions can shift query plans in ways synthetic data hides. Schedule the cutover window and rehearse it. For a single Flexible Server instance the upgrade itself is usually the quick part; validation afterward is what eats the time.
For teams weighing the decision, the honest comparison is upgrade cost versus bridge cost. A vCore-hour surcharge on an 8-vCore production server runs 24 hours a day for as long as the estate stays on the old version, so even a modest rate compounds quickly across a fleet. An upgrade project costs engineering time once. Neither number is trivial, but only one of them ends.
Also worth a look: the version policy page shows PostgreSQL 15 support ends November 11, 2027, so if you are migrating anyway, skipping straight to 16 or 17 buys more runway than another stop on the treadmill. PostgreSQL 18 has been available on Azure since September 2025.
If your estate is small, this is a one-weekend project. If you have dozens of servers across subscriptions, start with an inventory query: list every Flexible Server, note the engine version, and anything on 13 or lower is either already billing or will be soon. The Azure announcement is on the Updates feed, with the full version matrix and FAQ on Microsoft Learn.