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, Lansweeper data reported by The Register in March 2026 found that Windows Server 2016 accounted for 20.3% of the servers Lansweeper monitors — 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.

Phishing remains the most prevalent type of breach or attack in the UK government's Cyber Security Breaches Survey 2025/2026, experienced by 38% of businesses — 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

Windows Server 2016 ESUs are not priced per device: Microsoft licenses them per core, and its Azure Arc pricing page lists a per-core monthly rate for Windows Server 2016 ESUs enabled by Azure Arc. The widely quoted $61-per-device year-one price, doubling to $122 and $244, is Microsoft's Windows 10 commercial client ESU pricing — a separate programme — not Windows Server 2016 pricing.

The $45 year-one rate for devices managed through Microsoft Intune or Windows Autopatch is likewise a Windows 10 client ESU discount, not a Windows Server 2016 price.

Windows Server ESUs are licensed per core rather than per device, with a 16-core minimum per physical server (8 cores per virtual machine). No escalating percentage schedule has been published for Windows Server 2016; for the previous Windows Server 2012/R2 programme, Microsoft priced every on-premises ESU year at 100% of the full licence price.

Crucially, Windows Server 2016 falls under the consistent ESU pricing model Microsoft introduced on 1 April 2026, under which customers pay the same list price regardless of deployment location (Azure, on-premises or other public clouds) or purchasing channel — so the free-in-Azure ESU arrangement of earlier programmes should not be assumed. On-premises servers can enrol through Azure Arc, with billing starting on 13 January 2027. For teams unwilling to pay for ESUs, third-party maintenance solutions are also worth evaluating as a way to support the hardware while planning the migration.

• •Windows Server 2016 ESU: licensed per core (per-core monthly rate via Azure Arc), not per device
• •$61/$122/$244 and $45 per-device prices: Windows 10 client ESU, not Windows Server
• •Per-core licensing: 16-core minimum per server
• •Windows Server 2012/R2 precedent: 100% of full licence price in each ESU year
• •From 1 April 2026: same ESU list price in Azure, on-premises or other clouds

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
• •Microsoft Windows IT Pro Blog — Windows 10 client ESU per-device pricing ($61 base; $45 Intune/Autopatch), not Windows Server
• •Microsoft Lifecycle FAQ — ESU per-core minimums and Windows Server 2012/R2 pricing precedent
• •Progressive Robot — per-core licensing and Azure Arc terms
• •Microsoft Azure Arc Blog and Azure Arc pricing — consistent ESU pricing model and per-core Windows Server 2016 ESU rate
• •Lily Comms — recommended upgrade paths
• •Zinstall — in-place upgrade feasibility