What SDxCentral reports
SDxCentral describes HCI as virtualization that merges server and storage resources, and sometimes networking, into an appliance run from one console. Its stated drawback is that compute and storage scale together, even when only one is short. The piece lists Azure Local alongside AWS Outposts and Google Distributed Cloud as cloud-provider on-premises offerings. It also names Nutanix, VMware under Broadcom, Red Hat OpenShift and HPE Morpheus VM Essentials as software platforms in the same market.
Gartner research VP Julia Palmer gives three reasons for the renewed interest in disaggregation:
- Storage is easier to manage. Palmer says modern arrays take about two hours to learn, against five-day classes in the past. That is her observation, not a measured industry benchmark.
- Arrays are more cost-competitive. She cites deduplication, compression and specialized controllers. The article says flash costs the same inside HCI or an array, and it attributes current high flash and memory prices to supply constraints.
- Platforms now accept third-party storage. That allows a common control plane over separate storage and compute.
Palmer also says customers pick a platform first and then decide between HCI and disaggregated. In her view, large organizations with unpredictable growth suit disaggregation, while small offices and edge sites suit HCI. Some organizations use both. The article gives no market-share or survey numbers, so treat these as analyst and vendor views.
What "disaggregated" means on Azure Local
Microsoft's documentation treats hyperconverged and disaggregated as distinct deployment types. The distinctions below come from Microsoft Learn.
| Hyperconverged | Disaggregated | |
|---|---|---|
| Storage | Local drives pooled with Storage Spaces Direct (S2D) | External SAN, no S2D |
| Scale | Up to 16 machines for standard clusters, up to 8 for rack-aware clusters | SAN storage, up to 64 machines |
| Growth model | Compute and storage grow together | Storage capacity is independent of node count |
| Rack-aware | Supported | Not supported, per a community documentation site |
Microsoft's network guidance says disaggregated clusters scale across 1 to 8 racks, up to 16 nodes per rack and 64 nodes per cluster. Its deployment-type guide recommends disaggregated when storage requirements grow at a different rate than compute. The Well-Architected guidance puts the same trade-off differently: disaggregated deployments add the L2 service tier, SAN, redundant fabrics, and specialist operations. That is the cost of independent scaling.
The middle option: hybrid HCI plus SAN
The easiest mistake is to equate "Azure Local supports a SAN" with "this is a disaggregated cluster." Microsoft documents a third arrangement. A hyperconverged cluster can attach an external SAN alongside S2D, so you choose storage per workload. Microsoft's network guidance says this SAN is attached after the initial deployment, as a day-2 step. It says you can't start a hybrid configuration from the start, and rack-aware clusters don't support it. Microsoft's own wording is that you can also attach an external SAN for more storage capacity to a hyperconverged deployment.
Microsoft's external-storage article says the capability covers both hybrid (S2D plus SAN) and disaggregated (SAN only) deployments. Supported protocols are Fibre Channel and iSCSI. SAN volumes appear as Cluster Shared Volumes formatted with NTFS and mapped as storage paths for VMs. Microsoft says the arrays can back VMs, AKS clusters and Azure Virtual Desktop. Listed benefits include reusing existing SAN investment, familiar operations, and resilience from dual fabrics and multipathing. These are vendor-described benefits, not independent test results.
Practical notes for administrators
Microsoft's external-storage article, last updated July 2026, lists several prerequisites:
- Hybrid Fibre Channel and iSCSI setups need an Azure Local cluster deployed at version 2604 or later.
- iSCSI NICs must be dedicated physical ports; vNICs aren't supported in hybrid storage.
- iSCSI NICs stay outside Network ATC and are configured manually, with static IPs and no default gateway.
- The guide registers the storage vendor with the Microsoft Device Specific Module (MSDSM) so MPIO claims the LUNs. Everpure FlashArray, for instance, needs removal of a generic wildcard vendor entry.
- For Fibre Channel, don't zone the HBA World Wide Names until after Azure Local deployment, to avoid confusion over LUNs.
- The array must support SCSI-3 Persistent Reservations, or cluster validation will fail.
- Every node must see the same LUNs with consistent LUN IDs.
Networking differs too. Microsoft says disaggregated designs carry storage and cluster traffic over TCP, so they don't need PFC or lossless Ethernet, though they still need jumbo frames, MLAG or vPC, and MPIO-compatible VLANs. For jumbo frames, the MTU depends on the storage vendor, so use the vendor's value end to end. Switched hyperconverged designs with S2D rely on RDMA instead.
How to weigh it
A reasonable sequence for a Microsoft-centric team:
- Estimate compute and storage growth separately. If they track each other, HCI's simplicity is hard to beat.
- Check whether you already run a SAN that you want to keep.
- Compare your node count against the 16-machine HCI ceiling and the 64-machine disaggregated one.
- Confirm your array model and firmware appear in Microsoft's supported SAN list, and check your workloads. Microsoft's workload table shows Azure Local VMs, AKS, SQL Server, Azure Virtual Desktop and AI workloads available on both hyperconverged and disaggregated.
- Plan for the operational overhead of fabrics, zoning and storage-team coordination.
Caveats
SDxCentral is an explainer built on interviews, and Gartner's Palmer and vendor executives each have a point of view. Nothing in it shows Azure Local is the better choice, and Microsoft's documentation doesn't claim universal superiority either. Documentation also changes quickly: the pages cited here span Azure Local versions 2604 through 2610, so confirm limits against the release you plan to run. The reliable takeaway is that on Azure Local, "disaggregation" is a specific, documented architecture with its own limits, not a generic label.
References
- HCI today: Hyperconverged infrastructure and the convergence trend - SDxCentral SDxCentral · 2026-11-12T00:00:00+00:00
- Find your Azure Local deployment type - Azure Local | Microsoft Learn learn.microsoft.com
- Network considerations for cloud deployment for Azure Local - Azure Local | Microsoft Learn learn.microsoft.com