Windows Server 2016 End of Support: What Are Your Options in 2027?

Windows Server 2016 reaches the end of extended support on January 12, 2027, and after that date it receives no security updates unless you enroll it in Extended Security Updates or run it in Azure (Microsoft Learn). Your realistic options are an in-place upgrade, a migration to new hardware, paid Extended Security Updates, a move to the cloud, or retiring the workload. The right answer depends on two things you can check this week: whether each host is supported on a newer Windows Server version, and how the 2016 license was bought.

What happens when Windows Server 2016 reaches end of support?

The server keeps running, but Microsoft stops publishing security updates for it. Microsoft warns that this can cause security or compliance issues and put business applications at risk (Microsoft Learn). Check the database tier too, because SQL Server 2016 extended support already ended on July 14, 2026 (Microsoft).

What are your options before January 12, 2027?

• In-place upgrade: fastest if the host is supported and the roles allow it, but it keeps the old hardware.
• Migrate to a new server: the cleanest result, but exposed to current server prices and lead times.
• Extended Security Updates: a paid bridge for up to three years, for servers that need more time.
• Move to Azure or another cloud: useful when the hardware is failing or the workload is due for change anyway.
• Retire the workload: often possible for old file shares or line-of-business apps nobody still uses.

Can you upgrade Windows Server 2016 directly to 2022 or 2025?

Nonclustered systems can upgrade directly to Windows Server 2025 from Windows Server 2012 R2 or later, and Windows Server 2016 is also within the two-version limit for moving to 2022 (Microsoft Learn). Clusters are stricter: a cluster OS rolling upgrade can move only one version at a time. Microsoft also notes that not every role supports in-place upgrade, and that each Windows Server upgrade needs its own license.

Microsoft lists a suggested MSRP of $1,176 for a 16-core Windows Server 2025 Standard license and $6,771 for Datacenter, plus client access licenses for every user or device (Microsoft). Support dates favor the newer release: Windows Server 2025 extended support runs to November 14, 2034 (Microsoft Lifecycle), while Windows Server 2022 ends on October 14, 2031 (Microsoft Lifecycle).

How do you check whether an existing host can run Server 2022 or 2025?

Work through these checks for each physical host. Meeting Microsoft's minimum does not mean the server vendor supports the combination, and vendor support is what matters when a controller driver fails.

• Minimum CPU features: Microsoft requires a 1.4 GHz 64-bit processor with Second Level Address Translation, SSE4.2 and POPCNT, and suggests Sysinternals Coreinfo to check (Microsoft Learn).
• Windows Server Catalog: Microsoft now points customers to this catalog to identify tested and certified hardware (Microsoft Learn).
• CPU generation: the Windows Server 2025 list published in November 2024 covered second through fifth generation Xeon Scalable (x2xx to x5xx) and EPYC from 7xx2 onward, so first generation x1xx parts were not on it (Tom's Hardware).
• Dell: the PowerEdge R750 page lists Windows Server 2025 LTSC (Dell). For the 14th generation R740 the evidence conflicts: a Dell community support employee said in December 2025 that it does not support Server 2025, while a later post in the thread cites a BIOS note mentioning it (Dell Community). Confirm your model at Dell's OS support site.
• HPE: a reseller's summary of HPE's February 2026 white paper quotes it as saying Gen9 and older servers are not supported on Windows Server 2025, and says Gen10 is certified only with conditions, including second generation Xeons (PCSP). Check HPE's own certification matrix for your exact model.
• Storage and network drivers: confirm your RAID controller and NICs have drivers for the target version before you schedule anything.
• TPM and Secure Boot: Microsoft says TPM and UEFI Secure Boot firmware are needed only for certain features, such as BitLocker (Microsoft Learn). The 2011 Secure Boot certificates began expiring in June 2026 (Microsoft Support), and administrators must start the certificate update manually on in-scope servers (Microsoft).

If a host fails these checks, a CPU swap is rarely the quick fix it looks like. Our guide on upgrading the CPU in an existing server covers what to confirm first.

How much do Windows Server 2016 Extended Security Updates cost?

Through Azure Arc, the published list rate effective August 1, 2026 is $0.007132 per core per hour for Standard and $0.041067 for Datacenter (Azure Retail Prices API). Some guides still say no price exists, but the rate is live in that API. The minimum is 16 physical cores per machine or eight virtual cores per VM (Microsoft Learn). By our arithmetic, at 730 hours a month, a 16-core server costs about $83 a month on Standard and about $480 a month on Datacenter, or roughly $1,000 and $5,756 a year at that rate. One year of Standard ESU is therefore close to the $1,176 suggested price of a new 16-core license, which is why ESU works as a bridge, not a plan.

• Coverage: Critical and Important security updates through January 2030, with no new features or nonsecurity fixes (Microsoft).
• Eligibility: you need Software Assurance through volume licensing, or SPLA or a Server Subscription (Microsoft Learn). A license bought without Software Assurance does not meet that rule, so check before you plan around ESU.
• Timing: enrollment opened on August 3, 2026, billing begins on January 13, 2027, and the Connected Machine agent must be version 1.62 or later (Microsoft Learn).
• Late enrollment: licenses provisioned after end of support carry a one-time back-billing charge for the time elapsed (Microsoft Learn), so waiting does not save money.

Should you move Windows Server 2016 to Azure or another cloud?

Azure is the cheapest way to keep a 2016 workload patched as-is, since Microsoft says ESU is free for VMs in Azure, including Azure VMware Solution and the Azure Stack portfolio (Microsoft Lifecycle FAQ). You pay for the VM instead, so this suits workloads that were moving anyway or hardware that is failing. Other clouds are possible through Arc, where Microsoft says virtual core licensing suits VMs on AWS, GCP or OCI. If you cannot get eligible ESU or new hardware in time, renting capacity for a year can be the better answer than buying at today's prices.

Why is it risky to leave a hardware replacement until now?

On November 6 there are about 67 days left, and that is shorter than many current server lead times. Moor Insights and Strategy's Matt Kimball told Network World in August that companies used to 30 to 45 day lead times are now looking at 6, 12 or even 18 months (Network World). Gartner's Jon Forest said in the same article that some server prices had risen more than 125%. Our guides to server lead times and why server prices went up cover both problems. Treat the deadline as a reason to put a bridge in place now, then order replacements on a realistic schedule.

What should you do this month?

• List every Windows Server 2016 instance, physical or virtual, with its host model, CPU, core count and application owner.
• Pull the license records, and mark which servers have Software Assurance, SPLA or a Server Subscription.
• Sort each server into upgrade, replace, ESU, cloud or retire, using the hardware checks above.
• Test an in-place upgrade on a copy of the workload, and confirm that the application vendor supports the target version.
• Connect ESU candidates to Azure Arc now, so enrollment is ready before January 12.
• Isolate any server left without coverage on a restricted network segment until it is replaced.
• Add the licenses, ESU and replacement servers to your 2027 hardware budget. For hypervisor hosts, see sizing a server for Proxmox, Hyper-V or VMware.

Nexus Compute can help when your review shows hosts that need replacing. We supply new servers through authorized distribution channels with the full manufacturer warranty, check compatibility against your platform before dispatch, and accept purchase orders with net terms for qualified organizations. Send us your host list through our quote form and we will price options, including alternates, within 48 business hours. If ESU or Azure is the better answer for a given server, we will say so.