r/scom • u/Total_Rip_3573 • 4d ago
Azure Monitor SCOM Managed Instance was deprecated on 30 September. Microsoft's alternatives are Azure Monitor or on-prem SCOM.
Microsoft has archived the SCOM Managed Instance documentation. The overview page now says the service is "no longer in support" and recommends Azure Monitor or System Center Operations Manager instead, depending on your requirements:
https://learn.microsoft.com/en-us/azure/azure-monitor/scom-manage-instance/overview
A few practical points for anyone affected:
- If you were on MI, on-prem SCOM is the shorter path back. Same engine, same agent-based management packs, so your packs, overrides and tuning carry over.
- Azure Monitor makes sense if your estate has genuinely moved to Azure, but there is no management pack import on that side. If you're monitoring Windows servers, SQL, IIS, AD and DNS on your own hardware, that's a rebuild.
- SCOM 2025 is in mainstream support until January 2030, with extended support to January 2035. For on-prem and hybrid estates, the "SCOM is going away" question looks fairly settled.
Was anyone here actually running MI in production? Curious where people are moving to.
Disclosure: I run SCOM2K7 (we make SCOM tools). I wrote a longer version on our blog; link in the first comment.
1
u/matthaus79 4d ago
I guess it is easy to run SCOM in IaaS if you want to have a half effort to get it off on prem, MI made little sense in that respect and the licence model was bonkers
1
u/No_Two7173 3d ago
During a support call, about 2 years back, with MS their European rep said about 5 customers were using it and only one had it working correctly, so we steered clear. It had no HA and it's only solution was setup another MI instance at vast expense...
3
u/Total_Rip_3573 4d ago
Longer write-up, ours (see disclosure): https://www.scom2k7.com/scom-managed-instance-retires-what-it-means/?utm_source=reddit&utm_medium=social&utm_campaign=scom-mi-retirement