Windows Server 2016 support ends January 12, 2027. Your options
Windows Server 2016 stops getting security updates on January 12, 2027. Five realistic ways forward, and how to choose the right one for each server.
Windows Server 2016 reaches the end of extended support on January 12, 2027. After that date Microsoft ships no more security updates for it unless you pay for Extended Security Updates. (Microsoft's announcement) The servers won't stop running, but every new vulnerability stays open, and these machines often run the line-of-business apps that matter most.
First, know what's on them
Before choosing a path, list for each server: what runs on it, who owns it, what it talks to, and how hard it would be to rebuild. Pay attention to the quiet ones: certificate authorities, file shares, scheduled tasks and old IIS sites nobody has touched in years.
Five ways forward
1. Upgrade in place to Windows Server 2022 or 2025. Fastest for simple roles. Take a backup, test the upgrade on a clone first, and check that third-party software supports the new version.
2. Rebuild on a new server and migrate the role. Cleaner than an in-place upgrade and often the right call for domain controllers, certificate services and file servers. It's also a chance to drop years of drift.
3. Move the VM to Azure. Lifting the server into Azure gets it off ageing hardware and can simplify Extended Security Updates; some Azure hosting options include them, so check the current terms for your VM type. Treat it as a bridge, not a destination: the OS still needs upgrading eventually.
4. Modernize the application. If the server only exists to host one .NET application, the real fix may be moving the app itself: from .NET Framework to modern .NET, and from a Windows service to a container or a Linux host. It takes longer, but it ends the cycle of OS deadlines for that workload.
5. Pay for Extended Security Updates. Up to three more years of critical and important security patches, through 2030, available for on-premises servers through Azure Arc, with billing starting January 13, 2027. Useful for the few systems that genuinely can't move in time, as long as each one has a dated exit plan.
How to choose
- Low complexity, supported software: upgrade in place.
- Infrastructure roles: rebuild and migrate.
- No time before January: Azure or ESUs as a bridge, with a plan.
- A single custom app on its own server: modernize the app.
Most estates end up using three or four of these at once. The point is to decide per server, deliberately, rather than discovering in February which machines were forgotten.
Our cloud architecture & migration and .NET modernization work covers both sides of this. If you're not sure where to start, the Health Check maps it in two weeks.
Dealing with this in your own system? We do this work for a living. The first call is free.
Book a call