S2D: Virtualization Storage Ledger 2026 Scorecard

Part of the Virtualization Storage Ledger (edition 2026-10-16). How the scores work: methodology.

Snapshot

Type: product
Owner: Microsoft Corporation (public)
Licence: Windows Server Datacenter feature (USD 6,771 per 16-core licence plus client access licences, or USD 33.58 per core per month through Azure Arc; page undated) or Azure Local billed per physical core per month with L1 hyperconverged, L2 disaggregated or SAN and L3 disconnected tiers; 180 day Windows Server evaluation, 60 day Azure Local trial
Latest release: Azure Local 2609 (12.2609.1003.7, 2026-09-11) on a Windows Server 2025 base; Windows Server 2025 GA 2024-11-01
Support lifecycle: Windows Server 2025 mainstream to 2029-11-14 and extended to 2034-11-15; each Azure Local release is supported for six months and the 23H2 OS ended in April 2026
Next milestone: none dated; automatic key backup, internal DNS for local identity, GPU management from Azure and add node in the portal are previews in 2608 and 2609
Hypervisors: Hyper-V only, as a Windows Server or Azure Local feature with Failover Clustering and Cluster Shared Volumes (Microsoft Learn S2D overview)
Tier: Storage inside a VM platform
Archetype: Integrated stack
Evidence grade: A. Release dates, the Azure Local what's new and release tables, the billing page, the lifecycle pages and the Windows Server 2025 what's new were read from Microsoft Learn (grade A). The 2016 to 2022 feature steps and the stretched cluster dates rest on background knowledge and the VM Platform Ledger (grade C). Azure Local host prices were not captured.

Scope of the scores: Storage Spaces Direct ships only with Windows Server Datacenter or inside the Azure Local subscription and serves Hyper-V only, which the hypervisor integration ceiling and the lock-in rows reflect. Azure Local as a VM platform is scored in the VM Platform Ledger; this entry scores the storage layer and shows both commercial routes.

Scorecard

Dimension	Score	Direction
Capability today	73.3 / 100	higher is better
Momentum since end of 2022	+3.1 points (2015 to 2022: +70.2)	higher is better
Credibility	17.5 / 25	higher is better
Commercial risk	11.5 / 25	lower is better
Technical lock-in	12.0 / 25	lower is better
Integrator fit	16.5 / 20	higher is better
AI leverage	7.0 / 20	higher is better
Ledger Index	62.8 / 100	balanced weights; see the methodology

Capability by domain, 2015 to today

Scores 0 to 5 against fixed anchors; total is weighted to 100.

Domain (weight)	2015	2019	2022	Today
Data services core (15)	0	4	4	4
Resilience and HA (15)	0	3.5	4	4
Performance and protocols (12)	0	3.5	3.5	3.5
Hypervisor integration (12)	0	3.5	3.5	3.5
Scale and topology (10)	0	3.5	3.5	4
Data protection and DR (10)	0	3.5	3.5	3.5
Security (8)	0	3	3	3.5
Operations and automation (8)	0	3.5	3.5	4
Hardware and deployment freedom (5)	0	2.5	2.5	2.5
Kubernetes and containers (5)	0	0	2.5	3
Total / 100	0.0	66.2	70.2	73.3

Year by year: 2015: 0.0 · 2016: 63.9 · 2017: 63.9 · 2018: 66.2 · 2019: 66.2 · 2020: 67.7 · 2021: 70.2 · 2022: 70.2 · 2023: 68.7 · 2024: 70.0 · 2025: 70.8 · 2026: 73.3

What moved the score

Year	Domain	Change	Points	Trigger
2016	Data protection and DR	0 → 3.5	+7.0	Windows Server 2016: Storage Replica synchronous and asynchronous, Hyper-V Replica, resilient change tracking, Azure Site Recovery and broad backup vendor support; no immutable snapshots
2016	Data services core	0 → 3.5	+10.5	Windows Server 2016: thin provisioning, mirror and parity erasure coding, ReFS block cloning and checkpoints, Storage QoS with minimum and maximum IOPS
2016	Hardware and deployment freedom	0 → 2.5	+2.5	Windows Server 2016: Microsoft-approved validated servers; Azure Local later limits hardware to its catalogue
2016	Hypervisor integration	0 → 3.5	+8.4	Windows Server 2016: native Hyper-V datastore with CSV, ODX, live migration and checkpoints; single-hypervisor ceiling applies
2016	Operations and automation	0 → 3	+4.8	Windows Server 2016: PowerShell, Failover Cluster Manager, Health Service, cluster-aware updating
2016	Performance and protocols	0 → 3.5	+8.4	Windows Server 2016: SMB 3 with SMB Direct RDMA, NVMe cache tiers, all-flash and hybrid sizing guidance; no NVMe/TCP target
2016	Resilience and HA	0 → 3.5	+10.5	Windows Server 2016: two and three way mirror, dual parity, chassis and rack fault domains, self-healing, cloud and file share witness
2016	Scale and topology	0 → 3.5	+7.0	Windows Server 2016: 2 to 16 nodes, hyperconverged or converged Scale-Out File Server, 1 PB per cluster (4 PB from 2019)
2016	Security	0 → 3	+4.8	Windows Server 2016: BitLocker on cluster volumes, SMB encryption in flight, role-based access; no external key manager
2018	Data services core	3.5 → 4	+1.5	Windows Server 2019: Data Deduplication on ReFS volumes (feature detail grade C); native ReFS dedup and compression follow in 2025
2018	Operations and automation	3 → 3.5	+0.8	Windows Admin Center for S2D clusters (year grade C)
2020	Resilience and HA	3.5 → 4	+1.5	Azure Stack HCI 20H2: stretched clusters with Storage Replica, 4 to 16 nodes at 5 ms (date grade C)
2021	Kubernetes and containers	0 → 2.5	+2.5	AKS on Azure Stack HCI GA with CSI drivers for S2D volumes and SMB (year grade C)
2023	Resilience and HA	4 → 3.5	-1.5	Azure Stack HCI 23H2: stretched clusters no longer supported on the new deployment model (per the VM Platform Ledger)
2024	Kubernetes and containers	2.5 → 3	+0.5	2402: AKS enabled by Azure Arc included at no extra charge; RWX through SMB
2024	Security	3 → 3.5	+0.8	Azure Local 23H2: more than 300 security settings with drift control and Trusted launch VMs (GA date grade C); confidential VMs still preview in 2607
2025	Operations and automation	3.5 → 4	+0.8	2504: Azure-side billing and lifecycle; Azure CLI, ARM, Bicep and Terraform manage Azure Local; monthly cloud-delivered updates
2026	Resilience and HA	3.5 → 4	+1.5	2601: rack aware clustering GA; 2607: local availability zones for disaggregated deployments
2026	Scale and topology	3.5 → 4	+1.0	2601: rack aware clustering across racks; 2604: disaggregated deployments to 64 machines, though those use SAN storage rather than S2D

Direction, 2023 to 2026

Each release item carries one theme and one driver (V vision, C customer need, M market window, U upstream, P portfolio).

Date	Item	Theme	Driver
2023-11	Azure Stack HCI 23H2: cloud-based deployment model; stretched clusters dropped (dates grade C)	Operations	P
2024-11	Windows Server 2025: NVMe optimisation, ReFS native deduplication and compression, Storage Replica compression	Data services	C
2024-11	Windows Server 2025: GPU partitioning with HA and live migration	AI	V
2024-11	Azure Stack HCI renamed Azure Local (date grade C)	Packaging	P
2025-01	AKS enabled by Azure Arc included at no extra charge	Kubernetes	P
2025-04	2504: billing taken from the Azure Local resource; continues until disconnected for more than 31 days	Licensing	P
2025-09	2509: storage path deletion workflow	Operations	C
2025-11	2510: rack aware clustering preview	Resilience	C
2026-01	2601: rack aware clustering GA	Resilience	C
2026-04	2604: SAN storage GA alongside S2D; disaggregated deployments to 64 machines	Scale	M
2026-04	2604: GPU acceleration for Azure Local VMs GA (DDA and GPU-P)	AI	V
2026-04	L1, L2 and L3 billing tiers; adding external storage moves a cluster to L2 after a 30 day trial (date grade C)	Licensing	P
2026-05	2605: iSCSI SAN preview; Azure Migrate to Azure Local with SAN storage	Hypervisor integration	P
2026-07	2607: iSCSI SAN GA; confidential VM (AMD SEV-SNP) preview; local availability zones	Security	V
2026-08	2608: GPU management from Azure and add node in the portal, both preview	Operations	V
2026-09	2609: automatic key backup and internal DNS for local identity, preview	Security	C
2026-09	Edge RAG enabled by Azure Arc on Azure Local, preview	AI	V

Centre of gravity: Operations (3), AI (3), Licensing (2)
Blind spots (no items): Performance, Data protection, Hardware
Driver mix: Vision 29%, Customer need 29%, Market window 6%, Upstream 0%, Portfolio 35%
Idea-to-need index: 0.45 (0 = demand-pulled, 1 = thesis-pushed)

Credibility: 17.5 / 25

Criterion	Score	Basis
Cadence	4.5	Monthly Azure Local releases on a published table since 2025; Windows Server LTSC every two to three years
Roadmap transparency	3	Public what's new and release tables on Microsoft Learn; no dated roadmap
Say-do	3.5	Rack aware clustering went preview to GA in 11 weeks and iSCSI SAN in 8; confidential VMs, GPU management and add node remain previews
Velocity	4	SAN support, disaggregation, iSCSI and rack aware clustering inside six months
Lifecycle stability	2.5	Windows Server keeps ten-year support, but Azure Local must update every six months, stretched clusters were dropped without an upgrade path and the product was renamed twice

Commercial risk: 11.5 / 25 (lower is better)

Criterion	Score	Basis
Price and licence volatility	3	Billing moved into Azure in 2504 and three price tiers arrived with SAN support in 2026; Azure Hybrid Benefit applies only to L1 hyperconverged
Purchase constraints	3	Datacenter edition for Windows Server; an Azure subscription, Azure Arc and catalogue hardware for Azure Local; L3 pricing by account representative only
Channel and access	1.5	Enterprise Agreement, CSP and twelve OEM hardware partners; OS download from the Azure portal
Owner stability	0.5	Stable owner, no acquisition behind the product
Cost of staying supported	3.5	Azure Local releases are supported six months and billing continues until the resource is disconnected; Windows Server 2025 is supported to 2034

Technical lock-in: 12.0 / 25 (lower is better)

Criterion	Score	Basis
Formats	1.5	VHDX is an open specification and ReFS is readable by any Windows host; VM configuration is binary
Export path	2.5	Hyper-V export per VM; Azure Migrate is inbound only
Stack coupling	3.5	Windows Server Datacenter, Failover Clustering and Hyper-V always; Azure Local adds the Azure subscription and Arc
Hardware / cloud coupling	3	Windows Server S2D runs offline on approved servers; Azure Local needs catalogue hardware and contact with Azure at least every 30 days (blended)
Skills and tooling coupling	1.5	Windows, PowerShell, Hyper-V and Azure skills are widely held

Integrator fit: 16.5 / 20

Criterion	Score	Basis
Partner programme openness	4	Open Microsoft partner network and CSP; twelve OEM hardware partners
Multi-tenancy and self-service	3.5	Azure RBAC, Azure Policy and Arc VM self-service on Azure Local; Windows Server alone has none
API and infrastructure-as-code	4.5	ARM, Bicep, Terraform and Azure CLI for Azure Local; PowerShell for Windows Server
Skills and certification	4.5	Microsoft certification tracks and the largest Windows skills pool; current track names not verified

AI leverage: 7.0 / 20

How the product uses AI, scored per year like capability. Only GA counts.

Criterion	2019	2022	Today	Latest step
AI workload infrastructure	1	1	3.5	2026: 2604: GPU acceleration GA for Azure Local VMs (DDA and GPU-P); RTX PRO 6000 Blackwell supported from 2603; GPU metrics in 2605
AI platform stack	0	0	0.5	2026: Edge RAG enabled by Azure Arc in preview, counted as half a step
AI-assisted operations	1	1	1	2016: Windows Server 2016: rule-based Health Service; no ML analytics or assistant found
Agent openness	1.5	2	2	2021: ARM and Azure CLI control of Azure Local; no MCP server found (year grade C)

Year by year: 2015: 0 · 2016: 3.5 · 2017: 3.5 · 2018: 3.5 · 2019: 3.5 · 2020: 3.5 · 2021: 4 · 2022: 4 · 2023: 4 · 2024: 6 · 2025: 6 · 2026: 7

AI say-do, 2023 to 2026: 3 AI items announced; 1 GA, 2 still preview, 0 pending, 0 dropped. GPU acceleration shipped; GPU management from Azure and Edge RAG are previews.

Microsoft's AI effort on this platform goes into GPU sharing for VMs, which is now GA with live migration, rather than into the storage layer or into operating it. Edge RAG is a preview and no agent interface exists. Check whether the GPU you plan to use is on the Azure Local support list, because support arrived model by model.

Reading

S2D scores as a solid, single-hypervisor storage layer whose recent gains come from Azure Local topology work: rack awareness, availability zones and SAN options. It trails vSAN and AOS on DR and security because it has no immutable snapshots, no anomaly detection and lost stretched clusters in the move to 23H2. The two purchase routes behave very differently: Windows Server gives ten years of support offline, Azure Local gives monthly features in exchange for a six-month update window and per-core cloud billing. A buyer should check which tier a planned design lands in, since adding external storage moves the whole cluster to L2.

Open questions and items to re-score

Azure Local L1 and L2 per-core host prices were not captured; the pricing page showed a placeholder.
Stretched cluster dates (20H2 added, 23H2 dropped) come from background knowledge and the VM Platform Ledger, grade C.
The Azure Stack HCI to Azure Local rename date and the 23H2 GA date were not found on the pages read.
Immutable snapshot support and current witness options were not verified; DR stays at 3.5.
Confidential VMs, GPU management from Azure, add node in the portal, key backup and Edge RAG are previews; re-score when GA.
Windows Server price history 2023 to 2026 and whether the 180 day evaluation is still offered were not checked.
CSI and RWX details for AKS on Azure Local were not read; Kubernetes stays at 3.

	’16	’18	’20	’21	’24	’25	’26
Data services core	1	1
Resilience and HA	2		1				1
Performance and protocols	3
Hypervisor integration
Scale and topology							2
Data protection and DR
Security					1
Operations and automation		2				1
Hardware and deployment freedom
Kubernetes and containers				1	2