Retirement: Azure Monitor SCOM Managed Instance will be retired on Sep 30, 2026

After September 30, 2026, customers will no longer be able to access the service. Please see our [retirement documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/scom-manage-instance/overview) for more details. **Recommended action** If your goal is to monitor on-premises workloads, please transition to [Operations Manager](https://learn.microsoft.com/system-center/scom/manage-operations-guide-overview?view=sc-om-2025)on-premises. You would need to delete your existing SCOM MI instance and re-deploy SCOM on-premises (hosted on on-premises datacenters or in Azure) using the steps mentioned [here](https://learn.microsoft.com/system-center/scom/get-started?view=sc-om-2025). If your goal is to monitor Azure-hosted or Azure Arc-enabled workloads, please transition to [Azure Monitor](https://learn.microsoft.com/en-us/azure/azure-monitor/fundamentals/overview). You would need to delete your existing SCOM MI instance, obtain a list of rules and monitors in the SCOM MI Management Packs (MP) that you are currently using, and determine their equivalence in Azure Monitor [Data Collection Rules](https://learn.microsoft.com/en-us/azure/azure-monitor/data-collection/data-collection-rule-overview) (DCR) by creating a DCR for each SCOM MP monitor you are using and integrating that with Azure Monitor VM Insights Alerts.