Windows Server 2016 end of support (12 Jan 2027): the migration playbook

Summary. Windows Server 2016 reaches the end of extended support on 12 January 2027, the same day as Hyper-V Server 2016, IIS 10 on Windows Server 2016, WSUS for Windows Server 2016, Windows Storage Server 2016 and .NET Framework 4.6.2. System Center 2016 ends a day earlier, on 11 January. After that, security fixes cost money. Microsoft announced Extended Security Updates (ESUs) for Windows Server 2016 on 25 February 2026 and made the Azure Arc version generally available on 6 August 2026. Microsoft's retail price list shows $0.007132 per core per hour for Standard and $0.041067 for Datacenter, about $5.21 and $29.98 per core a month, with minimums of 16 physical cores per machine or 8 virtual cores per VM, billed from 13 January 2027 for up to three years. Under Microsoft's rule for ESU offerings released from 1 April 2026, the list price is the same in Azure as on-premises, so moving to Azure no longer buys free patches. Windows Server 2016 upgrades in place straight to 2019, 2022 or 2025; pick 2025, the only one of the three still in mainstream support. On 1 November 2026, 72 days remain. Treat ESUs as a bridge for stragglers, not a plan.

About this article. This playbook is for IT managers and infrastructure teams who still run Windows Server 2016. Dates, prices and licensing terms were checked on 1 November 2026 against Microsoft lifecycle pages, Microsoft Learn documentation for Azure Arc, Active Directory and Windows Server, Microsoft licensing and pricing pages, Microsoft blog announcements and the Azure Retail Prices API. It is general information, not licensing advice: Microsoft changes terms often, so confirm with your licensing partner before you commit, and no vendor paid for inclusion. Researched with AI assistance and reviewed by our editorial team.

What stops on 12 January 2027

This is the execution guide. For where workloads should land, read our costed comparison of Windows Server 2025, Azure and Azure Local.

Windows Server 2016 (Datacenter, Essentials, MultiPoint Premium and Standard) follows the Fixed Lifecycle Policy. Mainstream support ended on 11 January 2022 and extended support ends on 12 January 2027, Pacific time. Containers released with Windows Server 2016 follow the same dates. After end of support Microsoft provides no security updates, no non-security updates, no free or paid assisted support and no online technical content updates.

Related products end alongside it, often on the same servers. Microsoft's 2027 end-of-support list gives these dates:

One more date compounds the risk. Microsoft's end-of-support planning page lists 14 July 2026 as the end of SQL Server 2016 extended support, so SQL Server 2016 on these servers is already outside standard support unless you bought SQL Server 2016 ESUs, which run to July 2029.

The 2026 change: ESUs exist, and Azure no longer makes them free

Microsoft announced ESUs for Windows Server 2016 on 25 February 2026, delivered through Azure Arc. Customers could configure them in the Azure portal from 3 August 2026, general availability was announced on 6 August, and billing starts on 13 January 2027. You get Critical and Important security updates for up to three years, through January 2030, and nothing else: no new features, no non-security fixes and no design changes. Microsoft's lifecycle FAQ describes the programme as a paid last resort and a temporary bridge, not a long-term answer.

The terms below come from Microsoft Learn, the Azure Arc pricing page and Microsoft's retail price list.

The meters are global retail prices effective 1 August 2026; monthly figures use Azure's 730-hour month. There are no separate Year 2 or Year 3 meters, so budget Year 1 with confidence and treat later years as unknown. Annual billing through volume licensing is available from your Microsoft representative.

Four points catch teams out.

Azure is not a free pass this time. For Windows Server 2012, ESUs were free on Azure VMs, Azure VMware Solution and Azure Stack HCI, now called Azure Local. On 27 March 2026 Microsoft announced that ESU offerings released on or after 1 April 2026 carry the same list price in Azure, on-premises or another cloud, through any purchasing channel. Microsoft's Azure Local ESU page names Windows Server 2016 under the new pricing, and the Azure Arc pricing page states the same-price rule. Older pages, including the lifecycle ESU FAQ, still describe free Azure ESUs; they were written for the 2012 cycle, which ended on 13 October 2026 (see our October 2026 end-of-life guide).

Azure VMs have their own meters. Microsoft's price list also carries Windows Server 2016 Azure ESU meters for VMs running in Azure, effective 1 September 2026, at $0.007132 per vCPU per hour, the same as the Standard core rate. We found no Microsoft Learn page that explains how they are enabled on Azure VMs, so confirm the mechanism with your account team.

Late enrolment is not a saving. For Windows Server 2012, Microsoft back-billed late Arc ESU sign-ups for every month missed since end of support, and the Arc pricing page applies the same one-time bill-back to late SQL Server 2016 sign-ups. Neither page states the rule for Windows Server 2016 yet, so do not plan around a gap: enrol stragglers before 12 January.

Physical versus virtual cores changes the bill. An 8-core branch server bills as 16 cores. A VM bills at the larger of 8 cores or its virtual core count. When only a few VMs on a large modern host still run 2016, Microsoft's own scenarios cover those VMs by virtual core instead of covering the whole host.

Arc servers enrolled in 2016 ESUs also get Azure Update Manager, Change Tracking and Inventory, and Azure Policy guest configuration at no extra charge, which makes Arc useful for inventory before you decide anything else.

Upgrade paths Microsoft supports from 2016

Microsoft's upgrade guide lists in-place upgrade, clean install, role migration, cluster OS rolling upgrade and edition conversion. From installation media, Windows Server 2016 can upgrade in place to 2019, 2022 or 2025. The lifecycle pages make the choice of target easy:

Starting with Windows Server 2025, non-clustered servers can upgrade up to four versions at a time, so 2016 to 2025 is one step. A cluster OS rolling upgrade moves one version at a time, so a 2016 failover cluster needs three rolling upgrades or a new 2025 cluster.

Microsoft lists these restrictions for in-place upgrades:

• The edition carries over. Standard can become Datacenter during the upgrade; Datacenter can never drop to Standard.

• No switching between Server Core and Desktop Experience.

• Disable NIC Teaming first and re-enable it afterwards.

• No in-place upgrade from Windows Storage Server editions or from servers that boot from VHD.

• Each Windows Server upgrade needs its own licence for the target version.

Microsoft says to back up every server before an upgrade or migration. Take that literally: a restore you have tested, not a backup job that reported success.

Active Directory and domain controllers

For domain controllers, Microsoft recommends a clean install: promote new servers running the newer version and demote the old ones, rather than upgrading DCs in place, so you get the full Active Directory improvements. The sequence:

1. Check functional levels. A Windows Server 2025 DC is supported at the Windows Server 2016 and 2025 functional levels, not at 2012 R2. Remove any 2012 R2 DCs and raise the forest and domain to the 2016 level before adding 2025 DCs.

1. Confirm SYSVOL uses DFSR. Domains at the 2016 functional level must replicate SYSVOL with DFSR, and Windows Server 2016 is the last release that supports the older FRS engine.

1. Promote new Windows Server 2025 servers. Server Manager and PowerShell run adprep for you during promotion. If you upgrade a DC in place instead, you must run adprep /forestprep and adprep /domainprep yourself.

1. Move the operation master (FSMO) roles to a new DC and confirm where they landed.

1. Demote and remove the 2016 DCs.

1. Raise the functional level to 2025 only when every DC runs 2025. That level adds the optional 32k database page feature and supports only Windows Server 2025 DCs, and forest and domain levels generally cannot be lowered once raised.

The commands for step 4, based on Microsoft's DC upgrade guide and the cmdlet reference. The -Identity value is the DC that receives the roles; 0 to 4 are the PDC emulator, RID master, infrastructure master, schema master and domain naming master.

            # Find the current role holders
Get-ADDomain | Format-List InfrastructureMaster, RIDMaster, PDCEmulator
Get-ADForest | Format-List DomainNamingMaster, SchemaMaster

# Move all five roles to the new Windows Server 2025 DC.
# Schema master and domain naming master are forest-wide roles, so run this
# as an account in Domain Admins, Enterprise Admins and Schema Admins.
Move-ADDirectoryServerOperationMasterRole -Identity "DC-2025-01" -OperationMasterRole 0,1,2,3,4

# Run the two Get commands again to confirm where the roles landed
          

Do identity first. Every later wave depends on healthy DCs, and a forest whose FSMO roles still sit on 2016 DCs on 13 January is the worst place to be.

Applications, databases and management tools

The OS upgrade is usually the easy part. Delays come from what runs on it.

• ISV support statements. Get written confirmation that each application supports Windows Server 2025. Missing statements are the usual reason to budget ESUs for a few VMs.

• SQL Server. SQL Server 2016 is already past extended support. Upgrade the OS and the database as one change, or move to Azure SQL Managed Instance, a route Microsoft's end-of-support page recommends for avoiding future upgrade cycles.

• .NET Framework 4.6.2. It ends with the OS. Test apps built against it on the framework version that ships with Windows Server 2025.

• System Center 2016. It ends on 11 January, and System Center 2025 has been generally available since 6 November 2024. Move monitoring, DPM backup and VMM early, so the tools protecting the migration are themselves supported.

• WSUS. WSUS for Windows Server 2016 ends with the OS. WSUS is deprecated, meaning no new features, but it still ships and is supported in Windows Server 2025, and Microsoft points server patching to Azure Update Manager.

• What 2025 removed or switched off. TLS 1.0 and 1.1 are disabled by default, and NTLMv1, the SMTP Server feature and Windows PowerShell 2.0 are removed. Test any app, script or mail relay that still depends on them.

• Hyper-V hosts and storage servers. Hyper-V Server 2016 and Storage Server 2016 end in January, and Storage Server cannot upgrade in place. Hosts move to Windows Server 2025 Datacenter or another platform; file shares move to a new server.

Which path for which server

Use this as the triage key for every 2016 instance. It follows the Microsoft guidance cited above.

Worked example: what an ESU bridge really costs

This is an illustrative estate, not a client case. Two groups will still run Windows Server 2016 on 12 January 2027:

• 12 application VMs with 4 vCPUs each, waiting for ISV certification, on two 32-core hosts that already run Windows Server 2025 Datacenter.

• 8 branch-office physical servers with 8 cores each, Standard edition.

Figures use Microsoft's Year 1 meters ($0.007132 and $0.041067 per core per hour) and a 730-hour month, which gives $5.20636 per Standard core and $29.97891 per Datacenter core a month. Software Assurance, which ESUs require, is assumed and not priced. Licence prices are Microsoft's suggested prices for 16-core Windows Server 2025 licences.

The 12 VMs. Covering both hosts by physical core at the Datacenter rate means 64 × $29.97891 = $1,918.65 a month, or $23,024 a year. Covering the VMs by virtual core at the Standard rate bills each VM at the 8-core minimum: 96 × $5.20636 = $499.81 a month, so $2,999 for six months or $5,998 for a year, about a quarter of the host route.

The 8 branch servers. Each bills at the 16-core minimum: 128 × $5.20636 = $666.41 a month, or $7,997 a year. Eight Windows Server 2025 Standard 16-core licences at $1,176 each total $9,408, so ESU spend passes the cost of new licences in about 14 months ($9,408 ÷ $666.41 = 14.1).

ESUs are affordable for a few months on a few VMs and expensive for whole hosts. Billing also does not shrink on its own: Microsoft says you must reduce the cores on an ESU licence yourself as servers are upgraded.

A 90-day plan with the deadline inside it

On 1 November 2026, 12 January 2027 is 72 days away; on 1 December it is 42. If day 1 is 1 November, the deadline falls on day 73. Anything that cannot finish before then must be enrolled in ESUs first.

For phase 6, a licence created in a deactivated state does not bill, and for 2016 you pick physical or virtual cores when you enable ESUs on each machine. After linking, azcmagent show should report the ESU status as active. If you start later than 1 November, compress phases 4 and 5 and move the ESU gate earlier.

Pre-cutover checklist

• Tested restore for every server.

• NIC Teaming disabled before each in-place upgrade; edition and installation type confirmed.

• Licence and activation ready for Windows Server 2025.

• Forest and domain at the 2016 functional level, SYSVOL on DFSR.

• Written ISV support statements on file.

• Arc agent 1.62 or later on any server that might need ESUs, with the required endpoints reachable.

• ESU licences provisioned and eligibility attested.

• Backup, monitoring and security agents compatible with Windows Server 2025.

• Patch source (WSUS, Configuration Manager or Azure Update Manager) set to deliver ESU updates.

India, EU and US notes

India. Azure's pricing pages list four India regions (Central India, India South Central, South India and West India) and can show prices in rupees. An in-place upgrade keeps personal data where it sits. If workloads move to Azure, keep personal data in Indian regions where your regulator expects it; our DPDP engineering playbook covers the obligations.

EU. If the exit includes a cloud move, read our note on the EU Data Act's cloud switching rules before signing multi-year commitments.

US. Microsoft's retail price list shows the same 2016 ESU rates on its US Government meters as on the global meters.

How eCorpIT can help

eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. Our cloud migration services team runs Windows Server 2016 exits end to end, from Azure Arc inventory and server triage to domain controller rebuilds, upgrade waves and ESU enrolment for the stragglers. Talk to us at /contact-us/.

Last updated: 1 November 2026.

References

1. Ending Support in 2027 — Microsoft Learn

1. Planning ahead for Windows Server 2016 end of support, 25 February 2026 — Microsoft Windows Server Blog

1. Generally available: Windows Server 2016 Extended Security Updates enabled by Azure Arc, 6 August 2026 — Microsoft Tech Community

1. Azure Retail Prices API: Azure Arc Extended Security Updates meters — Microsoft

1. License provisioning guidelines for Extended Security Updates for Windows Server — Microsoft Learn

1. Prepare to deliver Extended Security Updates for Windows Server — Microsoft Learn

1. Microsoft Services: Pricing Consistency Update, 27 March 2026 — Microsoft Licensing

1. Plan your Windows Server upgrade — Microsoft Learn

1. Windows Server 2025 lifecycle — Microsoft Learn

1. Windows Server 2016 lifecycle — Microsoft Learn

1. Plan your Windows Server and SQL Server end of support — Microsoft

1. SQL Server 2016 lifecycle — Microsoft Learn

1. Lifecycle FAQ: Extended Security Updates — Microsoft Learn

1. Deliver Extended Security Updates for Windows Server — Microsoft Learn

1. Rename Azure Stack HCI to Azure Local, archived 19 November 2025 — Microsoft Learn

1. Extended Security Updates on Azure Local — Microsoft Learn

1. Azure Arc pricing — Microsoft Azure

1. Azure Retail Prices API: Windows Server Azure ESU meters — Microsoft

1. Windows Server 2019 lifecycle — Microsoft Learn

1. Windows Server 2022 lifecycle — Microsoft Learn

1. Upgrade domain controllers to a newer version of Windows Server — Microsoft Learn

1. Active Directory Domain Services functional levels — Microsoft Learn

1. Move-ADDirectoryServerOperationMasterRole — Microsoft Learn

1. Microsoft System Center 2025 is now generally available, 6 November 2024 — Microsoft Windows Server Blog

1. Windows Server Update Services (WSUS) deprecation, 20 September 2024 — Windows IT Pro Blog

1. Features removed or no longer developed in Windows Server — Microsoft Learn

1. Windows Server 2025 licensing and pricing — Microsoft