Windows Server 2016 EOL: The January 2027 Migration Dataset

The January 2027 Deadline: What Actually Stops

Windows Server 2016 reaches the end of its extended support period on 12 January 2027. From that date, Microsoft ceases free security updates, bug fixes and technical assistance for the OS — the same cliff-edge every prior Windows Server version has faced, but this time landing squarely inside most UK organisations' 2026/27 budget cycle.

Microsoft's Extended Security Updates (ESU) programme offers a paid bridge for up to three years beyond that date, but it is deliberately limited: ESUs cover critical and important security fixes only. They do not include new features, non-security updates, or complimentary support — meaning any non-security bug, performance issue or compatibility problem discovered after January 2027 is the customer's problem to solve, ESU or not. Full server end of life information is worth reviewing alongside this deadline, since hardware and OS lifecycles rarely align neatly.

The Installed Base: Who Is Still Exposed in 2026

Data from 6sense identifies 391 UK companies still using Windows Server 2016 in 2026 — a concrete, named installed base rather than a rounded estimate, and a useful anchor for anyone assuming this is someone else's problem.

Separately, Air IT's monitoring data from May 2026 found that roughly one in five servers (around 20%) within monitored environments were still running Windows Server 2016 — a proportion of active server estates, not a count of organisations, and a sign that even IT-managed environments haven't fully cleared the OS.

Set against that, 6sense also puts Windows Server 2016's share of the broader server-and-desktop OS market at just 0.50% in 2026. That headline percentage looks negligible in isolation, but it sits alongside the 391-company and one-in-five-server figures above — three distinct scopes that together show a footprint that is small in market-share terms but still operationally significant for the organisations carrying it.

UK Risk Exposure: Downtime, Cyber Threat and Compliance

SI ICT puts the average cost of downtime for UK businesses at £1,800 per minute. That figure isn't specific to Windows Server 2016 failures, but it frames exactly what's at stake if an unsupported, unpatched server suffers an outage or forced emergency migration after January 2027 rather than a planned one.

UK SMEs already face an 85% phishing success rate and an average ransomware recovery cost of £25,000 — and running an unsupported OS with no further security patching only widens that attack surface at the exact point vendors stop closing new vulnerabilities.

On compliance, UK GDPR and the Data Protection Act 2018 require organisations to maintain appropriate technical and organisational security measures, and NCSC guidance consistently recommends supported, patched software baselines. For regulated sectors — finance, healthcare, public sector — continuing to run Windows Server 2016 past its support cliff is the kind of finding an auditor or regulator will flag first, regardless of whether an actual breach has occurred.

The ESU Bridge: Exact Pricing and Licensing Mechanics

Standard ESU pricing for Windows Server 2016 starts at $61 USD per device in year one, then doubles to $122 in year two and $244 in year three — a pricing curve designed to push customers toward migration rather than indefinite renewal.

A discounted rate of $45 USD per device is available in year one specifically for devices managed through Microsoft Intune or Windows Autopatch — worth checking if your estate already sits inside that management tooling.

Licensing runs per core, with a minimum purchase requirement of 16 cores per server; a separate percentage-based model also exists, priced at 75% of original licence value in year one, rising to 100% in year two and 125% in year three. These are two distinct purchasing mechanics, not the same figure expressed differently, and the better fit depends on your existing licence estate.

Crucially, ESUs are free for workloads running on qualifying Azure destinations — Azure Virtual Machines, Azure Dedicated Host, Azure VMware Solution and the Azure Stack portfolio — while on-premises servers connected via Azure Arc can enrol centrally at a reduced rate. For teams unwilling to pay Microsoft's escalating on-prem fees, third-party maintenance solutions are also worth evaluating as a way to buy planning time without the annual doubling.

• •Standard ESU: $61 (Y1) → $122 (Y2) → $244 (Y3) per device
• •Discounted ESU: $45 (Y1) for Intune/Autopatch-managed devices
• •Per-core licensing: 16-core minimum per server
• •Percentage model: 75% / 100% / 125% of licence value across three years
• •Azure-hosted workloads: ESU included free of charge

Choosing Your Exit Route: Upgrade, Migrate, ESU or Decommission

Microsoft's recommended upgrade paths from Windows Server 2016 are Windows Server 2022 and Windows Server 2025. A direct in-place upgrade from 2016 straight to 2025 is technically feasible in many environments, but migrating to new infrastructure — physical or cloud — is generally the more resilient route, since it avoids carrying forward years of configuration drift and ageing hardware into a fresh OS. For a fuller walkthrough, see our strategies for migrating EOL Windows servers.

Timing matters here: Windows Server 2022's mainstream support already ends on 13 October 2026 — a few months from now — though its extended support continues to 14 October 2031, giving roughly five further years of security-only coverage. Anyone targeting Windows Server 2022 should plan from day one as though they're entering an extended-support-only product.

Windows Server 2019 extended support, by comparison, ends on 9 January 2029 — a shorter runway than either 2022 or 2025, and one reason it isn't generally treated as a fresh migration target for organisations moving off 2016 now.

Hardware Timing: The Cost of Waiting

Server DRAM pricing has already risen more than fivefold since Q3 2025 and is projected to keep climbing into 2027. For any migration that involves new physical hardware rather than a pure cloud shift, that trend turns delay into a direct cost multiplier — the longer a hardware refresh is pushed back, the more expensive the same specification becomes.

This is exactly where cost-effective refurbished servers earn a serious look for budget-constrained migrations: they let teams secure capacity ahead of further DRAM inflation while capital is directed toward the software and services side of the transition instead.

Step-by-Step: Building Your 2026 Migration Runway

Start with discovery: identify every Windows Server 2016 instance across the estate and map its role — domain controller, file server, application server or database server — since each carries a different risk profile, dependency chain and acceptable downtime window. Domain controllers and application servers with tightly coupled line-of-business software typically need the longest lead time; file servers are often the fastest to move, particularly where cloud storage or Azure-hosted alternatives are viable.

From there, a phased runway works best: a discovery and audit phase, a planning and budget-approval phase, a pilot migration on the lowest-risk workload, a full wave-based migration, and a validation and cutover phase before decommissioning the legacy hosts. Building this against the January 2027 deadline — rather than starting the clock only once ESU becomes unavoidable — is what separates a controlled transition from a last-minute scramble.

• •Discovery & audit: inventory every instance and its dependencies
• •Planning & budget: confirm ESU vs. upgrade vs. cloud route and sign-off
• •Pilot migration: prove the path on one low-risk workload first
• •Full migration: move remaining workloads in managed waves
• •Validation & cutover: confirm functionality before decommissioning legacy hosts

Sources

Every figure in this article traces to the sources below.

• •Microsoft — Windows Server 2016 extended support end date
• •Sourcepass — what ends when extended support stops
• •OSnews — ESU three-year window
• •Choice Solutions — what ESU excludes
• •PCWorld — standard ESU pricing tiers
• •Microsoft Community Hub — discounted Intune/Autopatch ESU rate
• •Progressive Robot — per-core licensing and Azure Arc terms
• •Microsoft — free ESU for qualifying Azure destinations
• •Lily Comms — recommended upgrade paths
• •Zinstall — in-place upgrade feasibility