// TL;DR

Microsoft stops supporting Windows Server 2016 after January 12, 2027. Your server keeps running, but it stops getting security updates. If you're still on 2016, you have about two months, so start planning now.

  • Last day of support: January 12, 2027
  • Mainstream support ended: January 2022
  • Microsoft 365 Apps on 2016: unsupported since October 14, 2025
  • Best on-premises upgrade: Windows Server 2025
  • Typical move: 2–4 weeks per server

The quick answer

Windows Server 2016 reaches the end of extended support on January 12, 2027. After that, Microsoft releases no more security updates or fixes for it, and offers no support. The server will still boot and run your software. It just stops being protected.

For most small businesses, the right move is one of three: upgrade to a current version of Windows Server, move the server to Microsoft's cloud, or retire it by moving its job to Microsoft 365. Which one fits depends on what the server actually does.

Nothing visibly breaks on January 13. That's what makes it easy to put off, and why it's risky to ignore.

What changes on January 12, 2027

  • No more security updates. Any weakness discovered after that date stays open on your server.
  • No more support from Microsoft. If something goes wrong, there's no fix coming.
  • Your software vendors move on. Backup tools, security software and business applications gradually stop supporting an unsupported operating system.

This applies to the Standard, Datacenter and Essentials editions, which cover nearly every small business server. Many of these servers also run on hardware bought around the same time, so they may be nearing ten years old.

The catch for shared "terminal" servers

Some offices run Word, Excel and Outlook on a shared Windows Server that staff log into remotely. If that server runs 2016, it's already behind: Microsoft ended support for Microsoft 365 Apps on Windows Server 2016 on October 14, 2025.

The apps still receive security fixes on those servers until October 2028, but no new features, and Microsoft recommends moving that setup to Windows 365 or Azure Virtual Desktop. If this describes your office, plan the operating system and the Office setup together.

Why it matters for your business

Security

Attackers look for systems that no longer get patched, because the holes in them never close. A server holding your files, accounts or line-of-business data is exactly what they want.

Cyber insurance

Cyber insurance applications and renewals commonly ask whether you run unsupported operating systems. Answering yes can affect your coverage or premium, and answering inaccurately is worse. If your renewal is coming up, this is worth sorting out first.

Compliance

If you handle health records, payment cards or similar data, running unsupported software is one of the most common findings in an audit or risk assessment.

Not sure what your server runs?

We'll check what's on it, what depends on it and which path fits, then give you a fixed written quote.

Get a quote →

Your options

1. Upgrade to Windows Server 2025

If the server needs to stay in your building, for a specialized application, local hardware or a compliance reason, move to Windows Server 2025. It has mainstream support into 2029. Windows Server 2022 already left mainstream support in October 2026, so 2025 is the better long-term choice. If your hardware is old, plan for a new server too.

2. Move the server to Azure

Microsoft's cloud can run the same server without hardware in your office. It suits businesses with aging hardware, remote staff or growth plans, and it ends the hardware replacement cycle. You pay monthly instead of up front.

3. Retire it with Microsoft 365

Often the server mostly stores shared files or handles email. Those jobs can move to Microsoft 365, with SharePoint and OneDrive for files. Then there's no server to replace at all, which is frequently the cheapest answer for a small office.

I
If the server mostly handles shared files or email...
→ Move it to Microsoft 365
Retire the hardware and skip the next upgrade entirely.
II
If it runs a business application and the hardware is aging...
→ Move it to Azure
Keep the application, lose the hardware, and pay monthly.
III
If it has to stay on-site...
→ Upgrade to Windows Server 2025
Check that your application supports 2025 first, and plan new hardware if yours is near the end of its life.

About extended security updates

For older versions, Microsoft sold Extended Security Updates: paid patches for a few years after support ends. As of this writing, Microsoft's official ESU FAQ lists them for Windows Server 2012 and Windows 10, not Windows Server 2016, though some reports say 2016 coverage is offered through Azure Arc.

If they are offered, expect terms like Server 2012's: on-premises ESUs required Software Assurance or subscription licensing, cost the full license price every year, and covered security fixes only. Confirm the current details before counting on them, and treat them as a short bridge to a migration, never the plan itself.

What it costs

We quote server and cloud moves as fixed-price projects after a free assessment, so the number reflects what you actually run.

ProjectTypical cost
Email or a single system$3,500–$8,000
Full server move$8,000–$12,000+

Hardware and licensing depend on the path and are listed separately in the written quote. Cutover happens after hours or on a weekend, and the old server stays running until the new setup is checked.

A plan for the weeks you have left

A typical server move takes two to four weeks, and the holidays shorten the calendar. Here's the order we'd work in:

// Before January 12
  • List every server and confirm which ones run Windows Server 2016
  • Write down what each one does and which applications depend on it
  • Ask your software vendors which Windows Server versions they support
  • Pick a path for each server: Microsoft 365, Azure or Server 2025
  • Build and test the new setup before touching the old one
  • Move data in checked batches and test with real users
  • Cut over after hours, keep the old server until everything is proven, then retire it

If a move can't finish by January 12, don't panic, but do have a committed date and a plan for the gap. The worst outcome is a rushed cutover, or no plan at all.

We plan and run these moves for offices across Southern Wisconsin, then keep the new setup patched and monitored as part of managed IT for small businesses. While you're taking stock, check the desktops too: any still on Windows 10 are already past Windows 10 end of support.

Frequently asked questions

When does Windows Server 2016 reach end of support?

Extended support for Windows Server 2016 ends January 12, 2027. Microsoft's lifecycle page lists the end as 6:59 AM Pacific on January 13, 2027, so January 12 is the last full day. Mainstream support already ended in January 2022.

Will my Windows Server 2016 server stop working?

No. It keeps booting and running after January 12, 2027. What stops is Microsoft's security updates and support, so every vulnerability found after that date stays open.

Can I buy Extended Security Updates for Windows Server 2016?

Possibly, but check before you plan around it. As of this writing, Microsoft's Extended Security Updates FAQ lists the program for Windows Server 2012 and Windows 10, not Windows Server 2016, though some reports say 2016 coverage is offered through Azure Arc. For Server 2012, on-premises ESUs required Software Assurance or subscription licensing and cost the full license price each year. Treat any ESU as a short bridge to a migration, not a plan.

Should I upgrade to Windows Server 2022 or 2025?

For a new on-premises server, Windows Server 2025. Windows Server 2022 left mainstream support in October 2026, while Windows Server 2025 has mainstream support into 2029, so it gives you the longer runway.

We run Microsoft 365 apps on a shared Server 2016 machine. Is that affected?

Yes. Microsoft ended support for Microsoft 365 Apps on Windows Server 2016 on October 14, 2025. The apps still get security fixes there until October 2028, but no new features, and Microsoft recommends moving to Windows 365 or Azure Virtual Desktop.

How much does it cost to move off Windows Server 2016?

BadgerLayer quotes server and cloud moves as fixed-price projects after a free assessment: typically $3,500 to $8,000 for email or a single system, and $8,000 to $12,000 or more for a full server move. Hardware and licensing depend on the path you choose and are listed in the written quote.

Still on Server 2016?

Free assessment, written plan and a fixed-price quote. We're in Whitewater, Wisconsin and work across Southern Wisconsin.

Get a quote →