Windows Server 2016 End of Life: Upgrade, ESU, Azure, or Hosted?
Windows Server 2016 extended support ends on January 12, 2027. After that date, Microsoft stops shipping security updates, bug fixes, and technical support for it, although your servers will keep running. You have four realistic paths: upgrade in place (Windows Server 2016 can go straight to 2025), move the workload to Azure, buy paid Extended Security Updates as a temporary bridge, or move to a hosted server or desktop where a provider runs the platform. Most businesses end up using more than one, server by server.
Windows Server 2016 has been a dependable platform for business workloads since its release in October 2016, and many organizations still depend on it for critical applications and infrastructure. This guide explains exactly what changes on January 12, 2027, compares the four paths, and gives you a workload-by-workload decision table and a 60-day plan.
Apps4Rent migrates and hosts Windows Server workloads, so one path below is ours. We describe all four plainly.
Key Takeaways
- Extended support ends January 12, 2027, a Patch Tuesday. Mainstream support already ended on January 11, 2022.
- Servers do not stop working, but they stop receiving security updates and bug fixes unless they are enrolled in paid Extended Security Updates (ESUs).
- ESUs for Windows Server 2016 cover Critical and Important updates for up to three years, through January 2030, delivered through Azure Arc. They are paid, including in Azure.
- Windows Server 2016 can upgrade in place directly to 2019, 2022, or 2025. Windows Server 2025 has the longest runway, with mainstream support to November 13, 2029.
- Match each server to a path by workload. File servers, domain controllers, SQL hosts, remote desktop servers, and QuickBooks or tax hosts each have a natural next step.
- Servers that cannot move in time should be isolated, tightened, and given a written retirement date.
Why So Many Servers Are Still on Windows Server 2016
Most organizations that have not moved are not unaware of the deadline. The delay usually has practical causes:
- Legacy applications. Business-critical software built for older environments often needs testing or changes before an upgrade.
- Tangled infrastructure. Servers, databases, and services depend on each other, and upgrades need careful sequencing to avoid disruption.
- Competing priorities. Server modernization competes with security, operations, and business projects for the same people.
- Hardware limits. Older hardware and specialized workloads may not be ready for a newer Windows Server without extra investment.
- A preference for phased moves. Many teams upgrade gradually to validate workloads and limit risk.
All of those are reasonable. None of them moves the deadline.
What Changes on January 12, 2027
Windows Server 2016 follows Microsoft’s fixed lifecycle: five years of mainstream support, which ended on January 11, 2022, then five years of extended support, which ends on January 12, 2027. That day is a Patch Tuesday, and it brings the last security updates Windows Server 2016 will receive without paid ESU coverage. From then on, Microsoft ships no new security updates or bug fixes for the operating system, and standard support cases close. Your servers keep booting, which is exactly what makes the date easy to ignore.
| Windows Server version | Mainstream support | Extended support ends |
|---|---|---|
| 2016 | Ended January 11, 2022 | January 12, 2027 |
| 2019 | Ended January 9, 2024 | January 9, 2029 |
| 2022 | Ended October 13, 2026 | October 14, 2031 |
| 2025 | Until November 13, 2029 | November 14, 2034 |
Notice what the table implies for planning. Moving to Windows Server 2019 only buys you until January 2029, so it replaces one deadline with another. Our Windows Server 2019 timeline covers that date in detail.
What Happens If You Stay on Windows Server 2016?
Continuing past January 12, 2027 may seem manageable at first, but the risks compound over time:
- Security exposure. Newly discovered vulnerabilities stop getting patches, which leaves servers more exposed to ransomware and other attacks. Exploiting unpatched software was already the most common way into organizations in Verizon’s 2026 breach report.
- Compliance and audit pressure. Many frameworks expect supported software, so unsupported servers create findings in audits, security assessments, and insurance questionnaires.
- Compatibility drift. Application and hardware vendors focus on newer platforms, and support for 2016 gradually thins out.
- Rising operating costs. Workarounds, longer recovery times, and limited support options often cost more than a planned migration.
Your Four Options After Windows Server 2016
| Option | What it means | Best for | Main trade-off |
|---|---|---|---|
| Upgrade | Move the server to Windows Server 2025 or 2022 | Workloads and hardware that are ready | Application testing and licensing |
| Move to Azure | Rehost the server in Azure, then modernize | Teams leaving aging hardware | Ongoing Azure costs; no free ESUs for 2016 |
| Buy ESUs | Pay for security updates after January 2027 | A few servers that cannot move in time | Paid, security-only, temporary |
| Go hosted | Let a provider run the server or desktop | Small teams without IT staff | Less control over the platform |
Option 1: Upgrade to Windows Server 2025 or 2022
Upgrading keeps the workload where it is and moves it to a supported operating system. Windows Server 2016 can upgrade in place directly to 2019, 2022, or 2025. For servers that are not clustered, Windows Server 2025 can upgrade across up to four versions in one step, while 2022 and earlier targets move up to two at a time. Clustered servers upgrade one version at a time with a rolling upgrade.
Which version? Windows Server 2022 left mainstream support on October 13, 2026, and now has security-only support until October 14, 2031. Windows Server 2025 stays in mainstream support until November 13, 2029, with extended support to November 14, 2034. Unless an application vendor has not certified 2025, it has the longest runway and keeps you from repeating this project in a few years.
Before you start: take a full backup and test the restore, rehearse the upgrade on a copy, confirm each application vendor supports the new version, check hardware requirements, and budget for the new licenses and client access licenses, which generally must match or exceed the server version. For older, heavily modified servers, building a fresh server and migrating roles and data is often safer than an in-place upgrade.
Option 2: Move to Azure
Moving to Azure takes the server off aging hardware and into a managed cloud platform. The usual sequence is rehost first, then modernize: move the virtual machine to Azure, upgrade it to Windows Server 2025 once it is running there, and replatform pieces such as databases or web apps when things are stable.
One assumption deserves retiring. In the Windows Server 2012 cycle, servers running in Azure received Extended Security Updates at no extra charge. Microsoft’s lifecycle FAQ is explicit that free ESUs are not available for Windows Server 2016 in Azure, where they are a paid offering. Azure is a place to migrate to, not a way to avoid paying for an unsupported operating system. Our walkthrough of the four Azure migration paths covers rehosting, replatforming, bridging, and retiring in depth, and you can request a free end-of-life assessment from our Azure team to map your own estate.
Option 3: Buy Extended Security Updates as a Bridge
ESUs are Microsoft’s paid bridge for servers that cannot move by the deadline. For Windows Server 2016, they provide Critical and Important security updates for up to three years after end of support, covering January 12, 2027 through January 2030. Microsoft’s coverage years end on January 11, 2028, January 9, 2029, and January 8, 2030.
How they work: ESUs are delivered through Azure Arc. You connect each server by installing the Azure Connected Machine agent, then enroll eligible servers from the Azure portal or at scale with Azure Policy, and you pay through Azure. Licensing eligibility rules apply, so confirm yours before you count on ESUs in your plan.
What they do not do: ESUs add no new features and no non-security fixes, and the cost builds each year you rely on them. Treat them as a safety net for the few servers that truly cannot move, and give every enrolled server a written retirement date. They are a bridge, not a plan for the whole estate.
Option 4: Move to a Hosted Server or Desktop
Moving to a hosted environment hands the operating system, patching, and backups to a provider, so there is no Windows Server version left for you to retire. It fits businesses whose servers exist to run a few applications: a QuickBooks or tax software host, a remote desktop server, or a file server for a small team.
Apps4Rent’s rented virtual servers are unmanaged by default, with server administration available if you want us to patch and monitor them, while our fully managed Windows desktops are a complete service we run for you. The trade-offs are real: less control over operating system settings, application compatibility to confirm before the move, and exit terms to review before you sign.
Five Questions That Pick Your Path
Before you map servers to options, answer these five questions for each one. The answers usually point to a path on their own.
- Does the application vendor support Windows Server 2025? If not, you need a bridge such as ESUs, or a plan to replace the application.
- Is the hardware ready? Spending on an in-place upgrade for an aging machine can be the wrong investment. Azure or a hosted server avoids the hardware refresh.
- Do you have people to run it? If nobody on staff patches and monitors servers, a hosted option removes the job entirely.
- How much downtime can you take, and when? Upgrades and cutovers need windows. A tax practice or a retailer should avoid its peak season.
- Are there compliance constraints? Data location, audit logging, and regulated data narrow the choices, so confirm any provider’s attestations before you commit.
Two or more answers that point away from an in-place upgrade usually mean Azure or a hosted environment deserves a serious look.
Which Path for Which Workload?
The right answer is rarely the same for every server. A rented cloud server and a hosted cloud desktop solve different problems, and our comparison of a rented cloud server or a hosted desktop helps with that part of the decision. This table covers the common Windows Server 2016 roles:
| Workload | A sensible next step | Watch for |
|---|---|---|
| File and print server | Upgrade to 2025, or move shared files to cloud storage | Permissions, mapped drives, and legacy paths |
| Active Directory domain controller | Add new Windows Server 2025 domain controllers, move the roles, and retire the old ones | Functional levels, DNS, and replication health |
| SQL Server host | Upgrade the operating system and SQL Server together | SQL Server 2016 extended support ended July 14, 2026, so the database is already out of date |
| Remote Desktop Services server | Move users to hosted or Azure-based desktops, or rebuild on 2025 | Remote desktop licensing, profiles, and printing |
| QuickBooks, Sage, or tax software host | Host it with an QuickBooks hosted by an Intuit authorized provider, or rebuild on 2025 | License terms and multi-user performance |
| Hyper-V host | Upgrade the host to 2025, then review the guest operating systems | Guests may also be on 2016 |
| Legacy line-of-business application | Bridge with ESUs and network isolation while you replace the app | Vendor support and how exposed the server is |
What to Budget For
Each path has a different cost shape, and comparing them honestly means counting every line. Prices change, so ask for current quotes instead of relying on rules of thumb.
- Upgrade: new Windows Server licenses and client access licenses, possible hardware refresh, migration labor, and application testing.
- Azure: compute and storage charges, migration effort, Azure Hybrid Benefit eligibility where it applies, and later modernization work.
- ESUs: a subscription for each enrolled server for each year of coverage, plus the Azure Arc setup, and still the cost of the migration you are postponing.
- Hosted: a monthly fee that usually bundles the infrastructure, with licensing, backups, and administration depending on the plan.
Do not compare only the first year. ESUs and ongoing cloud costs recur, while an upgrade is mostly a one-time project, and a hosted plan trades project cost for a predictable monthly one.
Licensing Questions to Settle Early
Licensing causes more late-stage surprises than technology does. Settle these before you commit to a path, and confirm the details with your reseller or Microsoft, because the rules change.
- Server licenses and client access licenses. A newer Windows Server needs current licenses, and client access licenses generally must match or exceed the server version.
- Remote Desktop Services licenses. These are separate and tied to a version, which matters if the server hosts user sessions.
- Software Assurance and Azure Hybrid Benefit. Existing licenses with Software Assurance may lower Azure costs, and licensing coverage can also affect ESU eligibility.
- Application license terms. Some applications, including accounting software, set conditions for hosted use, so check before you move them.
- What a hosted plan includes. Ask whether the Windows license and remote desktop licenses are bundled or billed separately.
Find Every Windows Server 2016 Machine
You cannot plan around servers you have not found. Start with what you can query, then look for what you cannot.
Windows Server 2016 is build 14393. On a single server, running winver or systeminfo shows the version. In Active Directory, this PowerShell command lists domain-joined computers running it, from a machine with the Active Directory module installed:
Get-ADComputer -Filter 'OperatingSystem -like "*Server 2016*"' -Properties OperatingSystem | Select-Object Name, OperatingSystem
Then look for what Active Directory will not show you: servers that were never joined to the domain, virtual machines on hosts nobody remembers, and appliances running an embedded copy of Windows. Compare the result against your backup and monitoring lists. A server that is not being backed up is the one most likely to be forgotten, and the one that hurts most when it fails.
A 60-Day Countdown Plan
As of mid-November 2026, about two months remain until January 12, 2027. That is tight for a large estate and workable for a small one. A well-structured plan keeps the project on track:
Days 1 to 7: Build the inventory. List every Windows Server 2016 machine, including forgotten test and branch-office servers. Record the role, applications, owner, hardware age, and dependencies, and flag any SQL Server 2016 hosts.
Days 8 to 21: Triage and decide. Assign each server a path. Ask application vendors whether they support Windows Server 2025, check your ESU licensing eligibility, and identify the servers that will not make the deadline.
Days 22 to 40: Pilot and migrate the first wave. Start with a low-risk server to rehearse the process. Test restores, document the rollback plan, then move the first priority workloads. Move in phases instead of all at once, so each wave teaches you something before the next one.
Days 41 to 52: Move the rest and bridge the stragglers. Complete the second wave. For servers that cannot move, connect them to Azure Arc and enroll them in ESUs before January 12, with a written retirement date for each.
Days 53 to 60: Verify and freeze. Confirm backups, apply the January 12 updates, record what moved and what did not, and isolate any server that is staying behind. Update your asset inventory and risk documentation to match.
Still running Windows Server 2016?
Support ends January 12, 2027. Whether you are upgrading to Windows Server 2025, migrating to Azure, evaluating Extended Security Updates, or moving to hosted servers, Apps4Rent can help you modernize with minimal disruption.
If a Server Cannot Move in Time: Compensating Controls
Some servers will not make the deadline, whether because of a vendor dependency, a project freeze, or a budget cycle. An unsupported server is not automatically a breach, but it needs extra protection and a defined end date.
- Isolate it. Put the server on its own network segment, allow only the connections it needs, and keep it off the internet.
- Close remote access. Remove direct remote desktop exposure and put administration behind a gateway or VPN. Our guide to locking down remote desktop access lists practical fixes.
- Require MFA and limit administrators. Fewer admin accounts, individual logins, and multi-factor authentication shrink the attack surface.
- Run endpoint protection and monitoring. Keep security software current and review logs for unusual sign-ins.
- Test your backups. A backup you have never restored is a hope, not a control.
- Write down the plan. Record who owns the risk, the compensating controls, and the retirement date.
For the bigger picture on who secures what in any environment, see our guide to who secures what in the cloud.
Common Mistakes to Avoid
Treating “still boots” as “still safe.” The server will keep running, which is exactly why the deadline gets postponed. Security updates are what stop.
Assuming Azure means free ESUs. That was true for Windows Server 2012. It is not true for 2016, so budget accordingly.
Upgrading without a tested restore. An in-place upgrade is a change to a production server. Know you can go back before you begin.
Forgetting the layers around the server. SQL Server 2016 is already out of support, and client access licenses and application vendors need to be on the list too.
Waiting for the last two weeks. Migrations need pilots, testing, and rollback plans. Starting in the final month leaves no room for the surprises that every project has.
What Comes Next
With Windows Server 2016 extended support ending on January 12, 2027, organizations still running the platform should decide a path for each server now. Whether the answer is Windows Server 2025, Azure, ESUs as a temporary measure, or a hosted environment, proactive planning reduces risk, maintains compliance, and avoids a scramble. As a Microsoft Solutions Partner, Apps4Rent can help you assess your servers, plan the moves, and evaluate your options.
Frequently Asked Questions
-
When does Windows Server 2016 support end?
Extended support for Windows Server 2016 ends on January 12, 2027, which is a Patch Tuesday. Mainstream support already ended on January 11, 2022. After January 12, 2027, Microsoft stops releasing security updates and bug fixes unless a server is enrolled in paid Extended Security Updates.
-
What happens if I keep running Windows Server 2016 after January 12, 2027?
The server keeps working, but you stop receiving security patches and bug fixes. That increases exposure to vulnerabilities and ransomware, creates compliance and audit risk, erodes vendor compatibility, and raises maintenance and recovery costs over time.
-
Is there Extended Security Updates coverage for Windows Server 2016?
Yes. Microsoft announced Extended Security Updates for Windows Server 2016 on February 25, 2026. They provide Critical and Important security updates for up to three years after end of support, from January 12, 2027 through January 2030, and they are a paid offering.
-
How do Windows Server 2016 ESUs work?
They are delivered through Azure Arc. You connect each server by installing the Azure Connected Machine agent, then enroll eligible servers from the Azure portal or at scale with Azure Policy. Licensing eligibility rules apply, so confirm yours before you rely on them.
-
Are Windows Server 2016 ESUs free in Azure?
No. In the Windows Server 2012 cycle, servers in Azure received ESUs at no extra charge, but Microsoft states that free ESUs are not available for Windows Server 2016 in Azure. They are a paid offering there as well.
-
Can I upgrade Windows Server 2016 directly to Windows Server 2025?
Yes, in most cases. Windows Server 2016 supports in-place upgrades to 2019, 2022, and 2025. For servers that are not clustered, Windows Server 2025 can upgrade across up to four versions at once, while clustered servers upgrade one version at a time with a rolling upgrade.
-
Which upgrade path should I choose to replace Windows Server 2016: Windows Server 2022 or 2025?
Windows Server 2025 is the stronger choice for most organizations because its mainstream support runs until November 13, 2029 and extended support until November 14, 2034. Windows Server 2022 left mainstream support on October 13, 2026. Choose 2022 only if an application vendor has not certified 2025.
-
How do I plan a migration from Windows Server 2016 without disrupting business services?
Inventory your servers and map application dependencies, prioritize business-critical workloads, test compatibility, and migrate in phases with a pilot first. Include tested backups, a rollback plan, and validation steps for each wave, and align the choices with your security, compliance, and cost goals.
-
What are the common obstacles during a Windows Server 2016 migration, and how do I handle them?
The usual obstacles are legacy applications, older hardware, and tightly connected systems that need extra testing. Handle them by assessing the environment first, confirming vendor support for the new version, rehearsing on a copy, and working with an experienced migration provider such as Apps4Rent where you lack the time or skills.
-
Will my server stop working after January 12, 2027?
No. Windows Server 2016 keeps running after support ends. What stops is the flow of security updates, bug fixes, and standard Microsoft support, which is why running it unprotected becomes riskier every month.
-
What should I do with servers that cannot be migrated before the deadline?
Isolate them on their own network segment, remove direct internet and remote desktop exposure, require multi-factor authentication, keep endpoint protection and backups current, and write down a retirement date. For the few that need ongoing patches, enroll them in paid ESUs as a bridge.
-
Can I move a Windows Server 2016 file, QuickBooks, or remote desktop server to a hosted environment?
Often yes. A hosted provider can run the server or desktop and handle patching and backups, which removes the Windows Server version from your to-do list. Confirm application compatibility, license terms, and the provider’s exit terms before you move.
The deadline is fixed, but the path is yours to choose. Inventory your servers, pick a route for each, and start with the one that scares you least.