On 12 January 2027, Microsoft ends extended support for Windows Server 2016. After that date there are no more security updates, no more bug fixes and no more technical assistance for an operating system that still runs file servers, line-of-business applications, SQL databases, print servers and domain controllers in thousands of UK offices. Windows Server 2016 end of support is not a dramatic switch-off — the servers will keep running on 13 January — but every vulnerability discovered from then on stays open for good, and that changes your security, insurance and compliance position overnight.
This guide explains exactly what end of support means, how to find every Windows Server 2016 machine in your estate, and how to choose between upgrading in place, rebuilding on Windows Server 2022 or 2025, moving to Azure, or replacing a server with a cloud service altogether. It covers realistic costs, a step-by-step migration timeline, the Cyber Essentials implications and the mistakes that cause most overruns. It is written for UK business owners, operations directors and IT leads at organisations with between one and fifty servers who need to make a decision in the next few weeks, not the next few years.
What does Windows Server 2016 end of support actually mean?
Microsoft supports each Windows Server release under its Fixed Lifecycle Policy: roughly five years of mainstream support (new features, design changes and security updates) followed by five years of extended support (security updates and paid support only). Windows Server 2016 left mainstream support on 11 January 2022 and has been on extended support ever since. When extended support ends on 12 January 2027, the monthly Patch Tuesday security updates stop for every edition — Essentials, Standard and Datacenter — unless the server is covered by a separate Extended Security Updates (ESU) arrangement.
The practical effect is that a Windows Server 2016 machine becomes a permanently unpatched system. Attackers know this: when an operating system goes out of support, newly found vulnerabilities in it are never fixed, and exploits for issues patched in newer versions can often be reverse-engineered and turned against the older one. The same thing happened with Windows Server 2008 in 2020 and Windows Server 2012 and 2012 R2 in October 2023. Many of the ransomware incidents that UK businesses report start with an internet-facing or poorly segmented server that stopped receiving updates months or years earlier.
End of support also has knock-on effects beyond security. Software vendors progressively stop certifying their applications on unsupported operating systems, so an accounting, practice-management or ERP upgrade may refuse to install. Hardware bought around 2016–2018 is often reaching the end of its own warranty at the same time. And because Windows Server 2016 shipped alongside SQL Server 2016 (extended support ended 14 July 2026) and Exchange Server 2016 (support ended 14 October 2025), many businesses find they have a cluster of related deadlines, not just one.
The good news is that this is a well-understood migration. The tools are mature, Azure has specific licensing provisions for older Windows Server workloads, and most small estates can be moved or upgraded in a matter of weeks once the decisions are made. The rest of this guide is about making those decisions in the right order. For the wider picture on running unsupported software, see our Cyber Essentials guide to unsupported and end-of-life software.
Run winver or check System Information on every server you think you have, but do not stop there. Windows Server 2016 often hides in places people forget: a virtual machine on a Hyper-V host, the backup server, the server that runs the door-entry or CCTV software, or a print server nobody has logged into for years.
Windows Server 2016 end of support in numbers
A handful of dates and facts drive every decision in this guide. They are worth putting in front of whoever signs off the budget.
The third card is the one that most often concentrates minds. Cyber Essentials requires that all in-scope software is licensed and supported, and that high and critical updates are applied within 14 days of release. A Windows Server 2016 machine that is in scope after 12 January 2027 — and not covered by ESUs — will cause a failed assessment unless it is removed from scope by being isolated on a separate network segment with no internet access.
How UK SMEs use their Windows Server 2016 machines
Before deciding how to replace a server, it helps to be clear about what it actually does. The chart below shows the roles we most commonly find on Windows Server 2016 machines during Cloudswitched server audits for UK organisations of 10–250 staff. Most servers carry more than one role, which is why the percentages add up to more than 100.
Each role has a different natural replacement. File shares can often move to SharePoint, Teams or Azure Files. Domain controllers may be replaced by Microsoft Entra ID with devices joined directly to the cloud, or kept as small virtual machines in Azure. Line-of-business applications and SQL databases usually need a like-for-like server, whether on new hardware or in Azure. Print servers can frequently be replaced by a cloud print service. Splitting the server into its roles is the single most useful step in planning, because it stops you re-creating a ten-year-old design just because that is what was there before.
What it costs to replace a Windows Server 2016 machine
Costs vary with the number of servers, the complexity of the applications and whether you need to buy new licences. The table below gives indicative UK costs for a single typical server carrying file shares plus one business application, excluding VAT. Azure running costs are for a modest virtual machine with managed disks and backup in the UK South region, and assume reserved-instance pricing where you commit for one or three years; pay-as-you-go is higher. Use these as a starting point for budgeting, not a quotation.
| Option | One-off project cost | Ongoing cost | Typical lead time |
|---|---|---|---|
| In-place upgrade to Windows Server 2022 or 2025 on existing hardware | £600–£1,800 labour, plus licences if not covered by Software Assurance | No change, but hardware age risk remains | 1–2 weeks |
| New on-premises server, fresh Windows Server 2025 build and migration | £4,500–£9,000 (hardware, licences, CALs, labour) | £40–£90 per month support and warranty, plus power | 3–6 weeks |
| Lift-and-shift to an Azure virtual machine (rehost) | £1,500–£4,000 labour | £150–£400 per month including storage and backup | 2–4 weeks |
| Rebuild in Azure on Windows Server 2025 (replatform) | £2,500–£6,000 labour | £150–£400 per month including storage and backup | 3–6 weeks |
| Retire the server: files to SharePoint, identity to Entra ID, print to cloud | £2,000–£7,000 labour depending on data volume | Often covered by existing Microsoft 365 licences | 4–8 weeks |
Two factors move these numbers more than anything else. The first is licensing: if your Windows Server licences are covered by Software Assurance, Azure Hybrid Benefit lets you apply them to Azure virtual machines and pay only for the compute, which can reduce the Windows element of the bill considerably. The second is application complexity: a single off-the-shelf application with a vendor who supports Windows Server 2022 is straightforward, while a bespoke application written by a developer who has since retired can take longer to test than everything else combined. Our guides to Azure pay-as-you-go versus reserved pricing and Azure VM sizing go deeper on the running costs.
Upgrade on-premises or migrate to Azure?
For most small businesses the real choice is between staying on-premises with a newer operating system and moving the workload to Azure. Both are sound. The comparison below sets out how they differ for a typical SME with one to five servers.
Stay on-premises
Upgrade or replace with Windows Server 2022 / 2025 locally
Move to Azure
Rehost or rebuild as Azure virtual machines and services
Azure has one specific advantage for older Windows Server workloads: Microsoft has historically provided Extended Security Updates at no additional charge for out-of-support Windows Server versions running in Azure, as it did for Windows Server 2008 and 2012. That can buy time for an application that genuinely cannot run on a newer operating system yet. Check Microsoft’s current ESU terms for Windows Server 2016 before building a plan around it, and treat ESUs as a bridge to a supported version, not a destination.
The deciding question is usually your connectivity. If your office has a reliable leased line or full-fibre connection with a backup link, Azure-hosted servers will feel local for most applications. If you are on a single business broadband line in an area with frequent outages, an on-premises server or a hybrid design may serve you better until connectivity improves.
How ready are you for Windows Server 2016 end of support?
Readiness is rarely about technology alone. The score cards below show the areas we assess when a business asks us to plan their move away from Windows Server 2016, and where most UK SMEs sit when they first get in touch.
“Usually missing” here does not mean the business is badly run; it means nobody has needed that information since the server was installed. The discovery work fills most of these gaps in a few days, and it is the part of the project that pays for itself, because it prevents surprises during the migration itself.
A realistic Windows Server 2016 migration timeline
For a small estate of one to five servers, a well-run migration takes six to ten weeks from first audit to switching off the old hardware. With January 2027 approaching, that means starting now leaves enough time for testing and a sensible cut-over over a quiet weekend.
The weeks that slip are almost always weeks two and six: waiting for vendors to reply, and waiting for busy colleagues to test. Booking both early is the most effective way to keep a project on track.
Migration benchmarks: what typically moves where
When small UK organisations plan their move away from Windows Server 2016, the destination for each role tends to follow a pattern. The figures below show the share of each workload type that ended up in each destination across recent Cloudswitched projects. They are a useful sense-check for your own plan rather than a target.
Destination of Windows Server 2016 workloads in Cloudswitched migrations
The pattern is clear: very few businesses rebuild exactly what they had. End of support is a natural moment to retire roles that the cloud now covers, and to keep servers only for the workloads that genuinely need them. If your business applications feed reporting, that is also a good time to review the underlying data — our guide to data quality for business reporting covers what to look for.
Windows Server 2016 end of support checklist — 12 essentials
Work through this list in order. Each item should have an owner and a date, and the answers belong in a short migration document you can show to your auditor, insurer or Cyber Essentials assessor.
- List every server, physical and virtual, with its operating system version and build number.
- Record each server’s roles: file, domain controller, DNS, DHCP, print, SQL, application, remote desktop, backup.
- Name a business owner for every application, and confirm with each vendor which operating system and SQL versions they support.
- Check licensing: Windows Server editions, client access licences, SQL licences and whether Software Assurance is in place for Azure Hybrid Benefit.
- Take a full, tested backup of every Windows Server 2016 machine before changing anything.
- Decide per role: retire, move to a cloud service, rehost in Azure, rebuild on a supported OS or upgrade in place.
- Check that your internet connection and failover link can support cloud-hosted workloads.
- Agree a cut-over window and a rollback plan with the business.
- Test every business-critical process on the new environment, including month-end and printing.
- Update Cyber Essentials scope and documentation to reflect the new servers.
- Decommission old servers properly: demote domain controllers, archive, wipe and certify disposal.
- Set calendar reminders for the next lifecycle dates, including Windows Server 2019 (January 2029).
Windows Server 2019 reaches end of extended support in January 2029. If you are upgrading in place, skip straight to Windows Server 2022 or 2025 so you do not repeat this exercise in two years’ time. Windows Server 2025 supports direct in-place upgrades from Windows Server 2016, but always test the upgrade on a copy first.
Decision gauge: is your estate ready to move?
We score migration readiness out of 100 across inventory, application support, licensing, backup, connectivity and budget. The gauge below shows the median score for UK SMEs at the start of a Windows Server 2016 project. A score below 50 means the first two weeks should focus on discovery; above 70 means you can go straight to design and build.
The weakest areas are nearly always application vendor confirmation and dependency mapping. These are also the cheapest to fix: a few emails and a morning with a monitoring tool. The strongest area is usually Active Directory health, which tends to be stable even when everything else is undocumented.
Common Windows Server 2016 migration mistakes
The same handful of problems cause most delays and overspends. Knowing them in advance makes them easy to avoid.
- Leaving it until December. Vendors, IT providers and hardware suppliers all get busier as deadlines approach, and the Christmas period removes two weeks from the calendar. Start early enough to cut over before the holidays.
- Rebuilding the old design. Moving a 2016 server to a 2025 server with exactly the same roles misses the chance to retire file shares, print servers or domain controllers that the cloud now covers.
- Not asking the application vendor. Many line-of-business applications have specific supported versions. Installing on an unsupported combination can leave you without help when something breaks.
- Forgetting SQL Server. SQL Server 2016 is already out of extended support. Upgrading Windows while leaving SQL on 2016 solves only half the problem.
- Underestimating the internet connection. A single broadband line becomes a single point of failure for every cloud-hosted server. Plan a backup connection; our guide to static IP addresses and business broadband covers the connectivity side.
- Removing domain controllers badly. Simply switching off an old domain controller leaves stale records in Active Directory. Demote it properly and move any FSMO roles first.
- No rollback plan. Keep the old server available but powered off for at least two weeks after cut-over, so you can recover quickly if a missed dependency appears.
- Ignoring Azure costs after go-live. Virtual machines left oversized, or running out of hours when nobody needs them, are the most common source of Azure bill surprises. Set budgets and alerts from day one.
If a Windows Server 2016 machine must stay running after 12 January 2027 — for example, because it controls specialist equipment that cannot be upgraded — isolate it. Put it on its own network segment with no internet access and strictly limited inbound connections, document why, and plan its replacement. An unsupported server on your main network is both a Cyber Essentials failure and a real attack path.
Mini case study: a 60-person Bristol distributor moves off Windows Server 2016
A Bristol-based wholesale distributor with 60 staff across an office and a warehouse ran its business on two physical Windows Server 2016 machines bought in 2017. One carried Active Directory, file shares and printing; the other ran a stock-control system on SQL Server 2016. Both servers were out of warranty, and the comms room shared a cupboard with the office boiler.
Discovery took four days and found three things nobody had written down: a third virtual machine running the warehouse label printing software, a scheduled task that exported orders to a courier every night, and a mapped drive used by the finance team for bank file uploads. The stock-control vendor confirmed support for Windows Server 2022 and SQL Server 2022, and offered a hosted version which the business decided against because of the cost of customised reports.
The final design retired the file and print server entirely — shared folders moved to SharePoint and Teams, printing to a cloud print service, and laptops were joined directly to Entra ID. The stock-control system was rebuilt on a Windows Server 2022 virtual machine in Azure UK South with SQL Server 2022, reached over a site-to-site VPN from the warehouse, and protected by Azure Backup. A second connection from a different provider was added at the warehouse. The project took nine weeks and cut over on a Saturday with no lost trading time.
“We expected to replace two servers. In the end we replaced one and simply didn’t need the other. The thing I hadn’t appreciated was how much we’d have missed without the discovery work — the courier export alone would have stopped our deliveries on the Monday.” — Finance and Operations Director, wholesale distributor, Bristol
Running costs for the Azure server, backup and VPN are now a predictable monthly line, and the business no longer has hardware to replace in 2027 or beyond. When the directors later reviewed their IT roadmap with a virtual CIO — an approach we describe in the first 90 days with a virtual CIO — the server question was already off the list.
Windows Server 2016 end of support at a glance
| Topic | Key fact or recommendation |
|---|---|
| End of extended support | 12 January 2027 for all Windows Server 2016 editions |
| Mainstream support ended | 11 January 2022 |
| Related deadlines | SQL Server 2016 ended 14 July 2026; Exchange Server 2016 ended 14 October 2025 |
| Next deadline to watch | Windows Server 2019 in January 2029 |
| Recommended targets | Windows Server 2022 or 2025, or a cloud service that removes the server altogether |
| In-place upgrade | Supported from 2016 to 2019, 2022 and 2025; test on a copy first |
| Azure option | Rehost or rebuild as Azure VMs; Azure Hybrid Benefit reuses licences with Software Assurance |
| Extended Security Updates | A temporary bridge only; check Microsoft’s current terms for 2016, including Azure provisions |
| Cyber Essentials | Unsupported in-scope software fails; isolate or remove legacy servers |
| Typical small-estate timeline | 6–10 weeks from discovery to decommission |
| Typical Azure running cost | £150–£400 per month for a modest server with storage and backup |
| Biggest planning step | Split every server into its roles and decide each one separately |
| Biggest risk | Undocumented dependencies such as scheduled tasks and mapped drives |
| Decommissioning | Demote domain controllers properly, archive, wipe disks and certify disposal |
How Cloudswitched helps you move off Windows Server 2016
Cloudswitched plans and delivers Windows Server migrations for UK businesses, from single-server offices to multi-site estates. We carry out the discovery and dependency mapping, check application vendor support, design either an Azure or an on-premises target, handle the build, migration and cut-over, and look after the new environment afterwards with monitoring, patching, backup and cost management. We will tell you plainly when a server is better retired than replaced.
Plan your move before 12 January 2027
Our Azure team can audit your Windows Server 2016 estate and set out the options, costs and timeline for your business.
Talk to us about Azure Cloud ServersFrequently Asked Questions
When does Windows Server 2016 support end?
Extended support for Windows Server 2016 ends on 12 January 2027. Mainstream support already ended on 11 January 2022. After the extended support end date, Microsoft stops releasing security updates, non-security fixes and free support for all editions of Windows Server 2016, including Essentials, Standard and Datacenter. Servers will continue to start and run normally, but any vulnerability discovered after that date will not be fixed unless the server is covered by a separate Extended Security Updates arrangement.
Will my Windows Server 2016 machine stop working after January 2027?
No. The server will keep running, and your applications will keep working as they do today. What changes is that it will no longer receive security updates. Over time that makes it an easier target for attackers, increases the chance that new software will refuse to install on it, and can affect your Cyber Essentials certification and cyber insurance. The risk grows every month the server remains in use, which is why planning a replacement before the deadline is sensible.
Can I upgrade Windows Server 2016 directly to Windows Server 2025?
Yes. Windows Server 2025 supports in-place upgrades from Windows Server 2016, as well as from 2019 and 2022. You will need valid licences for the new version and should check that your applications and hardware are supported. Always take a full backup first and, ideally, test the upgrade on a copy of the server. For servers with complex roles or years of accumulated changes, a clean build and migration is often more reliable than an in-place upgrade.
Is it cheaper to move Windows Server 2016 to Azure or buy a new server?
It depends on your timescale and workload. A new on-premises server costs more up front — typically £4,500–£9,000 including hardware, licences and labour — but has low monthly costs. Azure has lower project costs and no hardware, but an ongoing monthly charge, typically £150–£400 for a modest server with storage and backup. Over five years the totals are often similar; the difference is usually decided by resilience, remote working and whether you want to replace hardware again in future.
What are Extended Security Updates for Windows Server 2016?
Extended Security Updates are a paid programme Microsoft has offered for previous Windows Server versions, providing critical and important security patches for a limited period after support ends. Microsoft has also historically made them available at no extra charge for those versions running in Azure. ESUs are intended as a short-term bridge while you migrate, not a long-term plan. Check Microsoft’s current published terms for Windows Server 2016 to confirm availability, pricing and eligibility before relying on them.
Does Windows Server 2016 end of support affect Cyber Essentials?
Yes. Cyber Essentials requires all in-scope software to be supported by its vendor and to receive security updates, with high and critical updates applied within 14 days. A Windows Server 2016 machine that is in scope after 12 January 2027 without ESU coverage will cause a failed assessment. You can remove a legacy server from scope by isolating it on a separate network segment with no internet access, but the better long-term answer is to replace or retire it.
How long does a Windows Server 2016 migration take?
For a small estate of one to five servers, six to ten weeks from discovery to decommissioning is typical. That includes a week of discovery, time for application vendor checks, design, build, user testing, a weekend cut-over, a week of extra support and the final removal of old hardware. The longest delays usually come from waiting for application vendors to confirm support and from scheduling testing with busy staff, so start both early.
Do I still need a domain controller if I move to the cloud?
Not always. Many small businesses can join laptops directly to Microsoft Entra ID and manage them with Intune, removing the need for an on-premises domain controller. However, if you still run applications or file servers that rely on traditional Active Directory authentication, you may need a domain controller, either as a small Azure virtual machine or through Microsoft Entra Domain Services. The decision depends on what your applications require, which is why discovery comes first.
What is Azure Hybrid Benefit?
Azure Hybrid Benefit lets you use existing Windows Server and SQL Server licences that are covered by Software Assurance, or qualifying subscription licences, when you run those workloads in Azure. Instead of paying for the Windows or SQL licence as part of the virtual machine price, you pay only for the underlying compute. For businesses with existing licences this can make a noticeable difference to monthly Azure costs, so check your licensing position early in the project.
What should we do with old servers once they are replaced?
Keep them powered off but available for a couple of weeks as a fallback. Then demote any domain controllers properly and move their roles, take a final archive backup if needed for record-keeping, securely wipe or destroy the disks, and use a disposal company that provides a certificate of destruction for UK GDPR purposes. Finally, update your asset register and Cyber Essentials documentation so they reflect the new environment.
Related reading
These recent Cloudswitched guides cover topics that often come up alongside a Windows Server migration.
Supported, secure servers without the hardware headache
Cloudswitched designs, migrates and manages Azure cloud servers for UK businesses, with monitoring, patching, backup and cost control included.
Explore Azure Cloud Servers









