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.
Development baseline, not a production release
Five independent MP artifacts, the platform-owned DA, monitoring workflows, operator views, customer override templates, and offline tests are implemented. Microsoft VSAE/SDK verification, ordered transient test sealing, and strong-name verification pass for the complete suite against the installed SCOM 2022 dependencies. Governed release signing and SCOM lab certification are still required before release.
No Azure Local SCOM package is publicly downloadable yet. This track remains a development and validation baseline.
Looking for the other SCOM product? See the independent Hyper-V SCOM Management Pack.
Implemented product
| Area | Development baseline |
|---|---|
| Packaging | Library, Discovery, Monitoring, Presentation, and optional Reporting artifacts |
| Model | 17 public classes and 28 public relationships, with stable deployment and storage identities |
| Discovery | Lightweight Azure Local qualification followed by full local topology discovery |
| Health | 14 unit monitors, six domain aggregates, and explicit monitoring-pipeline state |
| DA | One deployment service, six components, and 12 dependency rollups |
| Telemetry | 12 performance rules and four high-confidence Failover Clustering event-alert rules |
| Operations | 14 views, a read-only diagnostic task, and operational knowledge |
| Tuning | Separate customer-owned Discovery and Monitoring override MPs with provisional Lab, Standard, and Strict starters |
Documentation
- Architecture
- Management Pack structure
- Class and relationship model
- Discovery and workflow architecture
- Health and alert architecture
- Override and tuning architecture
- Validation and release gates
- Monitoring research and catalog
- Management Pack administration guide
Where to start
- Azure Local SCOM design — the governing design lane
- Architecture — the product and runtime boundary
- Monitoring catalog — what is monitored, collected, or deferred
- Management Pack guide — build, import, tune, upgrade, and remove
- Validation and release — completed authoring evidence and remaining lab/release gates
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.