When did SQL Server 2016 go out of support?

July 14, 2026. That was the end of extended support, which had been security-updates-only since mainstream support ended in 2021. Microsoft's lifecycle page expresses the same moment as 7/15/2026 6:59:59 AM Pacific — that is the instant support lapses, not a different date, and it is also when the first Extended Security Updates term begins. SQL Server 2016 followed the Fixed Lifecycle Policy across every edition: Developer, Enterprise, Enterprise Core, Express, Standard, and Web. Express is worth calling out, because it is free, it gets installed by application vendors without a licensing conversation, and it goes out of support on exactly the same date as Enterprise.

What does an ESU subscription actually cover?

Security fixes that the Microsoft Security Response Center rates as Critical, and nothing else. No new features, no functional improvements, no customer-requested fixes, and no fix if you hit a non-security bug. There is also no release cadence — Microsoft publishes an ESU only if a qualifying vulnerability is found, so quiet months are the expected behaviour, not evidence that something is broken. One more limit that catches people: an ESU licence does not include support for the underlying SQL Server version. Support is confined to problems with the updates themselves, such as a regression introduced by a specific patch.

How much do SQL Server 2016 ESUs cost?

Microsoft's own guidance puts ESUs at approximately 75% of the on-premises licence cost annually, and Azure bills the subscription hourly with the ability to cancel at any time. Treat that as a planning figure and confirm against your own agreement, because the number is a percentage of what you actually pay for the edition and core count you run — Enterprise per-core on a large box is a very different absolute figure from Standard on a two-socket server. The subscription also cancels automatically when you upgrade to a supported version or migrate into Azure SQL, so the meter stops when the work lands rather than at a renewal boundary.

What are the SQL Server 2016 upgrade options?

Four, and they suit different situations. Upgrade in place or side-by-side to a current SQL Server — 2022 carries extended support to 2033, and 2025 to 2036, so choosing 2025 buys three more years of runway for the same project effort. Move to Azure SQL Managed Instance, which under the always-up-to-date policy is versionless, meaning end of support stops being an event you plan for at all — at the cost of networking complexity, a 32 TB ceiling across the instance, and some documented T-SQL differences to test. Move to an Azure VM and upgrade SQL Server during the migration, if you need OS-level control or features Managed Instance does not expose. Or stay on 2016 and subscribe to ESUs, which is a scheduling instrument for an application genuinely pinned to 2016, not a destination. Most mid-market estates end up using two of these rather than picking one.

We only ever installed GDR updates. Does that matter for ESUs?

It does, and it is worth handling before you subscribe rather than after. Extended Security Updates for SQL Server 2016 include the most recent Cumulative Update. If your servicing history is General Distribution Release updates only, you have never taken those CU changes, so the first ESU you install will carry them all at once. Microsoft's guidance is to install and validate the latest CU at the time you subscribe, rather than discovering the regression risk during an emergency patch for an actively exploited vulnerability. That is a scheduled maintenance window now instead of an unscheduled one later.

Field notes · 10 min read · August 7, 2026

SQL Server 2016 End of Support: ESU or Upgrade?

SQL Server 2016 reached end of extended support on July 14, 2026. Extended Security Updates run in three yearly terms from July 15, 2026 through July 17, 2029 — but unlike SQL Server 2012 and 2014, moving a 2016 instance to an Azure VM no longer earns them for free.

The short version: SQL Server 2016 reached end of extended support on July 14, 2026. Extended Security Updates are available for three years, in yearly terms running July 15, 2026 to July 13, 2027, July 14, 2027 to July 18, 2028, and July 19, 2028 to July 17, 2029. They are not free, they are Critical-severity fixes only, and the trick that made them free for SQL Server 2014 does not work here.

Every end-of-support date generates the same two conversations. The first is the one everybody has: what do we upgrade to, and when. The second is the one that actually decides the budget, and it usually happens six weeks later, when somebody discovers the mitigation they were counting on doesn't apply to this product.

For SQL Server 2016 that second conversation has a specific shape, and it is worth having first.

The escape hatch that closed

For SQL Server 2012 and SQL Server 2014, there was a well-known move: lift the instance onto an Azure VM as-is and receive Extended Security Updates at no additional cost. It was a genuinely good deal, it was widely used, and it shaped how a lot of teams think about end-of-support economics. It still works for SQL Server 2014 today.

It does not work for SQL Server 2016. Microsoft Learn states it in a section of its own, with no hedging:

"Starting with SQL Server 2016 (13.x), migrating your workload to SQL Server on Azure VMs no longer provides free access to ESUs for SQL Server 2016 (13.x) instances."

The same applies to Azure VMware Solution: SQL Server 2014 workloads moved there get free ESUs, and SQL Server 2016 workloads can subscribe but are not eligible for the free ones. You can still run 2016 on an Azure VM. You can still subscribe to ESUs there, by registering the VM with the SQL IaaS Agent extension. You simply pay.

This matters more than a footnote should, because it inverts a business case rather than adjusting it. "Move it to Azure and the security updates come free for three years" was a migration justification that paid for the move. For a 2016 instance, that line is now a cost rather than a saving, and any plan still carrying it needs the numbers run again before anyone commits.

ESUs are a connectivity decision, not just a purchase

The second surprise is architectural. Getting ESUs onto a SQL Server 2016 instance is not a licensing transaction that ends with a PO. The delivery mechanism is Azure Arc, and for anything outside Azure — on premises, another cloud, a hosting provider — Microsoft is explicit that if you cannot connect the instance to Azure Arc, you do not qualify for the offer.

For instances already on Azure VMs, the equivalent is registering with the SQL IaaS Agent extension. Either way, the machine that has been sitting quietly in a rack for nine years now needs an outbound relationship with Azure, and somebody has to own that. Connecting a SQL Server instance to Azure Arc is free of charge, so the cost is not the obstacle — the obstacle is that an air-gapped or heavily-restricted instance is exactly the kind of instance most likely to still be running 2016, and exactly the kind that cannot meet this requirement.

There is a documented path for genuinely disconnected instances: you may be eligible to purchase ESUs through volume licensing and register the instance manually in the Azure portal. That route runs through your Microsoft account team rather than through a portal button, so it needs lead time.

The useful consequence: the Azure Arc route also removes the Software Assurance requirement. The traditional ESU entitlement needs Software Assurance under an EA, EAS, SCE, or EES. Microsoft documents an alternative — connect to Azure Arc and enable pay-as-you-go billing to receive ESUs without Software Assurance. For a mid-market shop whose SA lapsed years ago on a server nobody was changing, that is often the difference between having an option and having none.

What an ESU subscription buys, and what it doesn't

An ESU subscription is a narrower instrument than the phrase "extended support" suggests, and the gap between what people assume and what it covers is where the risk lives.

Critical-rated fixes only. Microsoft publishes an ESU if and when a vulnerability is rated Critical by the Microsoft Security Response Center. Anything below that bar is not shipped.
No release cadence. Because ESUs are issued only when a qualifying vulnerability appears, there is no monthly rhythm. A quiet quarter is the design working, not a delivery failure — but it also means "we're on ESU" is not the same statement as "we're patched monthly," and anyone reporting the estate's patch posture to an auditor or an insurer should be careful not to conflate the two.
No bug fixes. Non-security defects are not addressed. If you hit a functional bug in year two, the answer is to upgrade.
No product support. An ESU licence does not include support for the underlying SQL Server version. Support is limited to deploying, installing, and activating the updates themselves — including a regression introduced by one of them, but not the database engine's behaviour generally.
Three years, then nothing. The ladder ends July 17, 2029. There is no fourth year to plan around.

Priced at roughly 75% of the on-premises licence cost annually, three full years of ESUs approaches the cost of just buying the current version — which is, transparently, the point of the pricing. ESUs are designed to buy scheduling flexibility for an application that genuinely cannot be recertified yet, not to be a cheaper alternative to modernising.

The four paths, and who each one is actually for

Path	Best when	What it costs you
Upgrade in place or side-by-side to SQL Server 2022 or 2025	The application vendor supports a current version, and you want to stay on infrastructure you control.	Up-front licence and hardware, plus a recertification cycle. SQL Server 2022 has extended support to 2033; SQL Server 2025 to 2036. Choosing 2025 buys three more years of runway for the same project effort.
Azure SQL Managed Instance	You want the version treadmill to stop permanently. With the always-up-to-date policy, MI is versionless — end of support stops being an event you plan for.	Networking complexity (ExpressRoute or VPN Gateway), a 32 TB ceiling across all databases in the instance, and a set of documented T-SQL differences to test against.
Azure VM, upgraded during the move	You need OS-level control, or the app needs the filesystem, agents, or SQL features MI doesn't expose.	You still manage SQL Server and the OS. You do get out of the hardware business, and the licence can move with you.
Stay on 2016 and subscribe to ESUs	A vendor application is pinned to 2016 and recertification genuinely isn't available yet.	~75% of licence cost per year, an Azure Arc or SQL IaaS Agent connection, Critical-only fixes, and a hard stop in 2029. This is a scheduling instrument, not a destination.

Most mid-market estates end up splitting across two of these rather than picking one. The databases behind line-of-business applications with a supported current release get upgraded; the one instance under a vendor product that hasn't shipped a compatible version gets an ESU subscription and a calendar entry. That is a reasonable outcome. What isn't reasonable is buying ESUs for the whole estate because nobody has been through it instance by instance.

If SharePoint runs on it, you have two deadlines, not one

SQL Server 2016 is very often the database tier underneath a SharePoint farm, and SharePoint Server 2016 and 2019 went out of support on the same day — July 14, 2026. The two tiers do not have the same options.

SQL Server 2016 has a paid three-year ESU ladder. SharePoint Server 2016 and 2019 have no ESU programme at any price. There is nothing to buy. That asymmetry matters for sequencing: an ESU subscription on the database can hold the floor while the SharePoint migration runs, but the reverse is not available, and a plan that treats "the SharePoint platform" as a single dated risk will get the harder half wrong. We covered the application side and its three viable routes in SharePoint 2016 and 2019 EOL: three paths.

What to do in the next 30 days

Inventory every instance, including the ones nobody bought. SQL Server Express ships inside third-party applications, gets installed by a vendor's setup wizard, and never appears in a licensing review because it is free. It went out of support on the same date as Enterprise. Discovery by installed service, not by purchase records.
Map each instance to the application that depends on it, and find out what that vendor supports. This is the step that determines everything downstream, and it is the one that takes calendar time rather than engineering time, because it depends on somebody else answering an email.
Check your servicing history before you subscribe to anything. If an instance has only ever taken GDR updates, install and validate the latest Cumulative Update now — ESUs include it, and you would rather absorb that change in a planned window than during an emergency patch.
Decide the Azure Arc question early. ESUs depend on it for anything outside Azure. If an instance sits in a network that cannot reach Azure, you need either a network change or the volume-licensing route through your Microsoft account team — and both take longer than clicking subscribe.
Re-run any business case that assumed free ESUs on an Azure VM. If a migration was justified on that basis, the justification changed for 2016 instances.

Sources and further reading

The 30-second version

SQL Server 2016 left extended support on July 14, 2026. Extended Security Updates are available for three years — through July 17, 2029 — at roughly 75% of licence cost annually, covering Critical-rated fixes only, with no release cadence, no bug fixes, and no product support. Two things surprise people. First, the free-ESU-on-Azure-VM route that worked for SQL Server 2012 and 2014 explicitly does not apply to 2016, so any migration business case built on it needs re-running. Second, ESUs are delivered through Azure Arc, so an instance that cannot reach Azure cannot receive them without going through volume licensing — though that same Arc route also lets you buy ESUs without Software Assurance, which is often the only viable option for a mid-market shop whose SA lapsed. Inventory every instance including the free Express installs nobody purchased, map each to the application that pins it, and treat ESUs as a scheduling instrument rather than a destination.

Questions we get asked

When did SQL Server 2016 go out of support?: July 14, 2026. That was the end of extended support, which had been security-updates-only since mainstream support ended in 2021. Microsoft's lifecycle page expresses the same moment as 7/15/2026 6:59:59 AM Pacific — that is the instant support lapses, not a different date, and it is also when the first Extended Security Updates term begins. SQL Server 2016 followed the Fixed Lifecycle Policy across every edition: Developer, Enterprise, Enterprise Core, Express, Standard, and Web. Express is worth calling out, because it is free, it gets installed by application vendors without a licensing conversation, and it goes out of support on exactly the same date as Enterprise.
Can we just move it to an Azure VM and get free ESUs?: No — and this is the single most common wrong assumption about the 2016 deadline. That route worked for SQL Server 2012 and still works for SQL Server 2014, so teams reasonably expect it to carry forward. It does not. Microsoft Learn states it plainly: starting with SQL Server 2016, migrating your workload to SQL Server on Azure VMs no longer provides free access to ESUs. You can still run 2016 on an Azure VM and you can still subscribe to ESUs there through the SQL IaaS Agent extension — you just pay for them. If a migration business case was built on free ESUs, the numbers need re-running before anyone signs.
What does an ESU subscription actually cover?: Security fixes that the Microsoft Security Response Center rates as Critical, and nothing else. No new features, no functional improvements, no customer-requested fixes, and no fix if you hit a non-security bug. There is also no release cadence — Microsoft publishes an ESU only if a qualifying vulnerability is found, so quiet months are the expected behaviour, not evidence that something is broken. One more limit that catches people: an ESU licence does not include support for the underlying SQL Server version. Support is confined to problems with the updates themselves, such as a regression introduced by a specific patch.
Do we need Software Assurance to buy ESUs?: Not necessarily any more. The traditional route requires Software Assurance under an Enterprise Agreement, Enterprise Agreement Subscription, Server and Cloud Enrollment, or Enrollment for Education Solutions. But Microsoft also documents an alternative: connect the instances to Azure Arc and enable pay-as-you-go billing to receive ESUs without Software Assurance. Connecting a SQL Server instance to Azure Arc is itself free of charge. For a mid-market shop that let Software Assurance lapse — which is common once a server stops changing — the Arc route is usually the difference between having an ESU option and having none.
How much do SQL Server 2016 ESUs cost?: Microsoft's own guidance puts ESUs at approximately 75% of the on-premises licence cost annually, and Azure bills the subscription hourly with the ability to cancel at any time. Treat that as a planning figure and confirm against your own agreement, because the number is a percentage of what you actually pay for the edition and core count you run — Enterprise per-core on a large box is a very different absolute figure from Standard on a two-socket server. The subscription also cancels automatically when you upgrade to a supported version or migrate into Azure SQL, so the meter stops when the work lands rather than at a renewal boundary.
Our SharePoint farm runs on SQL Server 2016. Does that change anything?: Yes, and it is the most common version of this problem in the mid-market. SharePoint Server 2016 and 2019 went out of support on the same day, July 14, 2026 — but the two tiers do not have the same escape route. SQL Server 2016 has a paid three-year ESU ladder; SharePoint Server 2016 and 2019 have no ESU programme at any price. So the database tier can be bought time and the application tier cannot. Any plan that treats the farm as one deadline will underestimate the SharePoint side and overestimate how much room the ESU ladder really buys.
What are the SQL Server 2016 upgrade options?: Four, and they suit different situations. Upgrade in place or side-by-side to a current SQL Server — 2022 carries extended support to 2033, and 2025 to 2036, so choosing 2025 buys three more years of runway for the same project effort. Move to Azure SQL Managed Instance, which under the always-up-to-date policy is versionless, meaning end of support stops being an event you plan for at all — at the cost of networking complexity, a 32 TB ceiling across the instance, and some documented T-SQL differences to test. Move to an Azure VM and upgrade SQL Server during the migration, if you need OS-level control or features Managed Instance does not expose. Or stay on 2016 and subscribe to ESUs, which is a scheduling instrument for an application genuinely pinned to 2016, not a destination. Most mid-market estates end up using two of these rather than picking one.
We only ever installed GDR updates. Does that matter for ESUs?: It does, and it is worth handling before you subscribe rather than after. Extended Security Updates for SQL Server 2016 include the most recent Cumulative Update. If your servicing history is General Distribution Release updates only, you have never taken those CU changes, so the first ESU you install will carry them all at once. Microsoft's guidance is to install and validate the latest CU at the time you subscribe, rather than discovering the regression risk during an emergency patch for an actively exploited vulnerability. That is a scheduled maintenance window now instead of an unscheduled one later.

Related service

Server end-of-support service

Written by the team at Pro IT NW · Senior-led Microsoft project consultancy · Seattle / USA-wide.

Share on LinkedIn Follow Pro IT NW