Skip to content

Start here

This site covers two independent monitoring solutions. They are completely separate platforms with distinct operational boundaries, separate management packs, and independent prerequisites:

  • Hyper-V Private Cloud: Sovereign, 100% on-premises enterprise monitoring delivered through System Center Operations Manager (SCOM).
  • Azure Local: Independent SCOM and cloud-native Azure Monitor tracks for Azure Local (formerly Azure Stack HCI).

Follow the path below that matches your infrastructure.


Which solution do I need?

If your infrastructure is…Solution to useDelivered through
Hyper-V Private Cloud — standalone or clustered hosts, SAN, S2D, SMB, SDN, SCVMM, or AD/DNS management infrastructureHyper-V Private Cloud Monitoring (Flagship)SCOM 2019 / 2022 / 2025
Azure Local (formerly Azure Stack HCI), and you run SCOMAzure Local SCOM Management PackSCOM 2022 / 2025 (Lab Preview)
Azure Local, and you want cloud-native monitoringAzure Local Azure Monitor Health ModelAzure Monitor & Azure Arc

Independent deployments

Hyper-V and Azure Local are separate products with separate management packs and different health models. If your environment hosts both, deploy them independently.


Path: Hyper-V with SCOM (Flagship Solution)

This is the fully realized, production-ready flagship solution. It consists of four core packs plus optional capability packs based on your infrastructure (Clustering, Storage, S2D, File Services, Physical Network, Network ATC, SDN, VMM, and Pure Storage).

  1. Check the prerequisites: Ensure required Microsoft base packs (Windows Server, Cluster, IIS/PowerShell) are imported.
  2. Download the release: Download the sealed production 12-pack bundle (Hyper-V-Private-Cloud-Monitoring-Deployment-1.3.8.0.zip).
  3. Follow the administration guide:
    • Import the sealed .mp packs into SCOM.
    • Configure agent proxying on all cluster nodes and Hyper-V hosts.
  4. Apply the 2-Pack Override Solution:
  5. Leverage the Central Operations Hub:
    • Run built-in operator diagnostic tasks directly from the SCOM console:
      • TestDomainHealth: Validate Active Directory secure channel and domain controllers.
      • TestDnsResolution: Verify host DNS records and SRV registrations.
      • TestPortConnectivity: Run deep fabric port tests across gateways and domain controllers.
      • TestPxeWdsHealth: Check bare-metal deployment services and TFTP/PXE listeners.
      • GetLldpNeighbor: Discover connected Top-of-Rack switch ports and chassis IDs.
      • PfcEtsCounters: Inspect RDMA PFC pause frames and QoS priority drop counters.

Path: Azure Local with SCOM

Lab preview

The Azure Local SCOM packs remain under active development in the lab and are not yet released for general production.

  1. Read the prerequisites — lists the built-in SCOM dependencies.
  2. Follow the management pack guide — development and validation guidance.
  3. Review the monitoring catalog.

Path: Azure Local with Azure Monitor

Cloud-native monitoring for Azure Local clusters using Azure Arc, Azure Monitor Insights, and native Resource Health.

  1. Read the cloud prerequisites — Arc registration, Insights enablement, DCRs, and Azure RBAC assignments.
  2. Understand the entity model.
  3. Read the health model overview.

SCOM vs. Azure Monitor (Azure Local Only)

For Azure Local, operators can choose between on-premises SCOM and cloud-native Azure Monitor:

Note: For Hyper-V Private Cloud, SCOM is the sole authoritative monitoring platform; there is no Azure Monitor dependency.


Where to find documentation

If you want to…Go to
Deploy Hyper-V monitoringHyper-V Prerequisites and Administration Guide
Download management packsHyper-V Downloads
Operate and troubleshootOperations & Troubleshooting Hub
Understand thresholds and tuningMonitoring Catalog Policy
Review architecture and designArchitecture & Reference Overview
Connect alerts to ServiceNowIntegrations
View project roadmapRoadmap

Released under the MIT License.