Windows Server 2025 Licensing: What Changed, What Did Not, and What Azure Arc Adds

The licensing model from Windows Server 2016, 2019 and 2022 still applies. You license every physical core, with a minimum of 8 per processor and 16 per server, in two-core packs. Standard covers two virtual machines per full set of licenses and can be stacked; Datacenter covers unlimited VMs on the licensed host. Both editions need Client Access Licenses for every user or device that connects, unless the server is on pay-as-you-go. Our Windows Server licensing calculator applies those rules and prices Standard against Datacenter at Microsoft's list price.

Three edition details from Microsoft's 2025 comparison matter. Automatic Virtual Machine Activation, which activates guests from the host without product keys, requires a Datacenter host. 2025 Standard adds live migration between standalone nodes for planned downtime, but clustering for unplanned downtime needs Datacenter. And an in-place upgrade keeps the edition; you can move from Standard to Datacenter during the upgrade, never down. A third edition, Datacenter: Azure Edition, is built for VMs on Azure and Azure Local and is not a replacement for either on your own hardware.

Windows Server 2025 introduces a subscription alternative to the perpetual license: connect the server to Azure Arc, enable pay-as-you-go, and the operating system is licensed by usage and billed monthly to your Azure subscription. Microsoft's rules differ from perpetual licensing in ways that matter:

• The price is the same for Standard and Datacenter, on the pricing and model of Windows Server on Azure applied to machines outside Azure; it is not supported on Azure VMs.
• No CALs are required for standard functionality. RDS CALs are still required.
• The license covers only the machine it is enabled on, with no rights for VMs on that host; each VM needs its own license.
• The server must be Windows Server 2025 Standard or Datacenter, Arc-connected with the Connected Machine agent at version 1.47 or later, not already activated with an OEM, retail or volume license key, and online.
• You can enable it during Setup or afterwards from the Azure portal or PowerShell; the first seven days are a trial at no charge.
• Billing continues if you shut the machine down without disabling pay-as-you-go first. After disabling it, the machine needs a product key.

The usage rights sit in the Microsoft Product Terms, and the meter is yours: an Azure charge on your subscription, not a partner invoice. It fits a server you expect to retire, a project host, or a single box where sixteen cores of Datacenter plus CALs was always awkward. It does not fit a dense virtualization host, because the per-VM rule removes the Datacenter advantage.

Arc also brings management benefits to servers with active Software Assurance or Windows Server subscription licenses: Windows Admin Center in the Azure portal, Remote Support, Best Practices Assessment and Azure Site Recovery configuration. Attached services such as Update Manager or Defender for Servers are metered to your subscription; our Azure Arc Hybrid Server Management implementation onboards an estate with those costs acknowledged up front.

Hotpatching installs Windows security updates into the memory of running processes without a restart. It arrived on Azure with Datacenter: Azure Edition and came to your own hardware through Azure Arc; on 19 May 2026 Microsoft removed the subscription charge for Arc-connected 2025 Standard and Datacenter machines, and its documentation now states the feature is available at no extra cost.

The cadence, from Microsoft's Hotpatch article: a baseline cumulative update every three months, which requires a restart, then two months of hotpatch releases that do not — four planned restarts a year instead of twelve. Two caveats: an unplanned baseline, such as a zero-day fix that cannot ship as a hotpatch, replaces a hotpatch month and requires a restart; and hotpatch covers Windows security updates only, so nonsecurity updates, .NET, drivers and firmware still need a normal cycle.

Prerequisites: Windows Server 2025 Standard or Datacenter at build 26100.1742 or later; UEFI with Secure Boot and Virtualization-based Security running, which enabling hotpatch in the portal checks for; the Connected Machine agent and an Azure subscription. Datacenter: Azure Edition VMs have it on by default. The gain is fewer maintenance windows on the servers that hurt most to restart, orchestrated through Azure Update Manager, Group Policy or your existing patch tool.

A Client Access License is valid for its own Windows Server version and every earlier one, not later ones. Add a single 2025 host to an estate licensed with 2019 or 2022 CALs and every user or device that touches it needs a 2025 CAL.

Remote Desktop Services makes the rule visible because it is enforced: Microsoft's RDS licensing table shows a 2025 RDS CAL connecting to 2025 and earlier session hosts, and a 2022 RDS CAL unable to connect to a 2025 host. The license server has the mirror rule — 2025 RDS CALs install only on a license server running 2025 — so it is the first server to upgrade, not the last.

Two ways to make the CAL line smaller are legitimate: users whose Microsoft 365, Office 365 or EMS subscriptions carry CAL equivalency under the Product Terms do not need a separate Windows Server CAL (the plan-by-plan mapping is a Product Terms check, not an assumption), and pay-as-you-go removes the Windows Server CAL but not the RDS CAL. The Client Access License Calculator counts both.

Windows Server 2025 changed the in-place upgrade rule: non-clustered systems can jump up to four versions at once, so a 2012 R2, 2016, 2019 or 2022 server can upgrade directly to 2025 from installation media. Clusters are the exception: a rolling upgrade advances one version at a time, so a 2016 Hyper-V cluster goes through 2019 and 2022 first or is rebuilt alongside. Domain controllers are better replaced than upgraded. Our Windows Server 2016 to 2025 Upgrade Service handles both patterns, and the Hyper-V cluster upgrade is scoped separately.

Hardware requirements are modest but real: a 1.4 GHz 64-bit processor with SSE4.2 and POPCNT support; a CPU that fails the check is a refresh conversation, not a licensing one.

The calendar, from our deadlines register: on 13 October 2026 Extended Security Updates for Windows Server 2012 R2 end and Windows Server 2022 leaves mainstream support (extended support runs to 14 October 2031); on 12 January 2027 Windows Server 2016 reaches end of support. Windows Server 2025 follows the Long-Term Servicing Channel, five years of mainstream support and five of extended from release; check Microsoft Lifecycle for the exact dates.

Is pay-as-you-go cheaper than buying 2025 licenses?

For a server you expect to retire within a couple of years, it can be; for a host running five years with several VMs, perpetual Datacenter usually is. Run both for your own core counts.

Does hotpatching cost anything now?

No additional Microsoft charge for Arc-connected 2025 Standard and Datacenter since May 2026. The prerequisites cost effort, and any Azure services you attach to the Arc machine are metered to your subscription.

Do I still need CALs for Windows Server 2025?

Yes, on perpetual licenses, and they must be 2025 CALs. Pay-as-you-go waives the Windows Server CAL; RDS CALs remain required under either model.

Can I upgrade from 2016 directly to 2025?

Yes for a non-clustered server, from installation media. Clusters roll one version at a time, and domain controllers should be replaced rather than upgraded.

Standard or Datacenter for a 2025 host?

Count the VMs. Standard covers two per license set and stacks; Datacenter covers unlimited VMs and is required for Automatic Virtual Machine Activation and for clustering against unplanned downtime.

• Microsoft Learn: What's new in Windows Server 2025; Configure Windows Server Pay-as-you-go with Azure Arc; Hotpatch for Windows Server; Enable Hotpatch for Azure Arc-enabled servers; Comparison of Windows Server editions; Plan your Windows Server upgrade; Hardware requirements for Windows Server; Windows Server servicing channels; Automatic Virtual Machine Activation; License Remote Desktop Services with Client Access Licenses (CALs); Extended Security Updates for Windows Server overview
• IT Partner deadlines register