Windows Server 2016 end of support is 12 January 2027, when Microsoft's extended support ends and regular security updates stop. Mainstream support already ended on 11 January 2022. After 12 January 2027, the only security updates for Windows Server 2016 come through paid Extended Security Updates, which Microsoft sells for up to three years.
Below: Microsoft's dates, the ESU terms, the Azure question, the upgrade paths, and the inventory that sizes the job.
- Windows Server 2016 extended support ends on 12 January 2027. Mainstream support ended on 11 January 2022.
- Microsoft sells Extended Security Updates for Windows Server 2016 through Azure Arc, for up to three years, through 2030. Billing starts on 13 January 2027.
- Microsoft's no-extra-charge ESU terms for Azure VMs are written for Windows Server 2012 and 2012 R2. We found no Microsoft Learn page that extends them to 2016.
- Windows Server 2016 can upgrade in place to 2019, 2022 or 2025. What breaks is what runs on it: SQL Server, .NET apps, IIS sites, TLS settings and scheduled tasks.
Windows Server 2016 end of support date
Windows Server 2016 follows Microsoft's Fixed Lifecycle Policy: mainstream support, then extended support with security updates.
| Milestone | Date |
|---|---|
| Start date | 15 October 2016 |
| Mainstream support ended | 11 January 2022 |
| Extended support ends | 12 January 2027 |
| ESU setup opens in the Azure portal (Azure Arc) | 3 August 2026 |
| ESU billing begins (Azure Arc) | 13 January 2027 |
| ESU coverage ends | Up to three years, "through 2030"; no exact day on the pages we checked |
Checked 30 October 2026 against Microsoft's lifecycle page for Windows Server 2016 and its Azure Arc ESU preparation page.
Is Windows Server 2016 still supported, and for how long?
Yes, until 12 January 2027. After that, Microsoft's 2027 end-of-support list says there are no new security updates, no non-security updates and no assisted support, paid or otherwise. The servers keep running; what ends is Microsoft's servicing, and the easy answer to an auditor. See the risks of running end-of-life software.
The same list shows what else leaves on 12 January 2027: IIS 10 on Windows Server 2016, .NET Framework 4.6.2, Hyper-V Server 2016 and Windows Server Update Services for Windows Server 2016.
Windows Server 2016 end of support ESU: what you can buy
Microsoft does sell them, whatever older articles say. Its Azure Arc documentation, updated in October 2026, says "Extended Security Updates for Windows Server 2016 provide Critical and Important security updates for up to three years, through 2030." Microsoft's ESU FAQ still leaves 2016 out of its availability table, which is where the "no 2016 program" claim comes from.
| ESU term | What Microsoft's Azure Arc pages say |
|---|---|
| What's covered | Critical and Important security updates only. No new features or nonsecurity hotfixes |
| Editions | Standard and Datacenter |
| How you buy | Connect each server to Azure Arc (agent 1.62 or later), create an ESU license in the Azure portal, link it to servers |
| Who qualifies | Software Assurance through a volume licensing program, or servers licensed through SPLA or a server subscription |
| Minimums | 16 physical cores per machine, or 8 virtual cores per VM |
| Dev/test and disaster recovery | The no-cost benefits offered for 2012 don't apply to 2016 |
Licensing rows from Microsoft's Azure Arc ESU licensing page. For servers that can't connect to Azure, ask your Microsoft account team. The ESU FAQ calls the program "a last resort paid option" and "a temporary bridge."
Windows Server 2016 end of support on Azure: what Microsoft doesn't say
Don't assume that moving Windows Server 2016 to an Azure VM brings ESUs at no extra cost. That was the rule for 2012 and 2012 R2: Microsoft's Windows Server ESU overview says "There's no extra charge for Extended Security Updates on top of an Azure VM's cost," but that page is titled for 2012 and 2012 R2 and its table lists only those.
The 2016 sections of the Azure Arc pages don't repeat it. The 2012 guidance says servers stop needing ESUs once moved to Azure; the 2016 guidance says only once "updated to Windows Server 2019 or higher." Microsoft has dropped the Azure benefit once already: its SQL Server ESU page says that starting with SQL Server 2016, moving to Azure VMs no longer gives ESUs at no charge. Get Microsoft's answer in writing before a migration plan depends on it.
Windows Server 2016 in-place upgrade: which versions?
Windows Server 2016 can upgrade in place to 2019, 2022 or 2025 from installation media. Microsoft's upgrade paths page says nonclustered systems can jump up to four versions to Windows Server 2025. The Windows Update route to 2025 starts only from 2019 or 2022.
| Target | In place from 2016? | Mainstream support | Extended support ends |
|---|---|---|---|
| Windows Server 2019 | Yes, from media | Ended 9 January 2024 | 9 January 2029 |
| Windows Server 2022 | Yes, from media | Ended 13 October 2026 | 14 October 2031 |
| Windows Server 2025 | Yes, from media | See its lifecycle page | See its lifecycle page |
Checked 30 October 2026 against Microsoft's lifecycle pages for Windows Server 2019, 2022 and 2025.
Windows Server 2019 buys a little over two years; 2022 is already in extended support, to 2031.
The upgrade paths page lists the limits: no change of language, no switch between Server Core and Desktop Experience, and "Not all roles support in-place upgrade." An in-place upgrade also keeps "your settings, server roles, features, and data," including changes nobody wrote down. Moving the server elsewhere as it stands is a lift and shift; see lift and shift vs refactor.
Inventory before you upgrade: the OS is the easy part
What sizes the job is everything installed on top of the operating system.
| What runs on the server | What to check | What Microsoft documents |
|---|---|---|
| SQL Server 2016 | Every instance and what connects to it | Reached end of support on 14 July 2026 (2026 list) |
| .NET Framework applications | Each app's target framework, any .NET 3.5 apps, config files | 4.6.2 ends on 12 January 2027; 4.8 "follows the Lifecycle Policy of the parent OS" (.NET Framework FAQ) |
| IIS sites and classic ASP | Sites, app pools, bindings, certificates, handlers, run-as accounts | IIS "is a component of the Windows operating system and follows the same lifecycle" (IIS lifecycle page) |
| TLS settings | Registry changes, and what partners and old clients can negotiate | Windows Server 2016 supports TLS up to 1.2; TLS 1.3 starts with Windows Server 2022 (Schannel page) |
| Scheduled tasks and Windows services | What each one runs, under which account, and who owns it | Nothing. This part is yours |
| Server roles and features | Every installed role | Check Microsoft's role migration matrix first |
A server running since 2016 can hold a nightly task that copies a file to a partner's SFTP site, or an app pool running under a departed admin's account (examples illustrative): the legacy system examples that surface only when something fails. For the applications, see .NET Framework 4.8 end of support, classic ASP end of life and SQL Server 2016 end of support.
Before the upgrade weekend: where the 30-day assessment fits
Microsoft's tools check the operating system. The 30-day assessment checks what runs on it. It's fixed in scope, at a price agreed before we start. Over 30 days we read the code and configuration on your Windows Server 2016 machines and the architecture around them, and map what depends on what. We find the hidden architectural debt and flag the security and compliance gaps, starting with whatever loses Microsoft patches on 12 January 2027.
The report says in plain language what is broken, what each path (upgrade, rebuild, ESUs or migration) would break, and what it would take to fix it. Your own team can act on it, or we can do the work as a separate project with its own scope and price. The report stands on its own either way. If one server and one application are all that need checking, we'll say so.
Book a scoping call and bring a rough count of your Windows Server 2016 machines and what runs on each.