January 12, 2027. Microsoft confirmed the date in its February 2026 announcement: "extended support for Windows Server 2016 will end on January 12, 2027" (Microsoft Windows Server Blog). Your 2016 servers get one final monthly security update on that date. After it, Microsoft ships no security updates, no bug fixes, and no technical support for them.
One point of confusion we hear often: mainstream support ended back on January 12, 2022. What ends in 2027 is extended support, and no phase follows it (Microsoft Lifecycle).
January 2027 sounds far off in September. If you still run 2016 servers under a business-critical application, your assessment, your testing, and your budget cycle all have to fit in front of that date.
You have three, and most organizations use all three across different workloads.
Upgrade in place or rebuild on Windows Server 2025. Microsoft's recommendation, and the only option that ends the problem instead of postponing it. Nonclustered in-place upgrades support jumping up to four versions at a time, so 2016 to 2025 works. Our guide to Windows Server 2025 licensing strategies covers the core-count math, and Azure Arc hotpatching is now free for Windows Server 2025, which changes the reboot conversation for a lot of teams.
Move the workload to Azure. Rehosting is often less work than an in-place upgrade for an older application, and it takes a hardware refresh off your plate.
Buy Extended Security Updates and set a deadline. ESU is a bridge. It covers critical and important security updates only, for a maximum of three years past the end-of-support date. You get no new features, no quality fixes, no design change requests, and no technical support beyond activating the licenses and fixing problems a security update caused (Microsoft Lifecycle FAQ). We covered how the same options worked in the Windows Server 2012 cycle.
You have two ways to license ESU. Enable ESUs through Azure Arc, which bills via an Azure subscription from the product’s end of support date until cancelled. Or buy ESU licenses through commercial licensing from an EA reseller or a CSP partner (Microsoft Lifecycle FAQ). For Windows Server 2016 ESU purchased via EA reseller or CSP partner, Microsoft delivers ESUs through Azure Arc so be prepared to onboard your Windows Server machines to Arc-enabled servers (Connect Windows Server machines to Azure through Azure Arc Setup - Azure Arc | Microsoft Learn).
ESUs are now available for purchase on CSP. We're currently seeing approximate year-one list figures of $720 for a Datacenter 2-core pack and $124 for a Standard 2-core pack. Because these prices are per 2-core pack, you'll need to multiply them against the actual core counts in your Windows Server 2016 environment to estimate your cost. Treat these figures as directional and confirm current pricing before you add a line to your budget. Your total will depend on your core count.
Your ESU licenses have to match how you licensed the underlying Windows Server. On a physical core basis, you need an ESU license for every physical core on the server, with a 16-core minimum per server. On a virtual core basis, you need one for every virtual core assigned to the VM, with an 8-core minimum per VM. Edition has to match too, so Datacenter stays Datacenter.
ESU years stack. In Microsoft's words, "You may only acquire ESU Year 2 and Year 3 licenses if you've also acquired the ESU license(s) for the prior year(s)." Waiting a year to decide does not save you the first year's cost. It defers it.
Do not assume Azure makes ESU free this time. In the 2012 cycle, workloads on Azure VMs received ESUs at no additional charge, and plenty of planning decks still carry that assumption. As of April 1, 2026, Microsoft applies a consistent ESU pricing model so customers "pay the same list price for ESUs regardless of deployment location (Azure, on-premises, or other public clouds) or purchasing channel," and it names Windows Server 2016 in that change (Microsoft Licensing, Azure Arc Blog). If free ESUs in Azure were part of your reason to migrate, that benefit may no longer apply, so confirm the current terms before you finalize your plan.
1. Inventory every Windows Server 2016 instance, physical and virtual. Record edition and core count, since that is what prices the ESU.
2. Rank them by exposure. Internet-facing systems, anything touching regulated data, and anything in audit scope go first.
3. Assign a path per workload. Upgrade, migrate, or bridge with ESU. Mixing paths across workloads is fine. Leaving one undecided is what gets expensive.
4. Check your prerequisites now. ESU eligibility depends on active Software Assurance or qualifying subscription licenses (Microsoft Lifecycle FAQ), and your CALs need active SA or subscriptions licenses too.
5. Put an end date on any ESU bridge. Three years is the ceiling, and you pay double every year you stay.
The customers who handled the 2012 deadline well knew their core counts in the fall and made the call by spring. The ones who scrambled paid for a year of ESU nobody had budgeted, on top of the upgrade they still had to do.
Want a second set of eyes on the inventory and the licensing math? CloudServus is a Microsoft Solutions Partner, and our licensing practice prices your ESU exposure against an upgrade or migration path so you are comparing real numbers. Talk to an expert and we will start with your core counts.