Mr.PlanB Logo
    Infrastructure Monitoring Ledger 2026
    Ledger
    Infrastructure Monitoring Ledger 2026

    Microsoft System Center Operations Manager: Monitoring Ledger 2026

    Microsoft keeps SCOM as a long-supported on-premises engine for Windows estates while steering new monitoring to Azure Monitor and Arc.

    Edition October 4, 20266 min read

    Part of the Infrastructure Monitoring Ledger (edition 2026-10-04). How the scores work: methodology.

    Snapshot

    • Tier: Legacy enterprise
    • Owner: Microsoft Corporation (public company); SCOM part of System Center since 2007
    • Licence model: System Center Standard or Datacenter per core (16-core minimum per managed server); no standalone SCOM licence
    • Products scored: System Center Operations Manager 2016, 2019, 2022 and 2025 on-premises; Azure Monitor SCOM Managed Instance not scored
    • Latest release: SCOM 2022 UR4, 2026-09-25; SCOM 2025 UR1, 2025-12-11
    • Next signal: Further SCOM 2025 update rollups (UR2), no date; mainstream support to 2030-01-09, extended to 2035-01-10
    • Archetype: Windows estate maintenance incumbent
    • Evidence grade: A. Microsoft Learn pages, KB articles and lifecycle records cover every cell; the AI evidence has date conflicts with the release record.

    Scorecard

    DimensionScoreDirection
    Capability today67.8 / 100higher is better
    Momentum since end of 2022+0.0 pointshigher is better
    Credibility16.5 / 25higher is better
    Commercial risk10.0 / 25lower is better
    Technical lock-in16.0 / 25lower is better
    Integrator fit11.5 / 20higher is better
    AI leverage3.5 / 20higher is better
    Ledger Index54.0 / 100balanced weights

    Capability by domain

    Scores 0 to 5 against fixed anchors; total is weighted to 100.

    Domain (weight)201620192022Today
    Server, virtualization and storage (12)3.53.53.53.5
    Network monitoring (12)2.52.52.52.5
    Application and service monitoring (10)4444
    Data collection and scale (12)3.5444
    Alerting and event management (12)4444
    Visualisation and reporting (8)33.53.53.5
    Logs and traces (8)3333
    Automation and remediation (8)3.5444
    Security and compliance (8)33.544
    New-platform support (VMware exit) (10)11.51.51.5
    Total / 10062.467.067.867.8

    Year by year: 2016: 62.4 · 2017: 62.4 · 2018: 63.2 · 2019: 67.0 · 2020: 67.0 · 2021: 67.0 · 2022: 67.8 · 2023: 67.8 · 2024: 67.8 · 2025: 67.8 · 2026: 67.8

    What moved the score

    YearDomainChangePointsTrigger
    2018Automation and remediation3.5 → 4+0.8SCOM 1801: REST API for alerts and maintenance mode; ServiceNow only via partner connectors
    2019Data collection and scale3.5 → 4+1.2SCOM 2019: SQL Always On for all databases; Linux management-server failover
    2019New-platform support (VMware exit)1 → 1.5+1.0Nutanix-built AHV management pack; Kubernetes only through Azure Arc; no Proxmox, XCP-ng or KubeVirt to 2025
    2019Security and compliance3 → 3.5+0.8SCOM 2019 UR1: group managed service accounts remove static passwords; TLS 1.2 enforced
    2019Visualisation and reporting3 → 3.5+0.8SCOM 2019: HTML5 web console with alert, performance, topology and SLA widgets
    2022Security and compliance3.5 → 4+0.8SCOM 2022: custom RBAC roles, least-privilege agent accounts, SHA2; change tracking since 2019 UR2; no multi-tenancy

    Direction, 2023 to 2026

    Each item carries one theme and one driver (V vision, C customer need, M market window, U upstream, P portfolio).

    DateItemThemeDriver
    2023-02SCOM 2022 UR1: SQL Server 2022 supportD4 Collection and scaleU
    2023-11Azure Monitor SCOM Managed Instance GAD12 Packaging and licensingV
    2023-11SCOM 2022 UR2: Linux agents on OpenSSL 3.0 (RHEL 9, Ubuntu 22.04)D1 Server and virtualizationU
    2024-04SCOM 2019 leaves mainstream supportD12 Packaging and licensingP
    2024-11SCOM 2025 GA: Windows Server 2025 day-0; Kerberos replaces CredSSP and NTLMD9 SecurityU
    2024-11SCOM 2025 drops Service Provider FoundationD12 Packaging and licensingP
    2025-03GPU workload management pack (AI evidence)D1 Server and virtualizationM
    2025-06SCOM Managed Instance retirement announced for 2026-09-30D12 Packaging and licensingP
    2025-12SCOM 2025 UR1: TLS 1.3, SQL Server 2025, RHEL 10 and Debian 13 agentsD9 SecurityU
    2026-09SCOM 2022 UR4 maintenance rollupD4 Collection and scaleC
    • Centre of gravity: Packaging and licensing (4), Collection and scale (2), Server and virtualization (2)
    • Driver mix: Vision 10%, Customer need 10%, Market window 10%, Upstream 40%, Portfolio 30%

    Credibility: 16.5 / 25

    CriterionScoreBasis
    Cadence3.5Long-term releases 2016, 2019, 2022, 2024 with update rollups; semi-annual channel dropped 2019; 2022 UR3 to UR4 took two years
    Roadmap transparency3Public what's-new pages and KB article per rollup; no public roadmap
    Say-do4.514 of 15 items 2023-2026 shipped on time; SCOM Managed Instance dropped after GA
    Velocity2Rollups mostly fixes, OS and SQL support; SCOM 2025 adds TLS 1.3 and Kerberos-only authentication
    Lifecycle stability3.5Ten-year support per release, in-place upgrades; APM deprecated, Service Provider Foundation and UNIX agents removed

    Say-do record, 2023 to 2026: 15 items 2023-2026: 14 shipped on time, mostly rollups and protocol support; 1 dropped: Azure Monitor SCOM Managed Instance, GA 2023-11, retirement 2026-09-30.

    Commercial risk: 10.0 / 25 (lower is better)

    CriterionScoreBasis
    Price and licence volatility1Per-core System Center licence unchanged since 2016; only the Managed Instance PaaS came and went
    Purchase constraints3.5Sold only inside System Center suites; all cores licensed, 16-core minimum per server
    Channel and access1.5Docs and rollups public; sold through Enterprise Agreements and CSP partners
    Owner stability2Microsoft stable, but strategy steers to Azure Monitor and Arc; Managed Instance retired 2026
    Cost of staying supported2Ten-year support windows; no paid feature removals found

    Security record of the product itself: No SCOM flaw on the CISA KEV list (the security record). OMIGOD (CVE-2021-38647) in the OMI component used by SCOM Linux agents was patched 2021-09-14 and added to KEV 2021-11-03; outside 2023-2026, so no deduction.

    Technical lock-in: 16.0 / 25 (lower is better)

    CriterionScoreBasis
    Formats3.5Management pack XML schema documented, but sealed packs are signed binaries; data in SQL Server
    Export path3.5PowerShell, REST and SQL warehouse readable; Microsoft states no tool converts packs to other products
    Stack coupling4.5Requires Windows Server, Active Directory, SQL Server and Microsoft agents; agents cannot feed OpenTelemetry
    Hardware / cloud coupling0.5Any hardware; runs fully offline
    Skills and tooling coupling4Pack authoring needs VSAE or Silect tools and health-model skills; dedicated certifications retired 2021

    Integrator fit: 11.5 / 20

    CriterionScoreBasis
    Partner programme openness4.5Microsoft AI Cloud Partner Program; large third-party pack ecosystem (SquaredUp, NiCE, OpsLogix, hardware OEMs)
    Multi-tenancy and self-service1.5Single tenant per management group; scoped user roles only; Service Provider Foundation dropped in SCOM 2025
    API and infrastructure-as-code3PowerShell module, REST API and .NET SDK; no Terraform provider; community Ansible only
    Skills and certification2.5System Center certifications retired 2021; active community (SCOMathon, Kevin Holman blog)

    AI leverage: 3.5 / 20

    StrandTodayLatest step
    AIOps on monitoring data0.52025: SCOM 2025: GPU workload management pack per AI evidence; no ML baselines on-premises
    AI platform stack0none
    AI-assisted operations12016: SCOM 2016: rule-based Tune Management Packs alert-noise analysis
    Agent openness22018: SCOM 1801: REST API; only a community MCP server (v0.1.3) since 2025

    AI say-do: 2 tracked, 1 GA (GPU management pack, on time), 1 dropped (SCOM Managed Instance, whose anomaly detection was cloud-only and is retired). On-premises SCOM has no ML, no assistant and no official MCP server.

    Reading

    Microsoft keeps SCOM as a long-supported on-premises engine for Windows estates while steering new monitoring to Azure Monitor and Arc. Since 2023 the record is servicing: rollups and protocol hardening ship on time, no new monitoring domain arrived, and the cloud Managed Instance was retired after two years. Buyers get deep Windows and Microsoft-application health models with support to 2035, at the cost of weak network and non-Microsoft hypervisor coverage and a heavy Windows, AD and SQL Server stack.

    Open questions and evidence caveats

    • The AI evidence dates SCOM 2025 GA and the GPU pack to 2025-03 and Managed Instance retirement to 2025-09; the release record says 2024-11 and 2026-09-30. release record used.
    • APM is described as deprecated in SCOM 2025 but not removed, so apps stays at 4.
    • VMware, Nutanix, ServiceNow and much hardware health come from third-party or partner packs, scored as not built in.

    Related reading

    More from Infrastructure Monitoring Ledger 2026