Windows Server 2016 End of Support: January 13, 2027
- Read time: 5 mins
Windows Server 2016 reaches end of support Jan. 13, 2027. That date coincides with January’s Patch Tuesday and it brings the last security update Microsoft ships for Windows Server 2016.
Although your servers will keep running after that date, they will no longer receive Microsoft’s standard security updates after that date unless they’re covered by an eligible Extended Security Updates option.
Windows Server 2016 End of Support Key Dates
| Milestone | Date |
|---|---|
| Windows Server 2016 mainstream support ends | Jan. 11, 2022 |
| SQL Server 2016 extended support ends | July 14, 2026 |
| Windows Server 2012 and 2012 R2 ESUs end | Oct. 13, 2026 |
| Windows Server 2022 mainstream support ends | Oct. 13, 2026 |
| Windows Server 2016 extended support ends (last free patch) | Jan. 12, 2027 |
| First Patch Tuesday with no free Windows Server 2016 updates | Feb. 9, 2027 |
| Windows Server 2016 ESUs end | January 2030 |
What Happens When Windows Server 2016 Support Ends?
Microsoft stops releasing free security updates for Windows Server 2016 after Jan. 12, 2027. Technical support for the operating system ends the same day and applies to on-premises servers, hosted servers, and Azure VMs alike.
| What Changes | Through Jan. 12, 2027 | After Jan. 12, 2027 |
|---|---|---|
| Security patches | Included at no cost | Paid ESUs only |
| Microsoft technical support | Available | Ended |
| ESUs for Azure VMs | Not needed yet | Paid, same list price as on-premises |
| Path to stay secure | Plan your move | Upgrade, migrate, buy ESUs or isolate |
Your Servers Keep Running
Windows Server 2016 will boot on Jan. 13 like any other day, your apps will load and your users won’t notice a thing. Everything will be just peachy.
Meanwhile, attackers study the patches Microsoft ships each month for Windows Server 2019, 2022 and 2025. They find the flaws behind those fixes and test them against 2016 servers that will never get the same fix. Unpatched servers turn into easy targets fast.
Domain Controllers Deserve Special Attention
Windows Server 2016 may still support critical roles such as Active Directory Domain Services, file services, and Remote Desktop Services. Domain controllers are particularly sensitive because they play a central role in authentication and authorization across the environment. Leaving those systems on an unsupported operating system introduces unnecessary identity and security risk.
Compliance Gets Harder to Defend
Unsupported operating systems can make compliance more difficult. Frameworks and security standards commonly require organizations to address known vulnerabilities, maintain appropriate security controls and manage technology risk. Continuing to run an operating system without standard security updates can create findings that require remediation or compensating controls.
Vendor Support Begins to Disappear
Software and security vendors follow Microsoft’s lead. Expect backup agents, endpoint tools and line-of-business apps to drop Windows Server 2016 from their supported lists. Some of the stack is already gone. SQL Server 2016 left extended support July 14, 2026, and Exchange Server 2016 left in October 2025.
Can You Buy Extended Security Updates for Windows Server 2016?
Yes. Microsoft announced ESUs for Windows Server 2016 in February 2026. They deliver Critical and Important security patches for up to three years, through January 2030. They do not include new features, non-security fixes or technical support for the operating system.
You can buy them two ways:
- Azure Arc. Connect your servers to Azure Arc and pay monthly through your Azure subscription. Enrollment is open now and billing starts Jan. 13, 2027. Minimums are 16 physical cores per server or eight virtual cores per VM.
- Volume licensing. Buy coverage one year at a time through commercial licensing.
Eligibility and licensing requirements vary by purchasing method. For ESUs enabled through Azure Arc, Microsoft requires customers to attest to qualifying Software Assurance or SPLA coverage. HBS can review your existing Windows Server licensing and determine the appropriate ESU path.
ESU cost depends on edition, core count, licensing model and applicable discounts. HBS can model the cost of ESUs against migration or upgrade options.
You should treat ESUs as a bridge. Three years of payments still leaves you facing the same migration in 2030, but on hardware that is three years older.
Your Options as Windows Server 2016 Support Ends
You have four paths. There isn’t one right destination for every Windows Server 2016 workload. HBS evaluates the application, infrastructure, dependencies, security requirements and economics of each system, then builds a modernization roadmap. For some workloads, that means Azure. For others, Windows Server 2025 on-premises or a hybrid architecture may make more sense.
Option 1: Migrate to Azure
Azure puts your workloads on a supported, patched platform without a hardware refresh. You skip procurement and rack time. You pay for the capacity you use. Your IT team gets out of the hardware maintenance business.
- A modern OS from day one. For eligible nonclustered systems, Windows Server 2025 supports a direct in-place upgrade from Windows Server 2016. Compatibility, server roles, applications, hardware and licensing should still be validated before choosing an in-place upgrade.
- Lower costs on licenses you already own. Azure Hybrid Benefit applies existing Windows Server and SQL Server licenses with active Software Assurance to Azure.
- Managed databases. Azure SQL Managed Instance handles database patching and upgrades for you.
- Cloud-native security options. Azure workloads can integrate with services such as Microsoft Defender for Cloud for security posture management and workload protection.
- Help paying for the move. Microsoft funding programs can offset assessment and migration costs for qualifying projects.
Option 2: Upgrade On-Premises to Windows Server 2025
Staying on-premises fits workloads with strict latency, data residency or hardware needs. Pick your target version carefully. Windows Server 2022 left mainstream support Oct. 13, 2026. Windows Server 2019 loses extended support Jan. 9, 2029. Windows Server 2025 gets security updates through Nov. 14, 2034, which makes it your longest runway.
Standalone 2016 servers upgrade in place to 2025 with installation media. Failover clusters move one version at a time, so a 2016 cluster takes three passes to reach 2025. For domain controllers, Microsoft recommends deploying new Windows Server 2025 systems, promoting them to domain controllers and demoting the older servers rather than performing an in-place OS upgrade.
Budget for compatible hardware and the Windows Server 2025 server and CAL licensing your environment requires. Customers with active licensing agreements or Software Assurance should review existing entitlements before purchasing.
Option 3: Buy ESUs as a Short Bridge
ESUs fit a short list of servers that can’t move by Jan. 12. A vendor app still waiting on certification. A cluster partway through its upgrade passes.
Enroll those servers through Azure Arc and give each one a retirement date. Arc bills monthly, so the charges stop when the server is gone.
Option 4: Isolate or Retire What Can’t Move Yet
Some servers have no upgrade path at all. A legacy app built by a vendor that closed its doors years ago. Contain those systems while you plan their exit.
Pull them off the internet, segment them from the rest of your network, and limit who can sign in. Also, consider monitoring them around the clock with a service like HBS Managed XDR. Then set a hard retirement date and hold to it.
While you’re at it, look for servers nobody uses. Decommission them. Each one you retire is one fewer to migrate or pay ESUs on.
What to Do Before Jan. 12, 2027
- Inventory every 2016 server by role. Domain controller, file server, SQL Server host, Remote Desktop Services or line-of-business app.
- Check what runs on top. Flag SQL Server 2016 instances and apps whose vendors haven’t certified Windows Server 2025.
- Pick a path for each server. Azure, on-premises upgrade, ESU bridge or isolation.
- Start with the easy wins. Move file and print servers first to prove your backup, rollback and licensing steps.
- Book vendor time now. Domain controllers, clusters and vendor apps take the longest, and December calendars fill fast.
How HBS Can Help
HBS moves your 2016 workloads to Azure or Windows Server 2025 with a plan built for your apps, compliance needs and budget.
- Azure Migration Assessment. We map every 2016 server, its dependencies and its real Azure cost so you move with clear numbers. Learn about the assessment.
- End-to-end migration. Our engineers handle the move and the Windows Server 2025 upgrade with minimal downtime. Explore Cloud Solutions.
- Licensing and ESU guidance. We apply Azure Hybrid Benefit where it fits, price ESUs for the servers that need a bridge and help you pursue Microsoft funding for qualifying projects. See Microsoft Licensing Management.
- Security after the move. Managed XDR and Managed One keep your new environment monitored and patched.
Find the right future for your Windows Server 2016 workloads.
Related Content
Windows 2012 R2 End of Life: What Happens When ESUs End
The last Windows Server 2012 R2 patch ships Oct. 13, 2026. Find out what happens to your servers and how an Azure migration gets you secure fast.
Azure Migrate & Modernize Assessment
See how HBS can help you migrate and modernize with Azure.
Navigating and Mitigating End of Life Software Risks
Using end of life (EOL) software increases your exposure to cyberattacks, data breaches, and compliance fines. Learn the risks, hidden costs, and best practices to manage outdated systems.