Windows Server 2016 end of life: what changes in January 2027
Windows Server 2016 extended support ends on January 12, 2027. What stops, how Server 2016 ESU through Azure Arc works and what it costs, upgrade paths to 2019, 2022 and 2025, a decision table by workload and a timeline to January.
Windows Server 2016 sits under file shares, domain controllers and line-of-business apps that nobody has touched in years. When support ends on January 12, 2027, those servers keep booting, but Patch Tuesday stops shipping fixes for them unless they're enrolled in paid Extended Security Updates (ESU). This server 2016 end of life guide takes you from an inventory to a plan for each workload, with ESU as the bridge for servers that can't move in time.
TL;DR
- Extended support for Windows Server 2016 ends on January 12, 2027. Mainstream support already ended on January 11, 2022.
- After that date, Microsoft stops releasing security updates for 2016, and support incidents for it close. The servers keep running.
- Microsoft sells ESU for Server 2016 through Azure Arc, billed monthly per core, for up to three years, through 2030. Use it to buy time for the servers that can't move by January.
- Server 2016 can upgrade in place to 2019, 2022 or 2025. Failover clusters move one version at a time.
- Pick the target with the calendar in mind: Server 2022 left mainstream support in October 2026, and Server 2025 is supported until November 2034.
- Start with an inventory by role, not by hostname. The role decides the path.
Windows Server 2016 lifecycle dates
Server 2016 follows Microsoft's Fixed Lifecycle Policy: five years of mainstream support, then five years of extended support. The dates below come from the Server 2016 lifecycle page on Microsoft Learn.
| Milestone | Date |
|---|---|
| General availability | October 15, 2016 |
| Mainstream support ended | January 11, 2022 |
| Extended support ends | January 12, 2027 |
| Paid ESU through Azure Arc | Up to three years, through 2030 (Azure Arc docs) |
| Editions covered | Datacenter, Standard, Essentials, MultiPoint Premium |
Microsoft Learn shows the end timestamps in UTC, so you'll see January 13 on some pages and third-party trackers. The last day of coverage is Tuesday, January 12, 2027, which is also the final Patch Tuesday that includes Server 2016. Container base images released with Server 2016 follow the same dates.
Mainstream support ending in 2022 already cut new features and non-security fixes. What's left today is security updates, and that's what January takes away.
Is Windows Server 2016 still supported?
Yes, until January 12, 2027. As of November 2026, Server 2016 is in extended support and still gets security updates every Patch Tuesday through January 2027. After that, only servers enrolled in ESU keep getting them for up to three years, through 2030.
What stops on January 12, 2027
Nothing switches off. Windows Server 2016 doesn't expire, deactivate or refuse to boot after end of support. Three things change.
Security updates stop. The February 2027 Patch Tuesday won't include Server 2016 unless the server is enrolled in ESU. Any vulnerability disclosed after January stays open on unenrolled machines for good, including ones in shared components like SMB, RDP, Print Spooler and the TCP/IP stack that newer versions get fixes for.
Microsoft support stops. Without ESU, you can't open a support case for Server 2016 after the date, even with a paid support plan. Microsoft's ESU FAQ says the same held for Server 2012 once its support ended without ESU coverage.
Everyone else starts leaving. Software vendors tie their own support to the OS lifecycle. Backup agents, security tools, database engines and line-of-business apps drop 2016 from their compatibility lists, often quietly, in the release notes of a version you haven't installed yet.
Some of the stack under Server 2016 is already gone. SQL Server 2016 left extended support on July 14, 2026, and Exchange Server 2016 on October 14, 2025. If either still runs on your 2016 boxes, the OS date is the second deadline, not the first.
Then there's compliance. Cyber insurance questionnaires and frameworks like PCI DSS and CIS Controls expect supported, patched systems. An unsupported server becomes an exception you have to document and defend at every renewal.
Is there ESU for Windows Server 2016?
Yes. Microsoft announced Server 2016 ESU on February 25, 2026, and the program went live through Azure Arc in August 2026. ESU delivers Critical and Important security updates for up to three years after end of support, through 2030. It adds no features or non-security fixes, and as of November 4, 2026, Microsoft's ESU lifecycle FAQ and the Server 2016 lifecycle page don't list it yet.
Delivery runs through Azure Arc. You connect each server with the Azure Connected Machine agent (version 1.62 or later), create a Server 2016 ESU license in the Azure portal and link it to those servers. There are no keys to install, and the patches can come through Azure Update Manager or the patching tool you already use. You can set up licenses now; billing starts January 13, 2027, per Microsoft's Azure Arc ESU guide.
Who qualifies:
- Editions: Standard and Datacenter.
- Licensing: Software Assurance through a volume licensing program (EA, EAS, EES, SCE or Open Value), or servers licensed through SPLA or a Server Subscription, which don't need Software Assurance.
- Left out this time: the Visual Studio dev/test benefit and free disaster recovery coverage from the Server 2012 program don't apply to Server 2016 ESU.
ESU is priced per core and billed monthly. Azure's Arc pricing page says the list price is the same wherever the server runs, Azure included. On November 4, 2026, Azure's retail price list showed $0.007132 per core per hour for Standard and $0.041067 for Datacenter, with a minimum of 8 virtual cores per VM or 16 physical cores per server. That puts an 8-core Standard VM at about $42 a month, roughly $500 a year, and a 16-core Datacenter host, which covers unlimited VMs, at about $480 a month.
Treat ESU as time to finish the move. It runs out in 2030, and each server you upgrade early comes off the bill.
The Server 2012 R2 ESU program ended on October 13, 2026, so any 2012 R2 servers you still run get no more security updates. Move them in the same project as your 2016 fleet.
Migration paths out of server 2016
You have four ways out: an in-place upgrade, a clean install with role migration, a cluster rolling upgrade, or moving the workload somewhere else entirely, such as Azure or a SaaS replacement.
In-place upgrade paths
Microsoft's upgrade path table (updated April 2026) supports in-place upgrades from Server 2016 to 2019, 2022 or 2025 using installation media. Starting with Server 2025, non-clustered servers can jump up to four versions at a time, so 2016 goes straight to 2025. The Windows Update feature-update route to 2025 only covers 2019 and 2022, so 2016 needs the ISO.
The restrictions matter more than the matrix. You can't switch between Server Core and Desktop Experience during an upgrade. You can't change language or downgrade edition, though Standard can move up to Datacenter. NIC Teaming has to be disabled first. Servers that boot from VHD and Storage Server editions can't upgrade in place. Each target version also needs its own license; Windows Server upgrades aren't free the way client upgrades were.
In-place upgrades suit servers where the role supports it, the hardware is still under warranty, and rebuilding would cost more than the risk. Take a backup and a snapshot first, and test the same build on a clone if you can.
Clusters, clean installs and Azure
Failover clusters are the exception to the four-version jump. A Cluster OS Rolling Upgrade moves one version at a time, so a 2016 Hyper-V or Scale-Out File Server cluster takes three passes to reach 2025. For older hardware that's often the argument for building a new cluster and live-migrating VMs across instead.
A clean install with role migration takes longer but leaves you with a fresh OS, no inherited registry clutter, and hardware you picked on purpose. Storage Migration Service in Windows Admin Center moves file servers, shares and permissions and can take over the old server's identity. We covered where that tool helps and where it stops in our Windows Admin Center guide.
Moving a VM to Azure doesn't extend Server 2016 support by itself, and Azure lists the same Server 2016 ESU price there as on-premises. If the workload is moving to Azure, upgrade the guest OS on the way.
Upgrading in place is where surprises show up. This r/sysadmin post asks what breaks when RD Gateway boxes go from 2016 to 2022:
Which version to target
The target version decides when you do this again.
- Server 2019: extended support ends January 9, 2029. That's two years of runway. Only pick it when an application vendor certifies nothing newer.
- Server 2022: mainstream support ended October 13, 2026, so it arrives already in extended support. Security updates run to October 14, 2031.
- Server 2025: mainstream support runs to November 13, 2029 and extended support to November 14, 2034.
For a fleet leaving 2016 in the next three months, 2025 is the default. Use 2022 where an application is certified for it and not yet for 2025.
This walkthrough shows a Server 2016 to 2025 in-place upgrade from installation media:
Inventory your server 2016 machines first
You can't plan a migration from a hostname list. You need four facts per server: the roles it runs, the application and its owner, the hardware and its warranty, and how it's licensed.
Start with Active Directory. Server 2016 reports build 14393:
powershellGet-ADComputer -Filter 'OperatingSystem -like "*Server 2016*"' ` -Properties OperatingSystem, OperatingSystemVersion, LastLogonDate, IPv4Address | Select-Object Name, OperatingSystem, OperatingSystemVersion, LastLogonDate, IPv4Address | Sort-Object LastLogonDate -Descending
AD only knows about domain-joined machines. Workgroup servers, appliances and VMs in a hoster's tenant won't show up, so cross-check against your hypervisor inventory and your RMM.
Then run a role check on each server:
powershell$os = Get-CimInstance Win32_OperatingSystem Get-WindowsFeature | Where-Object Installed | Select-Object @{n='Server';e={$env:COMPUTERNAME}}, @{n='Build';e={$os.BuildNumber}}, Name, DisplayName
Add the installed software list, the last reboot time, and whether the box is physical or virtual. In OpenFrame, the open, AI-native infrastructure layer for IT and security, you can run that script across your own fleet or a client's devices and collect the output in one place. OpenFrame costs $1 per device a month with Fae, Mingo and 10M AI tokens included, or $0.80 billed yearly with 25M, and the 14-day free trial needs no card. Flamingo builds OpenFrame, which competes with some of the tools covered here.
For physical servers, note the firmware and warranty date too. An in-place upgrade on hardware that's out of vendor support trades one unsupported layer for another, and a BIOS update is often a prerequisite for a newer OS to install cleanly.
The inventory also shows you what nobody owns. The server labelled "APP01" with no documentation tends to be the one tied to a vendor that stopped answering email. Find those early, because they take the longest.
Licensing checks before you upgrade
Licensing is where upgrade budgets go wrong, because the OS license is only one line.
Server licenses. Each Windows Server version needs its own license. If the server is covered by Software Assurance or a subscription, the new version is usually included in that agreement; OEM licenses that shipped with the hardware don't carry forward. Windows Server is licensed per core, with a minimum of 8 cores per processor and 16 per server.
Edition and virtualization rights. Standard covers two VMs per fully licensed host, and Datacenter covers unlimited VMs on the host. A 2016 Hyper-V host with a growing VM count is a good moment to recheck which edition the new host needs.
Client access licenses. Users and devices connecting to a 2025 server need CALs at the 2025 level or newer. The same applies to RDS CALs for session hosts. Existing 2016 CALs don't cover a newer server.
Activation. If you run a KMS host, it needs a key for the new version before it can activate Server 2025 machines. Update the KMS host before the first upgrade, or new servers will sit in the grace period.
Line these up per server in the inventory, next to the role and hardware. A server that's cheap to upgrade technically can still be expensive to license, and that changes which path is cheaper.
Decision table by workload
The role decides the path. This is the default we'd start from, then adjust for hardware and vendor constraints.
| Workload on Server 2016 | Default path | Watch for |
|---|---|---|
| Domain controller | Build a new 2025 DC, move FSMO roles, demote the old one | Raise functional levels only after every DC is upgraded; update DNS and DHCP pointers |
| File server | Storage Migration Service to a new server, or in-place upgrade | Share permissions, DFS namespaces, mapped drives in scripts |
| Hyper-V host or cluster | New cluster on 2025 with live migration, or rolling upgrade one version per pass | Guest OS versions, cluster functional level, backup agent support |
| RDS, RD Gateway, RD Web | In-place upgrade after a clone test, or a fresh deployment | RDS CALs must match or exceed the new version; certificates and gateway policies |
| SQL Server 2016 on 2016 | Move to a new server with a supported SQL version | SQL Server 2016 has been out of extended support since July 2026 |
| Exchange Server 2016 | Move mailboxes to Exchange Server SE or Microsoft 365 | Exchange 2016 support ended October 2025; don't upgrade the OS under it |
| Line-of-business app | Ask the vendor for a certified version, then rebuild | Unsupported vendor combos, license keys tied to hardware |
| Print server | Migrate queues to a new server or cloud print | Driver packages and Point and Print settings |
| WSUS server | Rebuild on 2025 for now, then plan the move off WSUS | WSUS is no longer actively developed; Server 2016 needs the CVE-2025-59287 fix (KB5070882 or later) until it's retired |
| App nobody can migrate yet | ESU through Azure Arc, plus isolation: dedicated VLAN, no internet, tight firewall rules, extra logging | Document the exception with a retirement date before ESU ends in 2030 |
ESU and isolation buy time for the server that can't move by January. Give it an owner and a retirement date.
A timeline from now to January 2027
If you're starting in November 2026, you have about ten weeks. Here's a schedule that fits.
Early November: inventory and triage. Run the AD query and the role script. Tag each server with a path from the table above, mark the ones that need ESU as a bridge, and flag anything with no owner.
Mid-November: set up ESU where you need it. Connect those servers to Azure Arc and create the ESU licenses. Billing starts January 13, 2027, so early setup leaves time to fix agent and licensing problems before the first bill.
Mid-November to early December: pilot and easy wins. Upgrade or rebuild the low-risk servers first: file servers, print servers, standalone utility boxes. Use them to test your backup, rollback and licensing steps.
December: the hard ones. Domain controllers, Hyper-V clusters, RDS and vendor applications. Book vendor time now; December calendars fill fast.
Mid-December to January 12: freeze and stragglers. Leave change windows for rollbacks and for the last two Patch Tuesday releases, December 8 and January 12. Put anything that can't move on ESU or isolate it, and write down its retirement date.
After January 12: prove it. Re-run the inventory query. The count of Server 2016 machines should be zero, or equal to your list of servers on ESU and documented, isolated exceptions.
The short version
Windows Server 2016 extended support ends on January 12, 2027, and paid ESU through Azure Arc can cover servers that need more time for up to three years, through 2030. The servers keep running, but without ESU, security updates and Microsoft support stop, and vendors follow. Inventory by role, pick a path per workload, and target Server 2025 unless an application pins you to 2022. Upgrade clusters one version at a time, rebuild domain controllers rather than upgrading them in place, and put ESU and isolation around whatever can't move, with a named owner and a date.

Conrad Lunderstedt
Solution Architect
I'm Conrad, Solution Architect at Flamingo. I've spent about 26 years in IT, roughly half of it inside MSPs and the rest in enterprise environments, so I've watched vendor decisions get made on both sides of that line. Now I spend my days talking with MSPs about the stack they already run, and helping them work through the requests and issues that come with it.
Related Content
Frequently Asked Questions
/blog/windows-server-2016-end-of-life
Still deciding?
Ask Mingo answers from our docs and customer stories.