Windows Server 2025

Standard suits physical or lightly virtualised servers and grants two OSE / Hyper-V container rights per fully licensed host. Datacenter is the right choice for any host running more than a handful of virtual machines because it unlocks unlimited OSEs on the licensed hardware, plus Storage Replica without size caps, Storage Spaces Direct, Software Defined Networking, shielded VMs and the new ReFS deduplication-and-compression feature. Essentials targets very small businesses with up to 25 users and 50 devices and is sold per server (no CALs), but it is a one-server-per-domain SKU and cannot host the file or print roles for a larger network without giving up its simplified licensing. Azure Edition is licensed differently — see below — and is only available through Azure Stack HCI or Azure VMs.

Both Standard and Datacenter are licensed per physical core on the host, sold in 2-core packs, with a minimum of 8 cores per processor and 16 cores per server. Every physical core on the box must be licensed even if you only use part of the hardware for Windows workloads. Hyperthreaded logical cores do not change the count: a 32-thread, 16-physical-core CPU still needs 16 core licences. If you add a second processor later, you must true up. For VMs on someone else's hardware (a hosting provider running Windows Server for you), the SPLA programme handles the per-core compliance and you do not buy core licences directly.

Every user or device that authenticates against a Windows Server instance needs a Windows Server CAL. User CALs are economical when staff use multiple devices; Device CALs win when many users share the same workstation (shift work, kiosks, training rooms). The most common audit finding is the missing Remote Desktop Services CAL: RDS sessions require both a base Windows Server CAL and a separate RDS CAL per user or device. Service-to-service authentication (machine accounts, application pool identities, SQL Server service accounts) does not require a CAL, but any named human or device with credentials on the network does — including contractors, auditors and read-only monitoring accounts.

Standard's two OSE rights are stackable: license the same physical hardware twice (i.e. pay for the cores twice) and you receive four VMs. Past roughly six to eight VMs per host the maths almost always favours Datacenter; the exact crossover depends on core count and discounting, but a useful rule of thumb is 'if you might ever exceed 6 VMs, just buy Datacenter from day one'. Containers in Hyper-V isolation count as OSEs; process-isolated Windows containers do not consume an OSE, which is why container-heavy hosts often stay on Standard even with high density.

One of the headline 2025 changes: hotpatching — installing security updates without rebooting — is available for any Windows Server 2025 instance attached to Azure Arc, not just for Azure-hosted machines, via a per-core monthly subscription. For organisations that previously deferred patching to keep uptime, this materially shortens vulnerability windows. Azure Arc itself extends the Windows Admin Center experience to manage on-prem, edge and multi-cloud servers from a single Azure pane, with policy, update, monitor and inventory tooling included. Active Software Assurance gives Windows Server licences the Azure Hybrid Benefit: you can run the same workload on Azure VMs without paying the Windows licence a second time, saving roughly 40% versus pay-as-you-go pricing — significant on long-running production VMs.

ReFS now supports block cloning, which makes file-copy operations near-instant for tools that use it (Hyper-V VHDX cloning, Veeam, modern backup engines). Storage Replica drops its size cap on Standard. SMB over QUIC is enabled by default, replacing the need for a VPN for SMB traffic from remote endpoints. Credential Guard is on by default in new installs; Windows Defender Application Control is integrated into the Windows Admin Center workflow; BitLocker now protects Cluster Shared Volumes natively. Active Directory has its first schema bump since 2016, introducing larger database page sizes (32 KB) and 64-bit clock values to support modern hardware and very large directories.

Server 2019 reaches end of mainstream support in January 2024 and extended support in January 2029. Server 2022 carries mainstream support to 2026 and extended support to 2031. Server 2025 is the right target for any new deployment or refresh. In-place upgrades are supported from 2019 and 2022 directly to 2025, but for production estates a side-by-side migration (new 2025 cluster, gradual workload move) is the safer pattern, particularly for domain controllers, Exchange and SQL Server hosts.