Windows Server 2016 extended support ends on 12 January 2027. After that date it gets no security updates unless you pay for Extended Security Updates, for up to three years. There are four routes: a new server, Microsoft 365, Azure, or buying time with ESU, and the decision needs making before December.
What ends
Microsoft’s extended support for Windows Server 2016 ends on 12 January 2027. After that, the server receives no security updates unless you buy Extended Security Updates. It will keep running; it just stops being fixed.
Microsoft confirmed the ESU program in February 2026. It covers security updates rated Critical and Important, for up to three years (to January 2030), bought through Azure Arc or through volume licensing. ESUs are now paid wherever the server runs, including in Azure, and Arc billing starts on 13 January 2027. They include no new features or non-security fixes.
What probably runs on it
In a small business, one 2016 server often does several jobs at once. List them before choosing a route:
- Sign-in and permissions (Active Directory).
- File shares.
- A line-of-business application and its database.
- Printing, and sometimes remote desktop for staff.
The four ways out
| Route | Suits | Watch for |
|---|---|---|
| A new server | Applications that must run on site, and offices with slow internet | Hardware lead times, and planning the migration properly |
| Microsoft 365 | File shares and sign-in, moved to SharePoint, OneDrive and Entra ID | Folder permissions and very large files |
| Azure | Applications that need a server but not one in the building | Monthly running costs and the internet connection |
| Extended Security Updates | Buying time for a server that can’t move yet | A yearly cost for security fixes only. It’s a bridge, not a destination |
Most small businesses end up combining two: files and sign-in to Microsoft 365, and the one application that needs a server to a new one or to Azure.
A timeline that still finishes before the date
From late November there are about seven working weeks left, with the holidays inside them. That is enough for most small offices if the decisions are made now.
- This week: list what runs on the server and who depends on it.
- Before December: choose the route for each job, and order anything with a lead time. If the server can’t move in time, decide on ESU now rather than in January.
- December: build and test, with a restore point first.
- First week of January: cut over in a quiet window, well before the 12th.
Source: Microsoft Windows Server blog, planning ahead for Windows Server 2016 end of support (opens in a new tab), 25 Feb 2026; Microsoft Learn, Extended Security Updates for Windows Server (opens in a new tab).
Read us first when you search.
GoogleAdd OpsWorq as a preferred source (opens in a new tab)

