Hyper-V design
Hyper-V has its own support contract and topology. Its SCOM Management Pack and conditional Azure Monitor Health Models are completely separate solutions: neither shares runtime components, deployment artifacts, health state, or release lifecycle with the other. Both may reuse validated Hyper-V research without creating a product dependency.
| Design lane | Commitment | Status |
|---|---|---|
| SCOM Management Pack | Committed | Comprehensive architecture proposed; phase-one research active |
| Azure Monitor through Arc-enabled SCVMM | Conditional | Research and go/defer/no-go ADR required |
SCOM Management Pack solution
The SCOM lane now has implementation-grade design contracts for the end-to-end architecture, Management Pack structure, class and relationship model, discovery and workflows, health and alerts, Distributed Application, authoring standards, security and operability, and validation and release.
The diagrams on these pages are rendered by the site's Vue component so architecture, sequence, state, class, and decision flows remain readable in both light and dark documentation themes.
The Hyper-V Distributed Application belongs only to this SCOM solution. Optional SquaredUp Dashboard Server content also belongs to the Hyper-V SCOM solution.
Azure Monitor Health Models solution
The conditional Azure Monitor design is a separate future solution boundary. It remains gated on Arc-enabled SCVMM research and ADR 0023 and does not inherit the SCOM class, workflow, Distributed Application, packaging, or health-state implementation. Optional SquaredUp Cloud content remains inside this same conditional boundary and cannot proceed before the Azure Monitor solution receives a go decision.
Platform design questions
- Which Windows Server, SCOM, cluster, and optional SCVMM versions are supported?
- Which standalone and clustered entities have stable discovery keys and ownership relationships?
- When is Network ATC the host-network authority, and when is networking manual or owned by SCVMM/SDN?
- Which signals should become default monitors, disabled monitors, collection rules, diagnostics, or exclusions?
- Which stable keys and relationships populate each standalone-host or cluster Distributed Application?
- Can Arc-enabled SCVMM expose a supportable Azure Monitor entity and telemetry model?
SCOM packaging is no longer an open question. ADR 0022 requires completely independent Azure Local and Hyper-V runtime products.
These questions are resolved through the research backlog, not by copying the Azure Local design.