What SAM Should Count Before You Buy Microsoft ESU
Microsoft confirmed up to three years of Extended Security Updates for aging Windows. Windows 10 commercial ESU is $61 per device in year one, and the price doubles each year. Windows 10 Enterprise 2016 LTSB follows the same doubling, cumulative structure. There is no official public Windows Server 2016 ESU list price on Microsoft’s planning post. SQL Server 2016 support ends 14 July 2026, and ESU is a paid, license-tied add-on. Microsoft ESU fees land against the agreement you already have.
That’s the problem.
This is not a security story. It is a commercial model that prices time against the license you already hold. Microsoft is selling patches as a percentage of that license, or as a per-device add-on, for as long as you have not moved. The calendar is the bridge. The invoice is the product.
What Microsoft actually confirmed
On 20 February 2026 Microsoft’s Windows IT Pro blog set the dates. Windows 10 Enterprise LTSB 2016 and Windows 10 IoT Enterprise 2016 LTSB reach end of support on 13 October 2026. Windows Server 2016 follows on 12 January 2027. SQL Server 2016 is earlier than both.
Microsoft’s preferred path for Windows Server 2016 is an upgrade to Windows Server 2025. For Windows 10 LTSB holdouts, it points at Windows 11 Enterprise LTSC 2024 or Windows 10 Enterprise LTSC 2021. That is the framing: move, or buy time. ESU is a temporary bridge. It does not include new features, quality fixes, or design changes.
The published dollar figure is for Windows 10 commercial ESU: $61 per device in year one through Volume Licensing, doubling each year, cumulative. Microsoft’s LTSB 2016 note uses the same rule, sold through Volume Licensing or a CSP. IoT Enterprise LTSB 2016 ESU is sold only through IoT OEMs. Windows Server 2016 ESU had no official public list price on the February planning post. Later updates point you at the price list. Do not invent a Server 2016 figure.
The closest official precedent on Microsoft’s lifecycle FAQ is Windows Server 2012 ESU: 100 percent of the full license price, each year. SQL Server 2012 year one was 75 percent. Microsoft has said SQL Server 2016 changes that structure, and from 1 April 2026 new ESU offerings use consistent list pricing across Azure, on-premises, and other clouds. Price SQL 2016 from the license those instances sit on (not from a device count, and not from the 2012 card).
Budgets don’t plan themselves. A year-one sticker is not a three-year position.
Microsoft ESU is tied to the license, not the patch
ESU is not a security SKU you pick off a list. It is a license-tied tax. You already paid for the right to run the version. You are now being asked to pay again for the patches that used to travel with support.
That is why the Server 2012 number matters even though that program is ending. One hundred percent of the full license price, per year, is buying the license again for the privilege of staying. Windows 10 ESU looks cheap next to those percentages until you multiply $61 by every device that cannot move, then sit with year two at $122 and year three at $244.
From 1 April 2026, new ESU offerings cost the same list on Azure, on-premises, or another public cloud. The old “free ESU if you move it to Azure” path does not apply to SQL Server 2016 the way it did for earlier versions.
The final cost still depends on your licensing agreement. If your file still has a single ESU cell with a guess in it, you are not looking at a license position. You are looking at a placeholder. Pricing those SKUs against the licenses they sit on is a cost-optimization problem, not a support-status export.
This is not a criticism of the teams who have a migration on a slide. Traditional SAM tools collect comprehensively and answer slowly. They were built to prove what is deployed, not to recast it as a stay-versus-move number the CFO can use. An analysis that arrives after Microsoft has framed the meeting as extra time is a document. One that arrives during the meeting is a decision input.
If that pattern feels familiar, the problem is not your team’s maturity. A commercial question is being answered with a support-status report, not a stay-versus-move number.
The July 2026 deadline is the one that arrives first
Windows 10 had a public countdown. The Windows Server 2016 date has been quieter. SQL Server 2016 is quieter still, and it arrives first.
Support ends on 14 July 2026. Microsoft’s lifecycle page lists ESU year one from 15 July 2026. You cannot price that from a device count. You price it from the license those instances sit on.
Picture your procurement director, sixty days from 14 July. SQL Server 2016 is still in production. Windows Server 2016 is still under it. A slice of the desktop estate is still on 2016 LTSB. Your CIO wants to know how many years of ESU you are actually buying, and what that costs against the licenses you already own. If that answer takes three weeks of specialist reading, you have already lost the framing of the meeting.
Do not let Microsoft frame this as whether you want more time. The question is narrower: what are you still running, what license does it sit on, and what does one year of ESU cost against that license versus moving the workload that actually needs the year.
A bridge is only a bridge if you know which year you are buying, and why.
What to count before you buy another year
Do this in the next thirty days, as a decision pack rather than a project.
| SKU | What Microsoft has published | What you still need to know |
|---|---|---|
| Windows 10 (commercial ESU, including LTSB 2016 structure) | $61 per device year one; doubles each year; cumulative. LTSB 2016 ESU through VL or CSP. | End of support for LTSB 2016: 13 October 2026. Agreement sets the bill. Count devices that cannot move. |
| Windows IoT Enterprise LTSB 2016 | Same 13 October 2026 date. ESU only through IoT OEMs. Price doubles and is cumulative. | Do not assume the $61 Volume Licensing device price applies. Ask the OEM. |
| Windows Server 2016 | No official public ESU dollar figure on the February planning post. Preferred path: Server 2025. End of support: 12 January 2027. | Server 2012 ESU was 100 percent of full license price each year. Model a percentage of the license you actually hold. Do not invent a device sticker. |
| SQL Server 2016 | Support ends 14 July 2026: the nearest cliff. ESU is paid; 2016 changes the earlier SQL ESU structure. Consistent list pricing from 1 April 2026. | Later-year cost on your agreement, not a 2012 percentage assumed across. July is first. |
Count LTSB devices. Count Windows Server 2016 and SQL Server 2016 against the licenses they sit on. If the unpublished Server 2016 price follows the 2012 rule, you are modeling a percentage of that license, not a device sticker. July is first. A year-one line is not a three-year forecast.
Then say, in one page, whether year one is a bridge with a named exit or a habit.
Can a non-specialist brief the CIO in fifteen minutes from the pack you have today? If the answer is no, you do not have an ESU position. You have a library.
The decision layer, not another inventory
You already have discovery data and contracts in a share drive. The gap is not another inventory. The gap is turning that estate into a decision: which 2016 SKUs are still running, what license they sit on, what one year of ESU costs against that license, and what should happen before 14 July. LICENSEWARE sits on the inventory and ITSM tools you already run. It is not a rip-and-replace SAM suite. It is a decision layer: what matters, why it matters now, what should happen next. Windows Server, SQL Server, and the CALs those instances sit on have to be read against entitlement, not a support-status flag.
If you are heading into the SQL Server 2016 date or a Windows Server conversation and your current tools still need three weeks to turn “still on 2016” into a stay-versus-move number, book an Audit Readiness Review. You can also start on the free plan and run the analysis on your own data.
The question to walk in with
Do not let Microsoft frame this as extra time. The right question is: what are we still running, what license does it sit on, what does year-one ESU cost against that license, and which workloads have a named exit before we buy year two. That is a data question, not a sales question.
Windows 10 already had its public countdown. Server 2016 is quieter. SQL Server 2016 is first. The vendor will walk in with a number. The only question is whether you have yours first: current, defensible, and tied to the contract in front of you.
