Windows Server 2016 End of Support: Refresh, Migrate, or Extend
What ends on January 12, 2027, four paths for Windows Server 2016 servers based on Microsoft's documentation, and how to decide server by server.
What ends on January 12, 2027
Microsoft ends extended support for Windows Server 2016 on January 12, 2027. After that date, servers receive security updates only if they are covered by paid Extended Security Updates (ESUs). The dates below are from Microsoft's own documentation as of October 2026; confirm them on the linked sources before you plan around them.
| Milestone | Date or period | What Microsoft says |
|---|---|---|
| Windows Server 2016 end of support | January 12, 2027 | Extended support ends in line with the Microsoft Lifecycle Policy |
| ESU setup opens in the Azure portal | August 3, 2026 | Windows Server 2016 ESUs can be configured from this date |
| ESU billing starts | January 13, 2027 | Billing for ESUs enabled by Azure Arc begins; licenses provisioned after January 12, 2027 are back-billed to that date |
| ESU coverage ends | Up to three years, through 2030 | Critical and Important security updates only |
Start with an inventory of every 2016 server
The right path differs from server to server, so the decision starts with a list, not a purchase. For each Windows Server 2016 instance, record:
- Whether it is a physical server or a virtual machine, and the age and warranty status of the hardware underneath it
- Its roles: domain controller, file and print, Hyper-V host, cluster node, or application server
- The applications it runs, and whether each vendor supports a newer Windows Server version
- Any SQL Server instance on the same server, and its version
- Its edition (Standard or Datacenter) and how it is licensed, because licensing decides ESU eligibility and edition affects how ESUs are licensed and billed
- Copies used for disaster recovery, which need their own ESU coverage to receive updates
See the server and storage refresh page.
Four paths: upgrade, refresh, migrate, or extend
Each 2016 server ends up on one of four paths. Many environments use more than one.
| Path | When it fits | What it depends on | Watch for |
|---|---|---|---|
| Upgrade in place | The hardware has life left and the applications support a newer version | Microsoft's supported upgrade paths and each application vendor's support | A reboot and downtime per server; clusters move one version at a time |
| Refresh with a clean install | Hardware is aging, or the environment is being consolidated or re-platformed | Sizing new servers and storage for the workloads, then migrating them | More planning per workload, and time for procurement and staging |
| Migrate to Azure | Workloads that suit a cloud platform | A migration plan for each workload and its data | Microsoft lists the same ESU list price for Windows Server 2016 in Azure as on premises |
| Extend with ESUs | Servers that cannot move before the end of support | Eligible licensing and a supported edition, through Azure Arc or Volume Licensing | Critical and Important security updates only, and coverage that ends in 2030 |
When an in-place upgrade is an option
Microsoft documents an in-place upgrade from Windows Server 2016 to Windows Server 2019, Windows Server 2022, or Windows Server 2025 for servers that are not clustered.
Clusters move one version at a time
A cluster OS rolling upgrade upgrades nodes one at a time while Hyper-V or Scale-Out File Server workloads keep running, but clusters can only upgrade one version at a time. Plan more than one step to reach the newest version.
Check the applications before the operating system
Microsoft's prerequisites for an in-place upgrade include checking which roles and features support it and any non-Microsoft application vendor requirements, a full backup with a restore test, and a maintenance window, because downtime is required. Confirm with each application vendor that the target version is supported before scheduling it.
Hardware still has to last
Upgrading the operating system does not extend the life of the server under it. If the hardware is near the end of its warranty, a refresh can cost less effort than upgrading now and replacing the server later.
Extended Security Updates as a bridge, not a destination
ESUs buy time for servers that cannot move before January 12, 2027. Microsoft offers them through Azure Arc with pay-as-you-go billing, and classic ESUs through Volume Licensing are purchased in yearly increments. Microsoft's terms for Windows Server 2016 ESUs enabled by Azure Arc:
- Critical and Important security updates for up to three years, through 2030. No new features or non-security fixes
- Standard and Datacenter editions are supported
- Requires Software Assurance through Volume Licensing or Microsoft Open Value programs, or servers licensed through SPLA or a server subscription
- Servers connect through the Azure Connected Machine agent, version 1.62 or higher
- Setup opens August 3, 2026; billing for ESUs enabled by Azure Arc starts January 13, 2027 and is monthly, and licenses provisioned after the end of support are back-billed to January 12, 2027
- The no-cost disaster recovery benefit does not apply: disaster recovery copies need their own ESU coverage
- For ESUs released on or after April 1, 2026, including Windows Server 2016, Microsoft charges the same list price whether the server runs in Azure, on premises, or in another cloud
- Microsoft's ESU pages for Windows Server 2012 describe ESUs as free in Azure, with notes for Azure VMware Solution and Azure Local. Those terms belong to the earlier program, which Microsoft excludes from the new pricing. Windows Server 2016 falls under the same-price rule, including on Azure Local, so do not plan on free ESUs for 2016 servers moved to Azure. If a page describes free ESUs, check which release it covers
Check SQL Server on the same servers
Windows Server 2016 servers may also run SQL Server versions with their own support dates. Extended support for SQL Server 2016 already ended on July 14, 2026, and Microsoft lists 2027 as the end of extended support for SQL Server 2017. SQL Server 2016 customers can subscribe to ESUs, but Microsoft states they are not eligible for free ESUs on Azure virtual machines. Plan the database and the operating system together, so a server is not migrated twice.
Choosing the target version
Microsoft's Windows Server blog describes end of support as an opportunity to upgrade to Windows Server 2025 or consider migrating to Azure. Windows Server 2019 and Windows Server 2022 are also supported upgrade targets, but each has its own end of support date; check the Microsoft lifecycle page for any version before committing to it, so the new platform is not the next deadline.
Turning the decision into a project plan
With the inventory and the path for each server decided, the work becomes a sequenced project:
- Group servers by path: upgrade, refresh, migrate, or extend
- Order the work by risk, starting with internet-facing servers and those holding sensitive data
- Size replacement servers and storage from current workloads, not from the old hardware
- Set the ESU scope only for servers that cannot move in time, with a date to retire each one
- Schedule changes around business cycles, and take a full backup with a restore test before each cutover
See the enterprise infrastructure modernization service, the Azure cloud planning page and the backup and recovery planning page.
Plan your Windows Server 2016 transition with Days Dynamics
Send us your server inventory and we will help you sort each server into a path, size replacement infrastructure, and plan the sequence of work around the January 12, 2027 date. A planning call is planning support, not a quote, an audit, or a commitment on licensing, availability, or delivery dates.
Sources
Primary sources checked when this guide was written. Dates and product status can change, so confirm on the source before you rely on them.
- Microsoft Windows Server blog: Planning ahead for Windows Server 2016 end of support (opens in a new tab)
- Microsoft Learn: Prepare to deliver Extended Security Updates (Windows Server 2016) (opens in a new tab)
- Microsoft Learn: Billing for Extended Security Updates (Windows Server 2016) (opens in a new tab)
- Microsoft Learn: License provisioning for Extended Security Updates (Windows Server 2016) (opens in a new tab)
- Microsoft Learn: Extended Security Updates on Azure Local (opens in a new tab)
- Microsoft: Extended Security Updates for Windows Server and SQL Server (opens in a new tab)
- Microsoft Learn: Extended Security Updates for Windows Server 2012 and 2012 R2 (opens in a new tab)
- Microsoft Tech Community: Plan for upcoming changes to Extended Security Updates on Azure Local (opens in a new tab)
- Microsoft Licensing: Pricing consistency update (March 27, 2026) (opens in a new tab)
- Microsoft Learn: Upgrade Windows Server in place (opens in a new tab)
- Microsoft Learn: Plan your Windows Server upgrade path (opens in a new tab)
- Microsoft Learn: SQL Server end of support options (opens in a new tab)
- Microsoft Learn: Extended Security Updates for SQL Server (opens in a new tab)
Related services
Related resources
Turn the checklist into a snapshot
The assessment turns this checklist into a two-minute planning snapshot for your situation, before any contact details.