Windows Server 2012 R2 After October 13: Upgrade, Rebuild or Retire

The final year of Extended Security Updates (ESU) for Windows Server 2012 and 2012 R2 ends on October 13, 2026. Microsoft lists a three-year ESU period for these versions, ending on that date in Azure and on-premises, so after October 13 these servers stop receiving security updates wherever they run. This short post sets out the dates Microsoft publishes and the options it documents for what comes next.

The Dates Microsoft Publishes

From Microsoft's Windows Server 2012 R2 lifecycle page and its ESU overview for Windows Server 2012 and 2012 R2:

• Mainstream support ended October 9, 2018.
• Extended support ended October 10, 2023.
• ESU Year 1 ran from October 11, 2023 to October 8, 2024.
• ESU Year 2 ran from October 9, 2024 to October 14, 2025.
• ESU Year 3, the last year, runs from October 15, 2025 to October 13, 2026.

Microsoft lists the same ESU end date, October 13, 2026, for servers hosted in Azure (including the Azure Stack portfolio) and for servers not hosted in Azure. Microsoft's lifecycle dates are shown in Pacific Time.

What Changes After October 13

ESU delivered critical and important security updates only. When the ESU period ends, Microsoft states that it will stop providing updates and recommends moving to a more recent version of Windows Server. Moving a 2012 or 2012 R2 server to Azure doesn't extend its security updates past October 13, 2026.

The Options Microsoft Documents

• Upgrade in place. Starting with Windows Server 2025, non-clustered in-place upgrades support up to four versions at a time, so a Windows Server 2012 R2 server can be upgraded directly to Windows Server 2025. Windows Server 2012 (not R2) can't: Microsoft's table only supports upgrading it to 2012 R2 or 2016 first. Cluster rolling upgrades still move one version at a time, and not every role supports an in-place upgrade. See Microsoft's supported upgrade paths.
• Build new and migrate. Stand up servers on a supported version and move applications and data across. This is often the cleaner route for roles such as domain controllers and file servers.
• Move the workload to Azure on a supported version. Microsoft's ESU overview, linked above, also covers assessing what you run and deciding what to keep on-premises.

For any server that can't move right away, the practical step is to document it, limit what it can reach, and give it a retirement date.

What an Upgrade Looks Like in Practice

We recently helped a client move its Active Directory domain controllers to Windows Server 2025. You can read how the work was planned and sequenced in the domain controller upgrade story.

Next Step

If you still have Windows Server 2012 or 2012 R2 in your environment, start with a list of each server, its role and its upgrade path. Book a Windows Server review with one of our senior engineers and we'll help you map each server to an upgrade, rebuild or retirement plan.