Microsoft · Software-defined
Windows Server 2025 Datacenter with Hyper-V and Storage Spaces Direct
Windows Server 2025 Datacenter includes Hyper-V, Storage Spaces Direct (2 to 16 servers per cluster, up to 4 PB per pool), Storage Replica, SDN Network Controller and Failover Clustering. It is licensed per physical core (16-core packs, perpetual with optional Software Assurance) or pay-as-you-go through Azure Arc, and runs on any server certified in the Windows Server Catalog. It suits organisations with Windows skills that want HCI without a cloud dependency, including stretched and fully offline clusters.
- Hypervisor
- Hyper-V
- Cluster size
- 2–16 nodes
- Two-node
- Yes · witness
- Management
- Windows Admin Center, Failover Cluster Manager and PowerShell per cluster; optional System Center VMM or Azure Arc for fleets
- Data reviewed
- 2026-09-19
Strengths
- No cloud dependency: perpetual licences, fully offline operation and a 10-year fixed lifecycle.
- Datacenter licensing covers unlimited Windows Server VMs on a licensed host.
- Synchronous Storage Replica stretch clusters and new S2D campus clusters for site and rack resilience.
- Full SDN stack (Network Controller, SLB, gateways, NSGs) included in Datacenter.
- Runs on any Windows Server-certified hardware, and any major backup product supports Hyper-V.
Considerations
- S2D needs Datacenter edition; Standard cannot run it.
- Do-it-yourself integration: cluster validation, drivers, firmware and patching are the customer's job.
- No built-in fleet management or self-service portal without System Center VMM or Azure Arc.
- AKS on Windows Server is retiring (March 2028); Microsoft steers new Kubernetes and AVD work to Azure Local.
- Pay-as-you-go ($33.58/core/month) carries no guest rights, so it rarely suits Windows-heavy HCI.
- Software Assurance, CALs and support contracts add cost beyond the $6,771 Datacenter list price.
Use-case fit
Mature Hyper-V clustering with unlimited Windows guests under Datacenter and free choice of certified hardware.
Low-cost landing zone for Windows-heavy estates, but the VMware conversion tool is still in preview and fleet management needs extra tooling.
RDS and third-party VDI with ReFS dedup and GPU partitioning, but no Azure Virtual Desktop session hosts.
Two-node switchless clusters work at branches, but there is no single-node S2D and no built-in fleet management.
All-NVMe S2D, Storage QoS and synchronous Storage Replica stretch clusters suit SQL Server and other tier-1 databases.
Strong SDN, but self-service and multi-tenancy need System Center VMM or third-party portals.
AKS on Windows Server is being retired by March 2028.
GPU partitioning with live migration and DDA, but no packaged AI services or object storage.
Synchronous and asynchronous Storage Replica, stretch and campus clusters, Hyper-V Replica and ASR to Azure.
Azure Arc adds cloud management, pay-as-you-go and Azure Hybrid Benefit, but the stack is not cloud-managed by design.
Familiar tools and perpetual licences, but building and patching S2D takes skill and there is no single support number.
Runs fully offline with perpetual licences, Common Criteria certification and long LTSC support.
180-day evaluation, checkpoints and ReFS block cloning, with no subscription needed.
Every comparison point
| Architecture & platform | |
|---|---|
| Hypervisor(s)Which hypervisor runs the virtual machines, and whether a choice of hypervisor is supported. |
Hyper-V, included in Windows Server. No choice of hypervisor. Windows Server Operating System | Microsoft ↗ |
| Architecture modelSoftware-defined (bring your own certified hardware), turnkey appliance, or disaggregated HCI (dHCI). |
Software-defined: bring your own Windows Server-certified servers. Hyperconverged S2D, converged (Scale-Out File Server) or SAN-backed Hyper-V clusters. learn.microsoft.com ↗ |
| Storage engineHow the distributed storage is implemented - controller VM, in-kernel, or a separate storage layer. |
Storage Spaces Direct in the host kernel (Software Storage Bus, storage bus cache, ReFS, Cluster Shared Volumes); no controller VM. Datacenter edition only. learn.microsoft.com ↗ |
| Minimum nodes per clusterThe smallest supported production cluster. |
Two servers for Storage Spaces Direct. Storage Spaces Direct Hardware Requirements in Windows Server ↗ |
| Maximum nodes per clusterThe largest supported cluster, and how further scale is achieved. |
16 servers per S2D cluster (over 400 drives, 4 PB). Hyper-V failover clusters on SAN reach 64 nodes and 8,000 running VMs. Storage Spaces Direct Hardware Requirements in Windows Server ↗ |
| Single-node deploymentWhether a one-node cluster is supported, and with what limits. |
Not for S2D (minimum two servers). A standalone Hyper-V host with local Storage Spaces works but has no HA. Storage Spaces Direct Hardware Requirements in Windows Server ↗ |
| Two-node cluster & witnessTwo-node support and what it needs as a witness or tie-breaker. |
Supported, switched or switchless, with nested resiliency. Witness options: file share, cloud (Azure Storage), disk or USB witness. learn.microsoft.com ↗ |
| Stretched / metro clusterOne cluster spanning two sites with synchronous mirroring and automatic failover. |
S2D stretch clusters with Storage Replica between sites (synchronous under 5 ms RTT). S2D campus clusters (Dec 2025 update) span two racks at 1 ms or less, up to 5+5 nodes. learn.microsoft.com ↗ |
| Independent scaling (compute-only / storage-only nodes)Whether compute and storage can grow separately. |
Converged deployments put Scale-Out File Server on S2D so compute clusters scale separately; SAN-backed and mixed architectures also supported. learn.microsoft.com ↗ |
| External storage (SAN / NAS) alongside HCIWhether existing SAN or NAS arrays can be attached to the same hosts. |
Full support for Fibre Channel, iSCSI and SMB 3 storage, alone or alongside S2D in the same cluster. learn.microsoft.com ↗ |
| All-flash / NVMe supportAll-NVMe support and any NVMe-optimised storage architecture. |
All-NVMe and persistent-memory S2D supported; Windows Server 2025 adds an optimised NVMe stack with more IOPS and less CPU. What's new in Windows Server 2025 ↗ |
| Host & VM maximumsPublished maximums per host or per VM - cores, memory, VMs. |
Hyper-V 2025 host: 2,048 logical processors, 4 PB RAM (5-level paging), 1,024 running VMs. VM: 2,048 vCPUs, 240 TB RAM (Gen 2), 64 TB VHDX. learn.microsoft.com ↗ |
| Storage & data services | |
| Deduplication & compressionInline or post-process data reduction, and which editions include it. |
ReFS native deduplication and compression (new in 2025), plus classic Data Deduplication. Post-process. What's new in Windows Server 2025 ↗ |
| Erasure coding (RAID-5/6)Capacity-efficient parity protection instead of full mirroring. |
Dual parity from 4 servers (50-80% efficiency) and mirror-accelerated parity; single parity from 3 servers (discouraged). learn.microsoft.com ↗ |
| Data resiliency (failures tolerated)Replication factor / failures-to-tolerate options and fault domains (rack, block). |
Two-way and three-way mirror, nested resiliency for 2 nodes, dual parity, chassis/rack fault domains and Rack Level Nested Mirror for campus clusters. learn.microsoft.com ↗ |
| Snapshots & clonesSpace-efficient snapshots and clones, and their limits. |
Hyper-V checkpoints (up to 50 per VM), ReFS block cloning, and thin-provisioned S2D volumes in 2025. learn.microsoft.com ↗ |
| Data-at-rest encryption & KMSSoftware encryption of the datastore, self-encrypting drives, and key management options. |
BitLocker (including on Cluster Shared Volumes) with TPM; shielded VMs with Host Guardian Service in Datacenter. Configured by the admin, not on by default. learn.microsoft.com ↗ |
| Storage QoSIOPS / throughput limits or guarantees per VM or volume. |
Storage QoS: minimum and maximum IOPS and bandwidth policies per VM or virtual disk. learn.microsoft.com ↗ |
| File services (SMB / NFS)Native file shares served by the platform. |
Native SMB 3 (including SMB over QUIC and Scale-Out File Server) and NFS server roles. learn.microsoft.com ↗ |
| Object storage (S3)Native S3-compatible object storage. |
No native S3-compatible object storage. Windows Server documentation ↗ |
| Block storage for external hostsPresenting volumes to physical servers or other clusters over iSCSI or NVMe-oF. |
iSCSI Target Server role and Scale-Out File Server (SMB 3) can present S2D capacity to other hosts. learn.microsoft.com ↗ |
| Data protection & DR | |
| Asynchronous replication (RPO)Native async replication and the lowest supported RPO. |
Hyper-V Replica (30 s, 5 min or 15 min) and Storage Replica asynchronous volume replication, with compression in 2025. Storage Replica Overview ↗ |
| Synchronous replication (zero RPO)Zero-data-loss replication between sites. |
Storage Replica synchronous block replication (zero RPO) between servers or clusters; unlimited in Datacenter, one 2 TB volume in Standard. Storage Replica Overview ↗ |
| DR orchestration & runbooksAutomated failover, failback and non-disruptive DR testing. |
Automatic site failover in stretch clusters; Azure Site Recovery recovery plans for Hyper-V to Azure. Hyper-V Replica failover is manual or scripted. Storage Replica Overview ↗ |
| Native backupBackup built into the platform, without a third-party product. |
Windows Server Backup for basic host backup; Microsoft Azure Backup Server is a separate product. No policy-driven VM backup built in. learn.microsoft.com ↗ |
| Immutable snapshots & ransomware protectionTamper-proof snapshots, ransomware detection and recovery features. |
No native immutable snapshots or ransomware detection; relies on third-party backup products. Windows Server Security documentation ↗ |
| Third-party backup ecosystemSupport from Veeam, Commvault, Rubrik, Cohesity, HYCU and similar. |
Hyper-V is supported by all major backup vendors (Veeam, Commvault, Rubrik, Cohesity and others) through Resilient Change Tracking. learn.microsoft.com ↗ |
| DR to public cloudUsing a public cloud as the recovery site. |
Azure Site Recovery replicates Hyper-V VMs to Azure with test failover and failback; Azure usage charges apply. learn.microsoft.com ↗ |
| Networking & security | |
| Software-defined networkingOverlay networks, VPCs, distributed routing and load balancing. |
Full SDN stack in Datacenter: Network Controller (a Failover Cluster service in 2025), Hyper-V network virtualization, Software Load Balancer, gateways and SDN Multisite. What's new in Windows Server 2025 ↗ |
| Microsegmentation / distributed firewallEast-west VM firewalling enforced at the hypervisor. |
Network security groups (Datacenter Firewall) enforced in the Hyper-V switch, with tag-based segmentation and default deny-inbound policies in 2025. What's new in Windows Server 2025 ↗ |
| RBAC, SSO & MFARole-based access control, directory / SAML integration and multi-factor authentication. |
Active Directory, JEA and Windows Admin Center RBAC; Microsoft Entra ID sign-in to Windows Admin Center in Azure through Arc. Workgroup clusters possible. What's new in Windows Server 2025 ↗ |
| Platform hardeningSecure boot, TPM, hardened baselines (STIG), automated drift remediation. |
Secured-core server, TPM, Secure Boot, VBS and Credential Guard on by default; OSConfig security baseline with 350+ settings; hotpatching via Arc. learn.microsoft.com ↗ |
| Security certificationsFIPS 140, Common Criteria, DISA STIG and similar attestations. |
Windows Server 2025 is listed among Microsoft's Common Criteria certifications; Windows cryptographic modules go through FIPS 140 validation. learn.microsoft.com ↗ |
| Management & operations | |
| Management consoleThe day-to-day management interface. |
Windows Admin Center (free, browser-based), Failover Cluster Manager, Hyper-V Manager and PowerShell; System Center VMM is licensed separately. learn.microsoft.com ↗ |
| Multi-cluster / fleet managementManaging many clusters and sites from one place. |
Windows Admin Center manages one cluster at a time; fleet management needs System Center VMM or Azure Arc (Windows Server Management enabled by Azure Arc). Windows Server Management enabled by Azure Arc ↗ |
| Lifecycle management (full-stack upgrades)Rolling, non-disruptive upgrades of software, drivers and firmware. |
Cluster-Aware Updating rolls OS updates across nodes; firmware and drivers come from OEM tools or Windows Admin Center extensions. Hotpatching via Arc cuts reboots. learn.microsoft.com ↗ |
| APIs & automationREST API, Terraform, Ansible, PowerShell and CLI coverage. |
Extensive PowerShell, WMI/CIM and DSC; REST through Windows Admin Center and Network Controller; Arc adds Azure APIs. Windows Server documentation ↗ |
| Monitoring, analytics & capacity planningBuilt-in health, performance analytics, forecasting and right-sizing. |
Health Service and cluster performance history for S2D, Windows Admin Center dashboards; Azure Monitor via Arc. No forecasting built in. learn.microsoft.com ↗ |
| Self-service & private-cloud portalCatalogues, projects, quotas and chargeback for consumers. |
No self-service portal in the box; needs System Center VMM or third-party tooling. Windows Server documentation ↗ |
| Live migration & HALive migration, automatic restart on failure and load balancing (DRS-like). |
Live migration, Failover Clustering HA restart, dynamic processor compatibility across CPU generations, and GPU-P live migration in 2025. What's new in Windows Server 2025 ↗ |
| Cloud, containers & AI | |
| Kubernetes & containersNative or integrated Kubernetes, and persistent storage for containers. |
AKS on Windows Server exists but is being retired: 2019 node pools March 2026, 2022 node pools March 2027, the whole architecture March 2028. Microsoft points to Azure Local. learn.microsoft.com ↗ |
| Hybrid / public cloudThe same stack in a public cloud, or cloud services managing the on-premises cluster. |
Azure Arc connects hosts to Azure: Update Manager, Machine Configuration, Windows Admin Center in Azure, ASR; some benefits require SA or pay-as-you-go. Windows Server Management enabled by Azure Arc ↗ |
| VDI / end-user computingValidated VDI brokers - Citrix, Omnissa Horizon, Azure Virtual Desktop and others. |
Remote Desktop Services and third-party VDI run on Hyper-V; Azure Virtual Desktop session hosts are not supported on plain Windows Server hosts (Azure Local only). learn.microsoft.com ↗ |
| GPU & AI workloadsGPU passthrough and vGPU, and packaged AI / inference offerings. |
GPU partitioning with HA and live migration, and Discrete Device Assignment. No packaged AI services. learn.microsoft.com ↗ |
| Database servicesBuilt-in database provisioning and lifecycle (DBaaS). |
No DBaaS; SQL Server runs in VMs or as failover cluster instances. Windows Server Operating System | Microsoft ↗ |
| Deployment & hardware | |
| Deployment method & timeHow a cluster is installed, and how long that typically takes. |
Manual build: install Windows Server, configure networking (Network ATC), run cluster validation and enable S2D via PowerShell or Windows Admin Center. Days for a first cluster. Storage Spaces Direct Hardware Requirements in Windows Server ↗ |
| Hardware optionsAppliances, certified / validated nodes and compatibility lists. |
Any server and components certified in the Windows Server Catalog; SDDC Standard/Premium qualifications recommended; the cluster must pass validation. Windows Server Catalog ↗ |
| Hardware OEMsWhich server vendors ship or certify nodes. |
Major server OEMs certify for Windows Server (for example Dell, HPE, Lenovo, Fujitsu and Supermicro); Lenovo publishes S2D-certified ThinkAgile MX configurations. Windows Server Catalog ↗ |
| Edge / ROBO suitabilitySmall footprints, remote management and low-touch operation for branches. |
Two-node switchless clusters with USB or cloud witness fit branches, but there is no central fleet management without Arc or System Center. learn.microsoft.com ↗ |
| Air-gapped / disconnected operationRunning and updating without any internet or cloud connection. |
Runs fully offline with perpetual licences, WSUS or offline updates. Pay-as-you-go and Arc benefits need connectivity. learn.microsoft.com ↗ |
| Migration tooling (e.g. from VMware)Built-in or vendor tools for moving VMs onto the platform. |
Windows Admin Center VM Conversion extension (preview, free) migrates VMware VMs from vCenter 6.x-8.x with CBT sync; System Center VMM and partner tools are alternatives. VM Conversion Extension in Windows Admin Center (Preview) ↗ |
| Licensing & subscription | |
| Licence modelSubscription, term, perpetual or free, and the usual term lengths. |
Perpetual core licences (optional Software Assurance) through volume licensing and OEMs, or pay-as-you-go through Azure Arc billed monthly. Windows Server 2025 Licensing Guidance ↗ |
| Licence metricWhat is counted - physical cores, sockets, nodes, TiB, or VMs. |
Physical cores (16-core and 2-core packs); CALs for users or devices. Pay-as-you-go counts cores per machine. Windows Server 2025 Licensing Guidance ↗ |
| Licensing minimumsMinimum cores per CPU, minimum order quantities and similar rules. |
At least 8 core licences per processor and 16 per server. Pay-as-you-go has no minimum core count. Windows Server 2025 Licensing Guidance ↗ |
| EditionsThe editions or packages sold. |
Datacenter (unlimited VMs, S2D, SDN, unlimited Storage Replica), Standard (2 VMs per licence, no S2D), Datacenter: Azure Edition and Essentials. learn.microsoft.com ↗ |
| Free / community editionA no-cost edition, and what it is licensed for. |
No free edition for production; a 180-day evaluation is available. learn.microsoft.com ↗ |
| Guest OS (Windows Server) licensingWhat the platform does, or does not do, for Windows Server guest licensing. |
Datacenter licensed for all host cores covers unlimited Windows Server VMs on that host. Standard covers two VMs per full licence. Pay-as-you-go gives no guest rights. Windows Server 2025 Licensing Guidance ↗ |
| Licence portabilityMoving the licence between hardware vendors, or into a public cloud. |
Licences move to any certified hardware; with SA, Azure Hybrid Benefit applies them to Azure VMs and Azure Local. learn.microsoft.com ↗ |
| Support & lifecycle | |
| Support offeringsThe support levels sold, and their hours. |
Microsoft Unified (Enterprise, Value Acceleration, Mission Critical) or support through partners; hardware support from the server OEM. Microsoft Unified Overview ↗ |
| Single point of support (hardware + software)One call for the whole stack, or separate vendors for hardware and software. |
Separate calls to Microsoft for software and to the OEM for hardware, unless an OEM resells Windows Server with its own support. Microsoft Unified Overview ↗ |
| Critical-issue responseTarget response time for a severity-1 issue on the top support tier. |
Microsoft Unified Enterprise: critical response within one hour for products other than Azure. azure.microsoft.com ↗ |
| Release & update cadenceHow often feature and maintenance releases ship. |
Monthly cumulative updates; hotpatches for Arc-enabled servers. New LTSC releases every few years (2016, 2019, 2022, 2025). learn.microsoft.com ↗ |
| Lifecycle policyHow long a release is supported, and long-term-support options. |
Fixed Lifecycle Policy: 5 years mainstream (to November 2029) plus 5 years extended (to November 2034). Windows Server 2025 - Microsoft Lifecycle ↗ |
| Cost | |
| Published list pricingWhether the OEM publishes prices, and the headline list price. |
Published MSRP: Datacenter $6,771 and Standard $1,176 per 16-core licence; pay-as-you-go $33.58 per core per month. Windows Server pricing and licensing ↗ |
| TCO drivers & hidden costsAdd-ons, minimums, hardware premiums and other costs that move the total. |
CALs, Software Assurance, System Center for fleet management, backup software, and staff time to build and patch. Pay-as-you-go needs guest licences per VM. Windows Server pricing and licensing ↗ |
| Vendor & ecosystem | |
| Vendor & ownershipWho owns and develops the platform, and recent ownership changes. |
Developed and sold by Microsoft. Microsoft Source ↗ |
| Ecosystem & communityPartners, certified applications, skills availability and community. |
Very large Windows Server and Hyper-V skills base, broad hardware certification, and support from all major backup and management vendors. Windows Server Catalog ↗ |
| Lock-in & exit optionsOpen formats, standard hypervisors and how hard it is to leave. A higher score means less lock-in. |
Standard VHDX format, perpetual licences, no cloud dependency and any certified hardware; tooling is Microsoft-specific. Windows Server Operating System | Microsoft ↗ |
| Regional availability & sovereigntyWhere the platform is sold and supported, and sovereignty considerations. |
Sold and supported worldwide; can run entirely on premises and offline for sovereignty needs. Microsoft Source ↗ |
Editions
| Edition | Model | Metric | Price / unit / yr | Basis | Support | Best for |
|---|---|---|---|---|---|---|
| Windows Server 2025 Datacenter (perpetual) ↗ | Perpetual | per physical core | $85 | OEM list price | Not included; Microsoft Unified or partner support, hardware from the OEM | HCI clusters running many Windows Server VMs, with unlimited guest rights and no cloud dependency. |
| Windows Server 2025 pay-as-you-go via Azure Arc ↗ | Subscription | per physical core | $403 | OEM list price | Not included | Short-term or variable-size hosts where Linux or separately licensed guests make unlimited virtualisation unnecessary. |
| Windows Server 2025 Standard (perpetual, no S2D) ↗ | Perpetual | per physical core | $15 | OEM list price | Not included | Physical or lightly virtualised servers and small SAN-backed Hyper-V clusters, not hyperconverged storage. |
Hardware routes
- Windows Server Catalog systems with SDDC Standard/Premium qualifications ↗
Hcl
Multiple OEMs — Certified servers, NICs and drives; SDDC AQs recommended and the cluster must pass validation. - Lenovo ThinkAgile MX certified configurations ↗
Certified
Lenovo — Lenovo certifies SR630 V4, SR650 V4 and SR650a V4 configurations for both Azure Local and Windows Server S2D. - Any Windows Server 2025-certified server ↗
Any
Dell, HPE, Lenovo, Fujitsu, Supermicro and others — Buy servers with Windows Server OEM or volume licences; S2D needs direct-attached drives behind a pass-through HBA.
Support
- Microsoft Unified Enterprise ↗
24x7 · Sev-1: 1 hour (non-Azure products) · Priced by agreement; covers Windows Server. - Server OEM hardware support ↗
Per OEM contract · Sev-1: Per OEM contract · Hardware, firmware and drivers are supported by the server vendor.
Deployment
- Networks
- Management, VM traffic, Storage / SMB Direct (RDMA), Live migration, Out-of-band (BMC)
- NICs
- 10 GbE minimum for 2-3 nodes; 25 GbE+ RDMA (iWARP or RoCE) recommended for 4+ nodes; two or more ports per node
- Switching
- Two redundant switches (DCB configured for RoCE), or switchless full-mesh cabling for small clusters
- Witness
- File share, cloud (Azure Storage), disk or USB witness; for stretch and campus clusters, in a third location
- Time to deploy
- One to several days for a first cluster; faster with scripts
Reference diagrams
Drawn for the default workload (200 VMs → 7 nodes). Build a comparison to size them for yours.OEM references
- ProductWindows Server Operating System | Microsoft ↗
- DatasheetWhat's new in Windows Server 2025 ↗
- DocsWindows Server documentation ↗
- RequirementsStorage Spaces Direct Hardware Requirements in Windows Server ↗
- LicensingWindows Server 2025 Licensing Guidance ↗
- PricingWindows Server pricing and licensing ↗
- SupportMicrosoft Unified Overview ↗
- LifecycleWindows Server 2025 - Microsoft Lifecycle ↗
- HclWindows Server Catalog ↗
- DrStorage Replica Overview ↗
- SecurityWindows Server Security documentation ↗
- NetworkingSoftware Defined Networking (SDN) ↗
- K8sOverview of AKS on Windows Server ↗
- CloudWindows Server Management enabled by Azure Arc ↗
- MigrationVM Conversion Extension in Windows Admin Center (Preview) ↗
- EcosystemWindows Server Catalog ↗
- CompanyMicrosoft Source ↗