Windows Server 2016 Ends January 2027: Plan Your Cloud Migration Now

Windows Server 2016 stops receiving security updates on January 12, 2027. After that date your options are an in-place upgrade to Windows Server 2025, replacement hardware, a move to Azure, or paid Extended Security Updates.

January 12, 2027 falls on a Tuesday. The second Tuesday of the month, which makes it Patch Tuesday, and that is not an accident. Microsoft lines these dates up so the last cumulative update a product ever receives arrives on schedule with everything else that month. Your server will patch that morning exactly like it always does. Then it never patches again.

That is the whole event. No alarm goes off. Nothing stops working. The license does not expire, the box does not shut down, and Monday looks identical to Friday, which is precisely why this date gets ignored until something outside the building forces the conversation. An insurance questionnaire, usually. Sometimes a client’s vendor review.

If you are running a server that was specced and built somewhere between 2016 and 2019, this is your deadline. The useful part of this is not the warning. It is working out which of four paths you are on, because a cloud migration is one of them. Not automatically the right one.

What Stops on January 12

End of support means Microsoft stops issuing security updates, hotfixes, and patches for Windows Server 2016. The operating system keeps running normally. What ends is the supply of fixes for vulnerabilities discovered after that date, along with coordinated vulnerability disclosure for the platform.

Nothing visibly changes. Mainstream support ended on January 11, 2022 and almost nobody noticed, because extended support carried the security updates for another five years, and security updates are the only part most businesses were consuming by then. January 2027 closes the extended window too. There is nothing behind it.

Here is the part that gets underweighted in every one of these conversations. Vulnerabilities do not stop being found in code because Microsoft stopped shipping fixes for one version of it. A flaw discovered in 2028 that touches the Windows kernel gets patched on Server 2019, 2022, and 2025, and the notes describing what it fixed are published openly, and comparing a patched binary against an unpatched one to work out precisely what changed is routine work rather than exotic research. Your 2016 box is the unpatched side of that comparison. Permanently.

One more thing worth checking while you are in there. If that same server also runs SQL Server 2016, that deadline already went by. Extended support for SQL Server 2016 ended on July 14, 2026. Two products. Same release year, same server, different dates. It catches people out constantly.

The Extended Security Updates Door Most Small Businesses Cannot Open

Microsoft does sell more time. Extended Security Updates cover Windows Server 2016 for up to three years past the deadline, delivered through Azure Arc and billed monthly against a core count you provision yourself.

Read the licensing requirement first.

Microsoft’s own provisioning guidance is blunt about the gate. In all cases you must attest to conformance with Software Assurance or an equivalent Server Subscription, and for this product the Services Provider License Agreement route that covered Windows Server 2012 is not available at all. Purchases run through an Enterprise Agreement, an Enterprise Subscription Agreement, a Server and Cloud Enrollment, or an education enrollment.

Now count how many businesses with 5 to 60 employees hold an Enterprise Agreement.

Not many.

Most of the servers we get called about across Rockland, Westchester, and Bergen arrived with an OEM Windows Server license bundled into a Dell or HP purchase order, and Software Assurance was never part of that transaction because nobody selling the hardware had a reason to raise it. Go find the paperwork. Do that first, before you assume anything, because that single line decides whether Extended Security Updates are on your menu or whether the January date is genuinely fixed for you.

There is a core minimum underneath it too. Physical core licensing requires at least 16 cores per machine and virtual core licensing requires 8 per virtual machine, so a modest 8-core server still bills as 16. Round up, always.

Four Paths, and How to Tell Which One Is Yours

Three of those four end with you off Windows Server 2016 for good. The fourth buys three years and hands you the identical decision in 2030. None of that argues against it. It argues for knowing which one you chose. And why.

The In-Place Upgrade Got Easier, Quietly

Windows Server used to cap in-place upgrades at two versions. Under that rule a 2016 server could reach 2022 and stop, and getting to the current release meant running the whole process twice.

That changed. Microsoft’s upgrade matrix now lets nonclustered systems jump up to four versions at once, and Windows Server 2016 to Windows Server 2025 is a supported single hop using installation media.

Conditions attach. They are the sort that surface at eleven on a Saturday night if nobody read them first.

• Windows Update will not do this one. The feature-update path to 2025 only opens from 2019 and 2022, so a 2016 server needs the ISO.
• Failover clusters still move one version per rolling upgrade. The four-version jump is for standalone servers.
• Every Windows Server version is a separate purchase. Unlike Windows client, the upgrade does not come with the old license.
• NIC Teaming has to be disabled before you start and re-enabled after.
• No switching between Server Core and Desktop Experience mid-upgrade, and a domain controller cannot be converted to a retail version.

Not every role supports an in-place upgrade in the first place. Check the matrix. Discovering it mid-reboot is the expensive way to learn it.

Hardware age is its own separate argument. Running an in-place upgrade onto a server with an out-of-warranty RAID controller and drives well past their duty cycle is a technically supported move that I would still talk you out of. The upgrade will probably work. The disk is the risk. That drive has been spinning since 2018.

Working Backwards From January

Four months sounds generous. Then you break it into the pieces that actually consume calendar and it stops sounding that way.

The long pole is almost never the server. It is the software. Nearly every business has one line-of-business application that pins the entire environment in place, and the vendor’s answer about which Windows Server versions they support today is the fact everything else hangs off. Get it in writing. A support rep saying it should be fine is not a supported-configuration statement, and the gap between those two things becomes very important in week two when something misbehaves and you need that vendor to actually help you.

Then procurement. That assumes you are buying. Then a maintenance window nobody wants to hand you in December.

Construction firms and manufacturers tend to get the hardest version of this. The estimating or ERP package sitting on that server is often a release or two behind on its own cycle, which means the upgrade path runs through the software vendor before it ever reaches Microsoft.

What to Do in the Next 30 Days

None of this commits you to anything. It replaces guessing with knowing.

• Write down every role and application on the box. File shares, print, Active Directory, DNS, DHCP, the database, and the thing nobody remembers installing.
• Find the license paperwork and look specifically for Software Assurance or a Server Subscription.
• Email each software vendor and ask which Windows Server versions they support now, and which they intend to support in 2027.
• Check the hardware. Purchase date, warranty status, drive age.
• Decide per workload rather than per server.

That last one carries most of the value. The reflex is to treat the server as a single object that either moves or does not, and it almost never is one. Files can go to SharePoint. Identity goes to Entra ID. The stubborn application can sit on a small Azure virtual machine or a much smaller replacement box, and the full-size server refresh you were bracing for stops being necessary at all.

We went through that split in more depth when comparing a file server against SharePoint and OneDrive, and the mail half of the move is covered in what to expect from a Microsoft 365 migration. The licensing that sits under all of it lives in Microsoft 365 and cloud services. However it lands, the backup design changes underneath it, which makes backup and disaster recovery a separate conversation rather than an afterthought.

Straight Answers Before You Budget for This