OPSWORQ

Guide

Windows Server 2016 ends 12 January 2027: the four ways out

By OpsWorq engineeringReviewed November 20266 min read

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

RouteSuitsWatch for
A new serverApplications that must run on site, and offices with slow internetHardware lead times, and planning the migration properly
Microsoft 365File shares and sign-in, moved to SharePoint, OneDrive and Entra IDFolder permissions and very large files
AzureApplications that need a server but not one in the buildingMonthly running costs and the internet connection
Extended Security UpdatesBuying time for a server that can’t move yetA 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.

  1. This week: list what runs on the server and who depends on it.
  2. 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.
  3. December: build and test, with a restore point first.
  4. 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).

Get started

Questions this guide didn’t answer?

1‑855‑OPSWORQ

855‑677‑9677 · Mon–Fri, 8am–5pm ET

If the business has stopped, call. Don’t use the form.

Ask the engineers who wrote it. A person replies within one business day.

What’s it about? Select all that apply.

A sentence is plenty.

A person replies within one business day. Nothing is sold, and you’re not added to a mailing list.

Prefer to talk? Pick a time for a 20‑minute call (opens in a new tab) Or call 1‑855‑OPSWORQ.

Call Talk to an engineer