Azure Local SCOM Management Pack
Azure Local / SCOM — the committed SCOM delivery surface for Azure Local.
This section covers how the Azure Local design is implemented as a SCOM Management Pack. Read the Azure Local SCOM design lane first. Shared principles do not make this platform's entity model, signals, or discoveries applicable to the Hyper-V MP.
Authoring has not started
The Azure Local design baseline is accepted. ADR 0022 requires an independent Azure Local runtime product; packaging validation confirms its artifact, coexistence, upgrade, and removal contract. Delivery is described in the public roadmap. See the implementation plan.
Looking for the other SCOM product? See the planned Hyper-V SCOM Management Pack.
What lives here
| Page (planned) | Content |
|---|---|
| Health model XML overview | The sealed Azure Local product structure selected by ADR 0022 |
| Class hierarchy reference | Implementation of ADR 0005 |
| Discoveries reference | PowerShell discovery scripts per ADR 0004 |
| Monitor inventory | Unit / Aggregate / Dependency monitors mapping to the Signal Catalog |
| Distributed Application | AzureLocal.Deployment, component groups, dynamic membership, rollup, views, reports, dashboards, and SLO targets from the DA design |
| Override pack reference | Customer-facing overrides per ADR 0008 |
| Authoring guide | VSAE + Kevin Holman fragment library workflow |
| Lifecycle | Sealing, signing, import, update, retirement |
| Diagrams | Health rollup tree (Mermaid) + class hierarchy (draw.io) |
Where to start
- Azure Local SCOM design — the governing design lane
- SCOM class hierarchy ADR
- Azure Local Distributed Application
- Discovery strategy ADR
- Customization — how operators tune the SCOM track
Track-specific upstream references
- Brian Wren / MPAuthor video series (SC 2012 R2 — Operations Manager Management Packs)
- Kevin Holman — SCOM Management Pack Fragment Library
- Silect MP Author (free authoring tool)
- See full reference list in REFERENCES.md.