Azure Local SCOM Management Pack design
This lane applies the accepted Azure Local platform baseline to SCOM. It does not govern the Hyper-V SCOM MP unless a shared pattern is explicitly adopted through ADR 0022 or a Hyper-V successor ADR.
Current status
The independent Azure Local SCOM product now has a functional development baseline. Its source builds five Management Pack artifacts, passes deterministic offline contract tests and Microsoft VSAE/SDK verification against the installed SCOM 2022 dependency set, and completes ordered transient test sealing. Governed release signing, SCOM lab import, discovery, fault/recovery, scale, upgrade, coexistence, and removal evidence remain release gates.
Canonical design
| Concern | Design source |
|---|---|
| Product boundary | Architecture and ADR 0032 |
| Packaging | Management Pack structure and ADR 0033 |
| Platform entities and relationships | Class and relationship model and ADR 0034 |
| Discovery and execution | Discovery and workflow architecture |
| Health, alerts, and rollup | Health and alert architecture and ADR 0035 |
| Distributed Application | Azure Local DA design, ADR 0026, and ADRs 0034–0035 |
| Overrides | Override and tuning architecture and ADR 0008 |
| Testing and release | ADRs 0014, 0015, 0016, 0017, and 0018 |
Implementation section
Continue to the Azure Local SCOM Management Pack for the implementation inventory, monitoring research, catalog, administration guide, and validation status.
The Azure Local DA is a required product artifact, not an optional dashboard convenience. It is the deployment-level service root for Health Explorer, views, reports, dashboards, and SLOs; aggregate and dependency monitors perform the underlying health propagation.