Connecting SCOM 2022 to Azure Log Analytics not working

Question

Hello there,

We are trying to set this up in SCOM 2022: https://learn.microsoft.com/en-us/services-hub/unified/health/setup-config-log-analytics-scom

However, after signing in to azure and select the Log Analytics workspace nothing happens. The connected MG list stays empty.

It seems this is still supported as the documentation is there, as well as the log analytics connection pane in SCOM 2022.

Any ideas why this is not working?

Thank you.

Answer 1

Hi Christian,

what you are seeing is confusing, but there is an important detail here:

The SCOM 2022 pane for connecting a management group to Log Analytics is based on the older legacy integration model. Microsoft still mentions the connected management group scenario in its hybrid monitoring guidance, but it also states that this method requires the legacy agent, does not use Data Collection Rules (DCRs), and does not support newer Azure Monitor capabilities such as VM Insights unless the machines are connected to Azure Monitor directly.

That is why I would not recommend investing much more time in troubleshooting this wizard for a new setup.

The more important point is that Microsoft’s strategic direction is now Azure Monitor Agent (AMA). Microsoft says AMA replaces the Log Analytics / MMA agent and uses DCRs for data collection. It also notes that the old Log Analytics agent was retired on 31 August 2024, and that cloud ingestion for the legacy agent can be shut down any time after 2 March 2026.

So the practical recommendation is:

• Keep SCOM 2022 for what it does well: management packs, health model, alerts, and on-premises workload monitoring. Microsoft’s hybrid guidance explicitly supports running SCOM and Azure Monitor side by side during transition.
• If your goal is to get server logs / events / performance data into Log Analytics, connect the servers to Azure using Azure Arc if needed, install Azure Monitor Agent, and configure collection with DCRs. Microsoft documents AMA as the current agent model for Azure Monitor.
• In other words: for a new implementation, use SCOM + AMA, not the old "connect SCOM management group to Log Analytics" approach.

So my answer would be:

Yes, the old pane and older documentation still exist, but this is legacy technology and no longer the recommended direction. If the goal is Azure Log Analytics integration today, the better next step is to onboard the monitored servers to AMA + DCRs and keep SCOM for classic monitoring.

I would suggest not spending too much more time on the connected management group wizard unless there is a very specific legacy requirement to keep that exact model.

Best Regards
Stoyan

---

"If my response was useful, please consider marking it as the answer. It keeps the forum clean, structured, and more helpful for everyone. Thank you for supporting the community."

Answer 2

The documentation describes how to connect an existing SCOM management group and its agents to an Azure Log Analytics workspace and then verify that connection from both sides.

From the documented flow, the connection is established and visible in Azure only after all of the following are true:

1. In the SCOM Administration console, under Administration → Operations Management Suite → Connection, the management group is successfully registered to the selected Log Analytics workspace by completing the Register to Operations Management Suite wizard.
2. After registration, in the same SCOM console area, at least one computer or group is explicitly opted in:
   • Go to Administration → Operations Management Suite → Connection.
   • In the Actions pane, select Add a Computer/Group.
   • Choose Windows Computer or Groups, clear the filter if needed, and add the desired objects.
3. The SCOM agents on those computers meet the minimum version requirements for Log Analytics integration (for example, SCOM 2012 SP1/R2 agents at the documented update rollup levels, or the Microsoft Monitoring Agent when multi-homing is used) and are able to send data to the SCOM management server.
4. The SCOM management server can reach Azure Log Analytics directly or via the Log Analytics/OMS Gateway, depending on the chosen connectivity method:
   • Agent Only or SCOM method if the management server has internet access.
   • Agent + Log Analytics Gateway if internet access is restricted and a gateway is used.

Only after these conditions are met does the Log Analytics workspace show the SCOM management group under Advanced Settings → Connected Sources → System Center. If the connected management group list in Azure remains empty, the issue is typically one of the following, based on the documented behavior:

• The registration step in SCOM did not complete successfully, so the management group was never associated with the workspace.
• No agents/computers were opted in under Add a Computer/Group, so no data is flowing from SCOM to Log Analytics.
• Network connectivity from the SCOM management server (or gateway) to Azure Log Analytics is blocked, preventing the management group from completing registration and sending data.

Verifying and repeating the documented registration steps in SCOM, ensuring at least one computer is opted in, and confirming connectivity (directly or via the Log Analytics Gateway, depending on the selected scenario) are required to make the management group appear in the Connected Management Groups list in the workspace.

---

References:

• Setup and configure Log Analytics using SCOM
• Establishing connectivity to Azure Log Analytics
• Log Analytics Gateway for Azure Monitor Setup