Microsoft
Microsoftanthonypstrother
There can only be one version of the Microsoft Monitoring Agent installed at a time. Version 10.20.x.x is the "Log Analytics" version of the agent that comes from Azure and is being deprecated in favor of the "Azure Monitoring Agent", the AMA. For your Log Analytics connection, you'll want to migrate from the MMA to the Azure Monitor Agent.
For SCOM communications, once the Log Analytics connection is migrated to the Azure Monitoring Agent, you'll actually want to uninstall the 10.20.x.x version of the MMA and reinstall the SCOM version of the agent that matches your current SCOM environment (2016 - 8.0.x.x, 2019 - 10.19.x.x and 2022- 10.22.x.x). Not changing versions should not affect overall SCOM monitoring, however it will allow you to keep in line with SCOM releases and manage the agent from the SCOM console (once we get them remotely manageable), including updating the agent later, which cannot be done with the 10.20.x.x agent version as it is a different code base.
What this means is that you'll end up running two monitoring agents side-by-side:
Keep in mind that the AMA for on-prem machines will also require the Azure Arc agent to be installed, so you may end up with three distinct agents running in parallel depending on where your servers live.
As far as where/how to get the AMA, there are several methods outlined in the docs here: Install and manage Azure Monitor Agent - Azure Monitor | Microsoft Learn. For manual testing, you may wish to look at this one in particular: Set up the Azure Monitor agent on Windows client devices - Azure Monitor | Microsoft Learn
The SCOM version of the MMA can be obtained directly on your management servers under "%ProgramFiles%\Microsoft System Center\Operations Manager\Server\AgentManagement\amd64", and installed manually/through automation, you will not be able to replace the 10.20.x.x version of the agent through the SCOM Console using normal methods.