question

@Anchalgupta-2608, Based on my research, there are far fewer cases left in modern enterprises where SMB1 is the only option. Some legit reasons:
1. You’re still running XP or WS2003 under a custom support agreement.
2. You have old management software that demands admins browse via the so-called ‘network' aka 'network neighborhood’ master browser list.
3. You run old multi-function printers with old firmware in order to “scan to share”.
https://techcommunity.microsoft.com/t5/storage-at-microsoft/stop-using-smb1/ba-p/425858

For SCOM, after researching, I didn't find any article mention the impact.

To double confirm, we can capture network trace on SCOM server or enable auditing mentioned in the following link: to check
https://azurecloudai.blog/2018/12/17/step-by-step-safely-disabling-smb-v1-from-your-production-environment/
Note: Non-Microsoft link, just for the reference.

Hope it can help.

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.