What changed
Azure Database for PostgreSQL Flexible Server versions 11, 12 and 13 reached the service’s Extended Support phase on August 1, 2026 after Azure standard support ended July 31. Microsoft provided those versions a one-month no-charge grace period. That grace period ends August 31, and Extended Support billing begins September 1. Enrollment is automatic for eligible unsupported versions. Microsoft says customers cannot continue running an unsupported version without Extended Support; the way to stop the charge is to complete a major-version upgrade to a currently supported PostgreSQL version. Extended Support is billed separately on a vCore-hour basis while an eligible server is running.
Why it matters
A database version that appeared to keep running normally in August becomes a new infrastructure cost in September. That makes engine age a FinOps issue as well as a maintenance issue. Teams with many vCores, HA replicas or forgotten non-production servers should inventory version 11–13 instances now, because the cost continues for as long as the server remains on an unsupported version and in a running state. The alternative is an in-place major upgrade, which itself needs extension, SQL and application compatibility testing.
Azure enrolled the old versions automatically
PostgreSQL 11, 12 and 13 entered Azure Extended Support on August 1 after their Azure standard-support window ended July 31. There is no separate opt-in switch. Microsoft says an eligible Flexible Server running an unsupported version is automatically covered, and customers cannot choose to keep the server running outside Extended Support.
The free month ends September 1
Microsoft gave versions 11–13 a one-month grace period through August 31. From September 1, Extended Support is a separate vCore-hour charge for servers in the Succeeded/running state. A stopped, failed or deleted server does not accrue that Extended Support charge for that period; billing resumes if it returns to a running unsupported version.
Paid support is a bridge, not a feature track
Extended Support includes security patches, critical bug fixes and access to technical support under the customer’s existing support plan. It does not include new features, performance enhancements, general bug fixes, performance tuning help or minor-version upgrade support. Microsoft explicitly recommends treating it as temporary migration time.
The escape hatch is an engine upgrade
To stop Extended Support charges, the server must be successfully upgraded to a PostgreSQL major version that Azure currently supports. Microsoft warns that major upgrades can expose incompatible extensions, deprecated parameters or SQL behavior changes. Non-core extensions such as pgvector or TimescaleDB are not automatically upgraded with the engine and may need separate work.
The support runway varies by version
Microsoft currently lists Extended Support ending March 31, 2027 for PostgreSQL 11, November 13, 2027 for PostgreSQL 12, and November 12, 2028 for PostgreSQL 13. Those dates create a hard outer boundary even for teams willing to pay the legacy-support premium.