The Microsoft Lifecycle page gives Windows Server 2016 one date on which the rest of the plan depends: Windows Server 2016 end of life for extended support falls on 12 January 2027. From the publication date of this text, 19 November 2026, that leaves 54 days. The period includes Christmas, New Year, Epiphany (a public holiday in Poland) and the year-end close, when many IT departments run a change freeze on production systems.
A server running Windows Server 2016 will still boot and serve users after 12 January 2027. It will, however, stop receiving security updates unless the organisation buys the Extended Security Updates programme. Every vulnerability disclosed later will stay in that system permanently, which makes it a cybersecurity problem for the whole network, not just one machine. The choice between an in-place upgrade, a clean install, role migration and ESU therefore has to be made separately for each server, before the change freeze begins.
When exactly does Windows Server 2016 support end?
Windows Server 2016 extended support ends on 12 January 2027. According to the Windows Server 2016 page in Microsoft Lifecycle, the system follows the Fixed Lifecycle Policy, and its support began on 15 October 2016.
Mainstream support ended on 11 January 2022. Since then Microsoft has added no new features and has delivered security updates under extended support. That is the phase now coming to an end.
The dates on the Lifecycle page are shown in the Pacific Time Zone (PT). That is why the table shows the end of extended support as “1/13/2027 6:59:59 AM”, the last second of 12 January 2027 Pacific Time. For an organisation in Europe the practical conclusion is simple: the last regular update cycle for Windows Server 2016 falls on 12 January 2027, and anything after that requires ESU.
In its description of the ESU programme, Microsoft states that the Windows Server Long Term Servicing Channel (LTSC) has a minimum of 10 years of support: five years of mainstream and five years of extended support. Windows Server 2016 has gone through both phases on the dates in the Lifecycle table.
What does the end of extended support mean for a server in your organisation?
The end of extended support means the end of security updates. Microsoft says so plainly in its description of the ESU programme: once a product reaches the end of support, security updates and bulletins end as well. The vendor adds that this can cause security or compliance issues and put business applications at risk.
A server running Windows Server 2016 is often the host for roles on which other systems depend: a domain controller, a file server, an application server, a Remote Desktop gateway or a Hyper-V host. An unpatched flaw in such a system therefore does not affect a single machine. An attacker who exploits it gains a foothold for the rest of the network.
The second consequence concerns audits. Security requirements that an organisation has adopted in its policies, customer contracts or risk management, as a rule, assume that systems receive updates. A server without vendor support is hard to defend in front of an auditor without a documented exception, an exit date and measures that limit the risk.
Key points:
- Windows Server 2016 extended support ends on 12 January 2027 (Microsoft Lifecycle, dates in PT).
- After that date only a server covered by the paid ESU programme receives security updates — for Windows Server 2016 in Azure as well.
- Microsoft calls ESU a last resort option, not a way to keep the system running indefinitely.
- Windows Server 2016 can be upgraded in place to versions 2019, 2022 and 2025, but not every role supports this.
What is ESU for Windows Server 2016 and who is it for?
Extended Security Updates (ESU) is a paid programme of security updates for systems past the end of support. Microsoft describes it as a last resort option for customers who need to run certain legacy Microsoft products past the end of support. ESU includes security updates and bulletins rated critical and important. It does not include new features, customer-requested non-security hotfixes or design change requests.
The Windows Server 2016 Lifecycle page lists three yearly ESU periods. The first runs from 13 January 2027 to 11 January 2028, the second to 9 January 2029 and the third to 8 January 2030. Each year is a separate period in the table, with its own end date. According to Microsoft, you can buy the licence for the second and third year only if you already hold the licences for the earlier years.
The access model for Windows Server 2016 is described in the Microsoft Lifecycle ESU FAQ, November 2026 version. On-premises and hybrid servers get ESU through specific volume licensing programmes or through Azure Arc-enabled servers, and the conditions include active Software Assurance or subscription licences. The programme covers the Standard and Datacenter editions. You download the activation keys from the Microsoft 365 admin centre and install them on the servers, so the contract alone is not enough if the key never reaches the actual machines. In Azure, ESU for Windows Server 2016 is paid, unlike the earlier offer for Windows Server 2012 and 2012 R2.
In practice ESU makes sense for servers that cannot be moved before 12 January 2027: vendor applications not certified on a newer version of the operating system, systems under a change freeze until a project ends, or machines whose replacement needs new hardware with a distant delivery date. For the remaining servers the programme is a cost that postpones the decision but does not replace it.
How do you find out which of your servers run Windows Server 2016?
The first step is a complete list of servers with the operating system version, role, business owner and dependencies. Without it you cannot judge how much work remains, and it is easy to miss a machine nobody remembers.
There are three sources for this list, and it is worth comparing them because each sees something different. The Active Directory catalogue shows domain-joined computers together with their operating system. The virtualisation console shows virtual machines, including those outside the domain. The patch or configuration management system shows the machines that report to it. A server present in only one of these sources is the first candidate for a closer look.
For each server, record three facts straight away: which roles and applications it runs, whether the application vendor supports it on Windows Server 2019, 2022 or 2025, and whether the machine runs on hardware the newer system will support. The answers to these questions determine the exit path for each server.
Which exit paths from Windows Server 2016 does Microsoft describe?
Microsoft describes five methods of moving to a newer version of Windows Server: an in-place upgrade, a clean install, role migration, a cluster OS rolling upgrade and an edition conversion. Each balances downtime, complexity and hardware requirements differently (Windows Server upgrade overview).
An in-place upgrade installs the newer system over the existing one and keeps settings, roles, features and data. A clean install gives a fresh environment on a new server or in place of the old system. Migration moves roles or features from the old server to a new one running a newer system. Failover clusters are upgraded node by node, without stopping Hyper-V and Scale-Out File Server workloads.
For Windows Server 2016, the table of in-place upgrade paths from installation media allows a move to Windows Server 2019, 2022 and 2025. From version 2025 onwards, non-clustered servers can jump up to four versions at a time, while a cluster on a rolling upgrade advances only one version. A Windows Server 2016 cluster therefore reaches version 2025 in three steps.
When does an in-place upgrade make sense, and when is role migration better?
An in-place upgrade makes sense when the server stays on the same hardware, its roles support this method and the business accepts a reboot and a short maintenance window. Migration is better when the hardware changes, when a role does not support an in-place upgrade or when the server has accumulated years of configuration that nobody can reproduce any more.
Microsoft lists restrictions worth checking before you decide. An in-place upgrade will not turn a Server Core installation into one with the Desktop Experience, or the other way round. It will not change the system language. By default it keeps the edition, so Standard upgrades to Standard. Not all roles support this method, and before any upgrade, clean install or migration the vendor recommends backing up the system and important files.
Licensing is a separate issue. Microsoft notes that, unlike Windows client, each Windows Server upgrade requires a separate licence. The budget for leaving Windows Server 2016 should therefore cover licences for the target version whichever path you choose.
In practice a simple rule works well: upgrade in place the servers with a single, simple role and current hardware supported by the target version, and migrate to new machines the servers with several roles, old hardware or undocumented configuration. Migration takes longer, but it leaves the old server as a fallback for the duration of testing.
What should you do with an application that does not run on a newer system?
When an application has no vendor support on a newer Windows Server, three routes remain: update the application to a version compatible with the new system, replace it with another solution, or keep the old server under ESU for a defined period. The first route is the shortest if the vendor has already released a newer version. The second requires a project. The third buys time, but it has a cost and an expiry date.
A server that stays on Windows Server 2016 for longer is worth treating as a high-risk system regardless of ESU. In practice this means network segmentation that restricts traffic to the necessary ports, disabling unneeded services, reviewing accounts with administrator rights on that machine and monitoring sign-ins. These measures do not replace updates, but they reduce the consequences of not having them.
Organisations went through the same decision pattern with workstations before Windows 10 support ended in October 2025, when they planned inventories, compatibility tests and rollouts of Windows 11 for user computers. With servers there are added dependencies between systems and longer maintenance windows, but the order of work is similar.
Does moving the server to Azure solve the end-of-support problem?
Moving a server to Azure does not give Windows Server 2016 free ESU updates, and it does not change the operating system version. According to the Microsoft Lifecycle FAQ, ESU at no additional charge in Azure covered Windows Server 2012 and 2012 R2 (their third ESU year ended on 13 October 2026), while for Windows Server 2016 it is a paid offering. Microsoft says it will provide information on installing and delivering these updates in Azure when the service becomes generally available.
Migration to Azure is therefore worth considering for servers that the organisation was planning to move to the cloud anyway, not as a route to ESU. For the rest it means a separate project: connectivity, backups, identity, access control and the running costs of machines in the cloud. The ESU end date applies in Azure as well, so migration postpones the operating system version problem but does not remove it.
How do you plan your exit from Windows Server 2016 in 54 days?
In the 54 days between 19 November 2026 and 12 January 2027, a realistic plan starts by splitting servers into three groups, not by upgrading the first machine. Group one is the servers you can upgrade or migrate before the year-end change freeze. Group two is the servers with a migration planned for the first quarter of 2027, which need ESU for a transition period. Group three is systems being retired, which you simply switch off.
For group two, it is worth taking the ESU decision before 12 January 2027: purchasing, obtaining the key and installing it on each machine take time, and a server without active ESU is left without updates from the first release after that date. For group one the tests after the upgrade matter most: user sign-ins, application behaviour, backups and monitoring.
Every server that stays on Windows Server 2016 after 12 January 2027 should have an entry in the risk register with an owner, a reason, an exit date and a list of measures that limit the risk. Such an entry distinguishes a conscious decision from neglect, including during an audit.
Which path should you choose for a specific server?
The choice of path follows from four characteristics of the server: hardware, roles, application compatibility and tolerance for downtime. Hardware comes first, because an in-place upgrade keeps the system on the same machine, while migration needs a new one.
| Server situation | Path | Condition | What to watch |
|---|---|---|---|
| Current hardware supported by the target version, one simple role, application supported on a newer version | In-place upgrade from media to 2019, 2022 or 2025 | The role supports an in-place upgrade | Backup before the change, same edition, licence for the target version |
| Old hardware or undocumented configuration | Role migration to a new server | A new machine and a window for testing | The old server as a fallback until testing ends |
| Failover cluster | Rolling upgrade node by node | One version at a time | Three steps from version 2016 to version 2025 |
| Application without support on a newer system | ESU for a transition period and an application change project | ESU decision and purchase before 12.01.2027 | Segmentation, fewer administrator accounts, exit date in the risk register |
| Server planned for a move to the cloud | Migration to an Azure virtual machine | Migration project ready | ESU for 2016 in Azure is paid and has an end date |
| System with no owner and no users | Retirement | Confirmation that nothing depends on it | Archive the data before switching it off |
If a server fits two rows at once, the deadline decides: the path you can close before the change freeze beats the architecturally neater one.
How can nFlo help you leave Windows Server 2016?
nFlo runs two services that fit this project. The IT System and Infrastructure Configuration Review is a technical audit of servers, networks, storage and Active Directory against CIS Benchmarks and vendor best practices, ending with a report of deviations and hardening guidance. For Windows Server it covers, among other things, account policies, user rights assignment, security options and audit policies, and firewall configuration.
Server Infrastructure Implementation and Optimization covers the design, deployment, migration and high availability of Windows Server and Linux environments, with hardware sized on the basis of workload measurements. If you want to establish which servers to upgrade, which to migrate and which need ESU, contact us.
What else should you know about the end of support for Windows Server 2016?
Will Windows Server 2016 stop working after 12 January 2027?
No. The system will boot and run as before. What changes is that without the ESU programme it will no longer receive security updates, so every new vulnerability stays in it permanently.
Is ESU for Windows Server 2016 available outside Azure?
Yes. According to the Microsoft Lifecycle ESU FAQ (November 2026 version), on-premises and hybrid servers get ESU through specific volume licensing programmes or through Azure Arc. In Azure, ESU for Windows Server 2016 is paid, unlike the earlier offer for Windows Server 2012. The Microsoft Lifecycle page lists three yearly ESU periods, from 13 January 2027 to 8 January 2030.
Can you go straight from Windows Server 2016 to Windows Server 2025?
Yes, with an in-place upgrade from installation media. Microsoft lists upgrade paths from Windows Server 2016 to versions 2019, 2022 and 2025. Clusters using a rolling upgrade can only advance one version at a time.
Will an in-place upgrade keep the server roles and data?
It keeps settings, roles, features and data, but not every role supports an in-place upgrade. Microsoft recommends backing up the system and important files before any upgrade or migration.
Do you need a new licence after upgrading to a newer version?
Yes. Microsoft notes that, unlike Windows client, each Windows Server upgrade requires a separate licence for the target version.
