{"id":9907,"date":"2026-09-06T22:43:34","date_gmt":"2026-09-06T22:43:34","guid":{"rendered":"https:\/\/pariswells.com\/blog\/?p=9907"},"modified":"2026-09-06T22:43:35","modified_gmt":"2026-09-06T22:43:35","slug":"extended-security-updates-esu-for-azure-database-for-postgresql","status":"publish","type":"post","link":"https:\/\/pariswells.com\/blog\/research\/extended-security-updates-esu-for-azure-database-for-postgresql","title":{"rendered":"Extended Security Updates (ESU) for Azure Database for PostgreSQL"},"content":{"rendered":"\n

Extended Security Updates (ESU) for Azure Database for PostgreSQL \u2013 Flexible Server were announced in January 2026 and took effect in August 2026. Extended support is automatically applied to eligible servers running unsupported PostgreSQL versions. As a result, ESU charges began accruing in August, and customers running PostgreSQL versions 11, 12, or 13 can expect to see increased billing from September 2026 onwards. Please note that ESU billing for PostgreSQL version 14 will begin in December 2026. Azure administrators should already have received advance notifications about this change, including portal banners in Azure. The only way to avoid ESU charges is to upgrade to PostgreSQL version 15 or later by performing a Major Version Upgrade (MVU).<\/p>\n\n\n\n

From a CSP partner perspective, this is an opportunity to proactively identify affected customer environments and help customers avoid unexpected ESU costs. I recommend reviewing your CSP customer estate for PostgreSQL Flexible Servers on versions 11\u201314, prioritising customers by version and workload criticality, and contacting them with an upgrade plan and target date. Where your team has delegated access to customer subscriptions, Azure Resource Graph can help identify affected servers at scale. For environments where you do not have the required access, you may want to ask the customer to run the query below and share the results with you.<\/p>\n\n\n\n

For each affected customer, consider validating application compatibility and extension dependencies, planning the MVU and an appropriate maintenance window, and confirming the expected billing impact if the server remains on an unsupported version. This can also be incorporated into your ongoing managed-services or customer-success cadence so that ESU exposure, upgrade status and blockers are tracked through to completion.<\/p>\n\n\n\n

Azure Resource Graph Explorer can also be used to identify servers running PostgreSQL versions 11, 12, 13, or 14:<\/p>\n\n\n\n

\n

resourcecontainers<\/p>\n\n\n\n

| where type =~ ‘microsoft.resources\/subscriptions’<\/p>\n\n\n\n

| project subscriptionId, subscriptionName = name<\/p>\n\n\n\n

| join kind=rightouter ( resources<\/p>\n\n\n\n

| where type =~ ‘microsoft.dbforpostgresql\/flexibleservers’ and properties.version <= 14<\/p>\n\n\n\n

| project subscriptionId, serverName = name, resourceGroup, location, version = tostring(properties.version)) on subscriptionId<\/p>\n\n\n\n

| project subscriptionName, subscriptionId, serverName, resourceGroup, location, version<\/p>\n\n\n\n

| order by subscriptionName asc, serverName asc<\/p>\n<\/blockquote>\n\n\n\n

If your team needs technical guidance to build a repeatable upgrade approach across your CSP customer base, I can help coordinate advisory support with a Data Cloud Solution Architect where appropriate.<\/p>\n\n\n\n

For additional information, please refer to:<\/p>\n\n\n\n