Skip to content
EOL Watch
Search itemsOpen menu

AzureRetirement

Azure Monitor SCOM Managed Instance retirement

Retirement date for Azure Monitor SCOM Managed Instance: 30 Sep 2026. After that date, customers can no longer access the service.

Retired , 30 Sep 2026

What breaks

Customers that run Azure Monitor SCOM Managed Instance (SCOM MI) are affected. After the retirement date, customers are no longer able to access the service. Both transition paths in the source require deleting the existing SCOM MI instance.

What to do

  1. To monitor on-premises workloads, transition to Operations Manager on-premises: delete the existing SCOM MI instance and re-deploy SCOM on-premises (hosted in on-premises datacenters or in Azure) using these steps.
  2. To monitor Azure-hosted or Azure Arc-enabled workloads, transition to Azure Monitor and delete the existing SCOM MI instance.
  3. For the Azure Monitor path, obtain a list of the rules and monitors in the SCOM MI Management Packs in use.
  4. Determine the equivalent of those rules and monitors in Azure Monitor Data Collection Rules (DCR): create a DCR for each SCOM MP monitor in use and integrate it with Azure Monitor VM Insights Alerts.
  5. See the Microsoft retirement documentation for more details.

Replacement

Operations Manager on-premises or Azure Monitor

Sources

Last checked against the first source in this list on .

Found an error? Report it

The text on this page is drafted with AI assistance from the vendor's text, checked against the official source and approved by a person before it is published. How items are written

Last checked · Added · Changelog for this item