Windows Server 2016 Support Ends Jan 2027: Small Office Options

What ends on 12 January 2027

Windows Server 2016 follows Microsoft's Fixed Lifecycle Policy. The Windows Server 2016 lifecycle page lists mainstream support ending in January 2022 and extended support ending in January 2027, for the Datacenter, Essentials, MultiPoint Premium and Standard editions. Microsoft's February 2026 announcement gives the date as 12 January 2027.

The practical risk is new vulnerabilities. Once updates stop, any flaw found later stays open on that server for good. If it holds client files, accounting data or staff logins, that matters for PDPA as well as for day-to-day security.

First, find out what the old server still does

Many office servers were set up years ago and nobody remembers every job they do. Before you choose an option, list each role. Missing one is how an office ends up with printers that stop working or an accounting program that cannot find its database on Monday morning.

Check the edition first: open Settings or run winver on the server. It decides whether paid ESU is even possible. Also ask your software vendors whether their programs are supported on Windows Server 2022 or 2025, or have a cloud version, because that often decides the route for you.

Your three options: cloud, new server or paid ESU

For a small office the choice usually comes down to these three. Microsoft's own guidance recommends upgrading to a current Windows Server version and treats ESU as a last-resort bridge.

Microsoft's upgrade path table shows Windows Server 2016 can be upgraded in place to 2019, 2022 or 2025. On a server that has been running for eight or more years, a clean install on new hardware with data moved across is usually less risky than upgrading the old box in place, but it takes more planning.

How Windows Server 2016 ESU works and who can buy it

Microsoft's Azure Arc ESU documentation says Windows Server 2016 ESUs provide critical and important security updates for up to three years, through 2030. You can configure them in the Azure portal from 3 August 2026, and billing begins on 13 January 2027. The server needs the Azure Connected Machine agent, version 1.62 or higher.

There are licensing conditions. The same page says you need Software Assurance through a Volume Licensing programme (for example an Enterprise Agreement or Open Value), unless the servers are licensed through SPLA or a Server Subscription. Many small offices bought a server with an OEM licence and no Software Assurance, so check this before you count on ESU.

Microsoft's ESU FAQ also says ESUs are free for VMs running in Azure. Moving an old server into an Azure VM can make sense for a line-of-business application, but you then pay for the VM every month, so compare that with replacing the application. Confirm current pricing in the Azure portal before deciding.

Back up before you change anything

Whatever you choose, the first step is the same: a full, tested backup of the server. Migrations and in-place upgrades are where data gets lost, usually because a folder or database nobody listed was left behind.

1. 1

   Take a full image backup of the server

   Use a tool that can restore the whole machine, not just files. Store a copy off the server, on a NAS or in cloud storage.

2. 2

   Export application data separately

   Ask each software vendor how to export or back up its database, and do that as well as the image.

3. 3

   Test a restore

   Restore a few folders and, if you can, the application database to another machine. A backup you have never restored is a guess.

4. 4

   Record shares, permissions and settings

   Write down share names, who has access, printer queues, scan destinations and any scheduled tasks.

5. 5

   Plan the cutover for a quiet day

   Pick a weekend or public holiday, tell staff in advance, and keep the old server switched off but intact for a few weeks after the move.

If you are deciding where backups should live afterwards, our comparison of Synology NAS vs cloud backup covers cost and ransomware protection for small offices.

Suggested timeline from now to January 2027

Twelve weeks is enough for a small office if you start now. Leaving it to December means doing the work over the year-end holidays, when vendors and staff are hard to reach.

If most of the server is shared folders, our file server to cloud migration guide walks through moving them to SharePoint or Google Drive. Offices that also still have Windows 10 PCs can read our Windows 10 ESU options at the same time, since both projects touch the same users.

Do it yourself or get help?

If your server only shares a few folders and you are comfortable with Microsoft 365 or Google Workspace admin, moving files to the cloud is a realistic DIY project. Domain logins, server-based accounting software, remote access and ESU licensing are where small offices usually need help.

Our Software & Server Protection Setup (S$590) covers hardening and patching a supported server or planning the move off an old one, and Backup & Ransomware Recovery (S$290) sets up tested backups before the change. IT Sorted is a Singapore-based team of developers with over 10 years of experience. You pay upfront, send the details in writing through the site chat or contact form, and follow progress on your order page.