Windows Server 2016 End of Support: The MSP Plan for January 12, 2027
Windows Server 2016 reaches end of support on January 12, 2027. After that, no more security updates unless the client pays for Extended Security Updates. That's about two months away, and most of that is holiday change freeze.
Microsoft's Windows Server blog points customers to two paths: upgrade to Windows Server 2025, or move the workload to Azure. Microsoft's Azure Arc ESU guide covers the third path: pay for up to three more years of critical and important security fixes, through 2030, billed from January 13, 2027.
Quick answer: MSPs should inventory every Server 2016 box across clients now, sort each one into upgrade, migrate, retire, or ESU as a bridge, and get client sign-off before the holidays. ESU through Azure Arc needs Software Assurance, a server subscription, or SPLA, has core minimums, and starts billing January 13, 2027, so treat it as a dated bridge with a migration project attached.
Start with the inventory
Pull every machine reporting Windows Server 2016 from the RMM. Then add what the RMM won't tell you: the line-of-business app on it, who at the client owns that app, whether the server is a domain controller, and whether anything else on the network depends on it.
That last column is where projects go sideways. The print server that also runs the badge system. The SQL box a vendor installed in 2017 that nobody has the license key for. Find those now, while there's time to ask questions.
Scope every Server 2016 box in one place
Scopable pulls the client environment into the scope, so each server gets its decision, labor, licensing, and ESU months on one quote the client approves line by line. Start for free and run it on your first client today.
The per-server decision
Every server lands in one of four buckets. Make the call per server, not per client.
| Decision | When it fits | What the client is buying |
|---|---|---|
| Upgrade to Server 2025 | The app vendor supports 2025 and the hardware has life left. | A scoped upgrade project, plus licensing if they don't already own it. |
| Migrate to Azure | The workload is a reasonable fit for cloud and the client is already in Microsoft's ecosystem. | A migration project and a new monthly Azure line. |
| Retire | The role moved to M365 or SaaS years ago and the box is just still on. | A short decommission project with a data check. |
| ESU as a bridge | The app can't move before January 12, or the vendor needs time. | ESU billing from January 13, 2027 plus a migration project with a date. |
ESU with no migration date is how a client ends up running 2016 in 2030. Write the end date into the quote.
The ESU fine print
Microsoft's ESU licensing guide for Azure Arc has a few rules that change the math. The ones that bite MSPs:
- Eligibility: the client needs Software Assurance through volume licensing, or the server licensed through a server subscription or SPLA. A box that shipped with an OEM license and never picked up SA or a subscription doesn't meet that bar, and that describes a lot of SMB servers. Check the license before you promise ESU to anyone.
- Core minimums: at least 16 physical cores per machine, or 8 virtual cores per VM. A small two-core VM still bills as eight.
- Edition and type are locked: you can't convert a license from Standard to Datacenter or physical to virtual later. Datacenter virtual core isn't a valid combination at all.
- No free disaster recovery: DR copies of Server 2016 need their own ESU coverage. The Visual Studio dev/test benefit doesn't apply either.
- Delivery: machines connect through the Azure Connected Machine agent, version 1.62 or higher. VDI machines use Multiple Activation Keys instead of Arc.
- Already covered: Azure VMware Solution and Azure Local VMs get ESUs free and shouldn't enroll through Arc.
Billing is monthly and tied to the cores on the license. When a server moves to 2019 or later, cut the cores or deactivate the license. Microsoft won't do that for you.
How to scope and quote it
This is a project, and it should be quoted like one. The upgrade itself is the easy part. The hours go into the app testing, the vendor calls, the DNS and DHCP moves, the backups you verify before you touch anything, and the rollback plan.
Build the quote from the inventory, one line per server, with the decision bucket, the labor, any licensing, and the ESU months if it's a bridge. A client who sees six servers and six decisions on one page signs faster than one who gets a lump number. The MSP project scoping guide has the hour categories most teams forget.
If you're building that inventory from RMM exports and a spreadsheet, Scopable's assessment and scoping software pulls the client environment into the scope so the server list, the gaps, and the project lines come from the same data. You did a version of this for Windows 10 last year. The Windows 10 end of life playbook is a decent template for the client conversation.
What to send clients this month
Send each client a short note: how many Server 2016 machines they have, the recommended path for each, and the date you need a decision. Put it on the next QBR if one lands before Christmas. If it doesn't, don't wait for it.
Frequently Asked Questions
When does Windows Server 2016 reach end of support?
Windows Server 2016 reaches end of support on January 12, 2027. After that it gets no security updates unless the server is enrolled in Extended Security Updates, which Microsoft delivers through Azure Arc for up to three years, through 2030, with billing starting January 13, 2027.
Who can buy Windows Server 2016 Extended Security Updates?
The server needs Software Assurance through a volume licensing program, or a server subscription or SPLA license. ESU through Azure Arc bills monthly per core with a minimum of 16 physical cores per machine or 8 virtual cores per VM, and disaster recovery copies need their own coverage.
How should an MSP scope Windows Server 2016 end of support work?
Inventory every Server 2016 machine, add the app, the app owner, and any dependencies, then sort each server into upgrade to Server 2025, migrate to Azure, retire, or ESU as a dated bridge. Quote one line per server with the decision, labor, licensing, and ESU months so the client can approve server by server.
