Hi AzurePro,
Thank you for the clarification. The reference to firewalls includes any centralized firewalls or implicit configurations, such as Azure Policies or custom route tables, that might block outbound connectivity. Even if no Network Security Group (NSG) or explicit firewall is applied to the SCOM MI subnet, it is important to check for these. Start by reviewing the Effective Routes for the subnet to ensure there are no misconfigured routes redirecting traffic to a non-existent device or blocking internet access. Additionally, verify that DNS resolution is working for the specific Azure endpoints required by SCOM MI, including management.azure.com, <YourRegion>.servicebus.windows.net, and nexus.microsoft.com. Use a VM in the same subnet to run 'Test-NetConnection' to confirm that both DNS resolution and port 443 connectivity to these endpoints are successful. If these checks pass, use the Azure Network Watcher tool or review the validation logs from the SCOM MI deployment blade for more detailed insights into any connectivity issues. Let me know if you need further guidance.
Kindly follow for reference:
https://learn.microsoft.com/en-us/azure/azure-monitor/scom-manage-instance/troubleshoot-scom-managed-instance
I hope this information is helpful.
If the answer is helpful, please click "Accept Answer" and kindly upvote it.