Microsoft Ends Free ESU Support for SQL Server 2016
Microsoft no longer provides free Extended Security Updates (ESU) for SQL Server 2016 on Azure. The change means organisations must pay for ESU, costing up to 75% of the license price, and the decision to defer migration now carries a financial penalty. This shift impacts budgeting and regulatory c…
By Felo News Desk · Published
For the last decade, Microsoft’s Extended Security Updates (ESU) program let customers postpone moving away from older SQL Server versions by simply running the database on an Azure virtual machine. The ESU coverage was free, a cost‑saving that many organisations relied on to extend the life of their on‑premises workloads.
That arrangement ended on 15 July 2026 for SQL Server 2016. From that date, ESU coverage on Azure is no longer complimentary; it is priced the same as it would be on any other platform. The cost is roughly 75% of the on‑premises licence fee per core, billed annually for a three‑year term that runs to 17 July 2029.
What Changed?
Previously, the free ESU route was a commercial incentive that turned the pressure of end‑of‑support into Azure consumption. Microsoft used this model for three successive cycles – 2008, 2012, and 2014 – allowing customers to keep their workloads in place while still receiving critical security patches. SQL Server 2014 remains in that free‑ESU‑on‑Azure state until July 2027.
With SQL Server 2016, Microsoft removed that subsidy. The program now operates under the same pricing rules as any other ESU purchase. Enrolment after the term has started is back‑billed to the first day of the term, so delaying a decision does not save money – the invoice simply arrives later.
Financial and Regulatory Implications
For South African organisations, the change has a dual impact. First, the cost of deferral rises significantly. Microsoft’s guidance states that the total cost of a three‑year ESU subscription can be up to 2.25 times the on‑premises licence cost, a figure that can strain capital budgets that were previously justified by the free‑ESU model.
Second, the decision to run an unsupported version becomes a regulatory risk. The Protection of Personal Information Act (POPI) requires that personal data be protected with appropriate technical and organisational measures. Running a product that no longer receives security updates can be seen as a contravention of POPI’s Section 19, as demonstrated by a 2023 enforcement notice against the South African Department of Justice. Insurers also now require proof that software is supported before underwriting coverage.
Three End‑of‑Support Dates to Watch
Many organisations plan around a single deadline, but there are actually three critical dates that will affect their SQL Server estates:
- Windows Server 2016 – end of support on 12 January 2027.
- SQL Server 2017 – end of support on 12 October 2027.
- SQL Server 2016 – end of support on 15 July 2026 (now with paid ESU).
Each date forces a new decision point, and the cumulative cost of repeated deferrals can exceed the cost of an earlier migration.
Is ESU a Bridge or a Destination?
Microsoft positions ESU as a bridge for workloads that cannot yet move due to application dependencies or testing constraints. However, the bridge is time‑boxed: it covers only critical vulnerabilities and does not guarantee a regular release cadence. After three years, the same decision – to migrate or to continue deferring – must be revisited, often with a higher budget already spent.
For organisations that cannot move immediately, a mixed strategy over several years may be the most realistic approach. Yet the choice should be made once, with a clear understanding of the long‑term cost and regulatory implications, rather than being left to reactive, cycle‑by‑cycle decisions.
In contrast, Azure SQL Managed Instance offers a version‑less platform with no end‑of‑support date to plan around. New instances default to the latest SQL Server version and receive continuous updates, eliminating the need for ESU purchases. However, migrating to Managed Instance still requires careful assessment of licensing, data residency, and application compatibility.
Ultimately, the shift from free to paid ESU for SQL Server 2016 forces organisations to re‑evaluate their migration strategy, budgeting, and compliance posture. The decision to defer is no longer a cost‑free option and must be weighed against the long‑term financial and regulatory risks.
Key facts
- Microsoft stopped offering free ESU for SQL Server 2016 on Azure as of 15 July 2026.
- ESU now costs up to 75% of the on‑prem licence price, billed annually for three years.
- South African organisations face higher costs and regulatory scrutiny for running unsupported software.
- Three critical end‑of‑support dates – Windows Server 2016, SQL Server 2017, and SQL Server 2016 – require separate planning.
- Azure SQL Managed Instance offers a version‑less, continuously updated alternative without ESU costs.
- Deferral decisions must be made with a long‑term financial and compliance perspective.”]
- faq
- :
Why it matters
The removal of free ESU support changes the economics of deferral, turning a previously inexpensive delay into a costly decision that also carries regulatory risk under POPI.
Sources
- [1] techcentral.co.za — originally reported as “Support ended for SQL Server 2016 - and so did the Microsoft subsidy”
