• CIO
  • CFO
4 min readBy Rullan Scott TechnologiesLast verified

Windows Server 2016 Support Ends January 2027: Upgrade, Pay for Updates, or Retire?

THE SHORT ANSWER

Windows Server 2016 extended support ends on January 12, 2027. After that, each server needs one of three plans: upgrade it in place to Windows Server 2022 or 2025, pay for up to three years of Extended Security Updates, or retire or move its workload. Waiting saves nothing, because late ESU sign-ups are billed back to January 12, 2027.

On this page

In December, an operations director asks IT for a list of servers still on Windows Server 2016. The answer is fourteen: a file server, two domain controllers, a line-of-business application running on SQL Server 2016, and several servers nobody is sure are still in use.

The application vendor hasn't confirmed support on a newer version. Finance wants to know what it costs to keep everything running for another year.

What changes on January 12, 2027?

Microsoft stops releasing security updates for Windows Server 2016 unless you buy Extended Security Updates (ESUs). Microsoft's lifecycle page lists three paid ESU years:

  • Year 1 runs to January 11, 2028.
  • Year 2 runs to January 9, 2029.
  • Year 3 runs to January 8, 2030.

What are your three options?

OptionWhat it involvesCost shapeWatch out for
Upgrade in placeMicrosoft supports a direct in-place upgrade from 2016 to 2022 or 2025 for non-clustered servers. Clusters move one version at a timeLicenses for the new version (or your existing rights), plus staff time and testingApplication support from the vendor, and the Active Directory point below
Pay for ESUsSecurity updates for up to three more years, bought per coreThrough Azure Arc, Microsoft lists $10.50 per two cores per month for Standard and $60 for DatacenterYou need Software Assurance, subscription licenses or SPLA. Late sign-ups are back-billed
Retire or moveSwitch off servers nobody uses, or move the workload to another platform or a SaaS serviceMigration effort, then lower running costsServers that turn out to be in use only once a year

For scale: a 16-core Standard server is eight two-core packs, so ESUs through Azure Arc cost about $1,000 a year at Microsoft's listed rate. Check current rates in the Azure pricing calculator for your own servers.

What do ESUs actually require?

  • Eligibility. Microsoft requires active Software Assurance, active subscription licenses, or "License-Included" services through an SPLA hosting partner.
  • No saving from waiting. Microsoft states: "Licenses provisioned after that date are back-billed to January 12, 2027." Deactivating a license doesn't avoid the charges either.
  • Not free in Azure. Earlier Windows Server versions got free ESUs in Azure. Microsoft says "Windows Server 2016 ESUs aren't included in this benefit and are a paid offering in Azure."
  • Disaster recovery copies. Microsoft says you can link paid ESU coverage to eligible Disaster Recovery Benefit servers "without incurring additional cost", as long as you follow the Disaster Recovery Benefit rules.

What do people usually miss?

Active Directory. Before you add a Windows Server 2025 domain controller, your domain and forest functional level must be at least Windows Server 2016. The 2012 R2 level is not enough.

SQL Server 2016. Many 2016 servers also run SQL Server 2016, which reached end of support on July 14, 2026. Microsoft offers paid ESUs for it in Azure and through Azure Arc. Plan the database and the operating system together.

Certificate services and other roles. A server that issues certificates or runs another infrastructure role needs its own migration plan, because other systems depend on it.

How should you decide server by server?

Sort each server into one of three groups: upgrade now, keep on ESUs with an exit date, or retire. ESUs make sense when an application vendor hasn't certified a newer version or a migration can't finish before January 12. Give every server on ESUs a date when it will leave Windows Server 2016, because the updates end in January 2030 at the latest.

Three checks you can run

CheckWhat a pass looks likeWhat a fail looks like
Can you list every Windows Server 2016 server, its workload and its owner?A complete list, including test and disaster recovery servers, with a plan for eachA list from memory, or servers nobody can account for
For servers you'll keep past January 12, have you confirmed ESU eligibility and tested enrollment?Licensing confirmed (Software Assurance, subscription or SPLA) and one server enrolled through Azure Arc as a testA plan to sort it out in January
Is your Active Directory domain and forest functional level at Windows Server 2016 or higher?Checked and confirmedStill at 2012 R2, or nobody has checked

Questions we hear

Is it safe to run Windows Server 2016 for a few months without ESUs?

After January 12, 2027, those servers stop receiving security updates, so any new vulnerability stays open. Waiting doesn't reduce the bill either. Microsoft back-bills Azure Arc ESU licenses to January 12, 2027, however late you enroll, so delaying only adds risk.

Do disaster recovery copies need their own ESU licenses?

Microsoft says you can link paid ESU coverage to eligible Disaster Recovery Benefit servers without additional cost, as long as you follow the Disaster Recovery Benefit rules for your licenses. Check that your DR servers qualify under those rules before you assume they're covered.

Can we upgrade straight from Windows Server 2016 to 2025?

For non-clustered servers, yes. Microsoft supports in-place upgrades from 2016 directly to 2022 or 2025. Clustered servers move one version at a time with rolling upgrades. Test the applications on each server first, and check with the application vendor that the new version is supported.

If we move a 2016 server to Azure, do we get free ESUs?

Not for Windows Server 2016. Earlier versions received free ESUs in Azure, but Microsoft says 2016 ESUs "aren't included in this benefit and are a paid offering in Azure." Moving a server to Azure can still make sense, but not to avoid ESU costs.

Sources

Take the eight-question Infrastructure Economics assessment