Hyper-V design
Hyper-V Private Cloud Monitoring is an enterprise on-premises monitoring suite engineered entirely for System Center Operations Manager (SCOM). It has zero cloud, Azure Monitor, or Azure Arc runtime dependencies.
| Design lane | Commitment | Status |
|---|---|---|
| SCOM Management Pack | Committed | Production release sealed (1.3.8.0); full architecture contracts published |
SCOM Management Pack solution
The SCOM lane provides implementation-grade design contracts for the end-to-end architecture, Management Pack structure, dependency and ownership contract, 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.
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?
SCOM packaging is governed by ADR 0022 and 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.