Hyper-V
Hyper-V is a separate platform track. Its primary delivery is a SCOM Management Pack. Azure Monitor is a conditional future delivery surface for environments that use Azure Arc-enabled System Center Virtual Machine Manager (SCVMM) and meet the yet-to-be-approved prerequisites.
| Delivery surface | Commitment | Status |
|---|---|---|
| SCOM Management Pack | Committed platform track | Research and design active |
| Azure Monitor through Arc-enabled SCVMM | Conditional roadmap track | Research gate; no implementation commitment |
Two independent solutions
The SCOM Management Pack and conditional Azure Monitor Health Models have separate design, source, deployment, testing, and release boundaries.
Why this is separate from Azure Local
Hyper-V and Azure Local share Windows Server virtualization and SCOM concepts, but they do not have identical product topology or signal sources. Azure Local adds a prescribed, Azure-integrated platform stack with opinionated storage, lifecycle management, registration, and Azure-side services. Hyper-V must also account for standalone hosts, general-purpose failover clusters, optional SCVMM management, and configurations that have no Azure dependency.
Network ATC is not an Azure Local-only capability. It is supported for eligible Windows Server 2025 Datacenter failover clusters and is this project's preferred host-networking baseline for such Hyper-V clusters. When SCVMM and Windows Server SDN are the selected network-management authority, the Management Pack must model that path instead of assuming Network ATC ownership. Older or otherwise ineligible Hyper-V environments still require explicit non-ATC coverage.
The project will reuse stable authoring patterns and shared health semantics while keeping platform-specific discoveries and monitoring independently supportable.
See the Hyper-V design map for the separate SCOM and conditional Azure Monitor Health Models lanes.
Planned Hyper-V topology research
The first spike will define the supported matrix for:
- standalone Hyper-V hosts;
- Hyper-V failover clusters;
- hosts and VMs managed by SCVMM;
- Network ATC-managed, manually managed, and SCVMM/SDN-managed host networking;
- virtual switches, adapters, storage, replication, and VM relationships; and
- supported Windows Server, SCOM, and SCVMM versions.
See Research spikes and the Hyper-V SCOM track for the delivery gate.
Phase-one execution is documented in the Hyper-V SCOM monitoring research plan. Its catalog policy separates the exhaustive raw inventory from the smaller default monitoring profile.