Windows Server 2016 end of life: January 12, 2027 date, ESU and upgrades
Windows Server 2016 support ends January 12, 2027. The exact date, how ESU works through 2030 with Azure Arc, and supported upgrade paths.
Windows Server 2016 reaches the end of extended support on January 12, 2027. Microsoft's lifecycle page encodes the exact cut-off as 6:59:59 AM on January 13, 2027, which is the end of the January 12 support day in Redmond. After that, servers running 2016 stop receiving free security updates unless they are enrolled in Extended Security Updates (ESU) or moved to a newer release.
This page covers the dates, what ESU for Windows Server 2016 is as of October 2026, how it is delivered, and the upgrade paths that Microsoft documents.
Windows Server 2016 end of life date
According to the Microsoft lifecycle entry for Windows Server 2016, the product follows the Fixed Lifecycle Policy:
- Release: October 2016.
- Mainstream support ended: January 11, 2022 (the lifecycle table shows 6:59:59 AM on January 12, 2022).
- Extended support ends: January 12, 2027 (the lifecycle table shows 6:59:59 AM on January 13, 2027).
The entry covers the Datacenter, Standard, Essentials and MultiPoint Premium editions. The page notes that containers released with Windows Server 2016 follow the same dates.
Extended support already means security fixes only: no new features and no design changes. The change in January 2027 is that the fixes themselves stop for anyone without ESU.
What Windows Server 2016 ESU includes
Extended Security Updates are Microsoft's last-resort option for products past end of support. For Windows Server 2016, Microsoft's Azure Arc documentation says ESU delivers Critical and Important security updates for up to three years, through 2030. It does not include new features, customer-requested non-security hotfixes or design change requests.
Microsoft's general ESU overview describes the same limits for the previous generation (Windows Server 2012 and 2012 R2, whose three-year ESU window ended on October 13, 2026). It shows how the program ends: there is a fixed final update, and no ESU after it.
The Azure Arc page lists Standard and Datacenter editions as supported for Arc-enabled ESU. If you run Essentials or MultiPoint Premium, confirm your options with your Microsoft contact or reseller before you plan around Arc.
How to get ESU: Azure Arc, volume licensing or Azure
Microsoft's Windows Server ESU page describes three routes, as of late October 2026.
Azure Arc-enabled ESU (pay as you go)
You install the Azure Connected Machine agent on each server (version 1.62 or higher for Windows Server 2016), then enroll it in the Azure portal or with Azure Policy. Per Microsoft's documentation:
- Windows Server 2016 ESU can be configured in the Azure portal since August 3, 2026.
- Billing for Arc-enabled ESU starts on January 13, 2027.
- Delivery is keyless, so there is no product key to acquire or activate.
- Billing goes through Azure, including drawdown of an Azure Consumption Commitment, with a monthly subscription model.
- To buy ESU you need Software Assurance through a volume licensing program such as an Enterprise Agreement, unless the machines are licensed through SPLA or a Server Subscription.
Arc is not for everything. Microsoft says not to use Arc to deliver ESU to virtual machines on Virtual Desktop Infrastructure; those use Multiple Activation Keys instead. Enrolling does not patch anything by itself: it makes the server eligible, and you still deliver updates through Windows Update, WSUS or Azure Update Manager.
Volume licensing ESU
The classic route is a yearly ESU purchase through Volume Licensing, followed by activating a key on each server. Microsoft says annual billing options are available through a Microsoft representative.
Servers running in Azure
Microsoft's ESU page says Windows Server ESU in Azure covers Azure Virtual Machines, Azure Dedicated Host, Azure VMware Solution and the Azure Stack portfolio, for three more years. For Windows Server 2012, Microsoft's overview states that ESU for servers hosted in Azure is free of charge. The Windows Server 2016 page does not spell out the charge, so confirm the 2016 terms with Microsoft before you rely on that.
What does ESU cost?
Microsoft's public pages reviewed for this article do not publish a per-core price for Windows Server 2016 ESU. Pricing depends on the licensing agreement, region and route, so get a quote from your reseller or Microsoft account team and avoid third-party numbers. Azure Hybrid Benefit can reduce the cost, according to Microsoft.
Budget for the full picture. ESU is a stopgap for servers that cannot move yet. It extends patches, not support for new hardware or features, and it ends in 2030.
Upgrading Windows Server 2016 to 2019, 2022 or 2025
Microsoft's upgrade path guide shows the following for in-place upgrades using installation media:
- Windows Server 2016 to 2019: supported.
- Windows Server 2016 to 2022: supported.
- Windows Server 2016 to 2025: supported directly, because Windows Server 2025 supports in-place upgrades of up to four versions at a time (from 2012 R2 and later).
The Windows Update upgrade method is listed only for Windows Server 2019 and 2022 moving to 2025, so a 2016 server needs installation media. Failover clusters can only use the rolling upgrade one version at a time.
Other limits from the same page:
- Each Windows Server upgrade needs its own license for the target version.
- You cannot switch between Server Core and Desktop Experience during an in-place upgrade.
- Language changes are not supported, and servers booting from VHD cannot be upgraded in place.
- Domain controllers have extra conditions; read Microsoft's domain controller upgrade guidance first.
- Disable NIC Teaming before the upgrade and re-enable it afterwards.
- Not every role supports in-place upgrade; check the role and feature matrix.
Where an in-place upgrade is not an option, build a new server on a supported release and migrate the roles and data. Microsoft's ESU overview also lists migrating workloads as-is to Azure virtual machines as an alternative to staying on-premises.
A practical checklist before January 12, 2027
- Inventory. List every server on Windows Server 2016, including VMs, test machines and appliances that embed it. Check the version with winver or PowerShell and record the edition.
- Sort by effort. Separate stateless servers (rebuild), role servers with supported in-place paths, and legacy application servers that need ESU.
- Check dependent software. Look up the vendor support matrix for your applications on 2019, 2022 and 2025, and confirm the lifecycle of any product installed alongside the OS.
- Decide on ESU early. Arc enrollment takes agent deployment and approvals, so start before the date.
- Test the upgrade. Clone a representative server, run the upgrade there and keep a tested backup.
- Keep patching. Until the end date, regular updates continue; see the Patch Tuesday calendar for 2026 and 2027.
Why unsupported servers are a security problem
Once updates stop, every new vulnerability in the operating system stays open on that machine. Attackers routinely target unpatched servers. For context on how quickly known-exploited flaws must be fixed in US federal systems, see our explainer on CISA BOD 26-04 and KEV timelines. Compliance frameworks and cyber insurers often ask for supported operating systems as well.
For a comparable paid extension on the client side, see our guide to Windows 10 ESU year 2. More platform coverage is in Infrastructure, Security and Cloud.
Frequently asked questions
When does Windows Server 2016 support end?
Extended support ends on January 12, 2027. Mainstream support ended in January 2022.
Can I get Extended Security Updates for Windows Server 2016?
Yes. Microsoft states ESU will run for up to three years, through 2030, via Azure Arc pay-as-you-go enrollment, volume licensing, or as part of running in Azure. Arc-enabled ESU billing begins on January 13, 2027.
How much does Windows Server 2016 ESU cost?
Microsoft's public pages do not list a fixed price, and it depends on your agreement and delivery route. Ask your Microsoft reseller or account team for a quote.
Can I upgrade Windows Server 2016 straight to 2025?
Yes, Microsoft lists a supported in-place upgrade from Windows Server 2016 to 2025 using installation media. You still need a license for 2025 and must check that your roles and applications support the upgrade.
What happens to Windows Server 2016 after January 2027 without ESU?
The server keeps running, but it no longer receives security updates. New vulnerabilities remain unpatched, which raises both attack and compliance risk.