Tips when migrating to Azure Monitor Agent from Log Analytics agent

Dear Jamesdld23 thank you for bringing up that important topic and guidance.

I am quite pessimistic that customers will be able and aware for this change needed. 

Even more as I believe Microsoft still allows the deployment of the log analytics agent. 

Can you confirm?

I would strongly plea to do everything possible so that this is prevented. 

If not changed Windows Admin Center still deploys old methods on Arc Enabled Servers. 

Afaik we have inventory and change tracking, both parts of Automanage. 

These also used to used the log analytics agent, but as I have heard they could use the AMA now. 

Summary:

What about the old these deployments for change tracking and inventory? 

Does a blogpost exist how to migrate these?

What method did and now does Automanage use when deploying Monitoring, Change Tracking and Inventory, old Update Management ? 

Have the methods to onboard these Services been Updated to prevent the deployment of the log analytics agent in the Portal 

Have the methods been updated throughout Windows Admin Center when deploying the services? 

How could Microsoft assist to make this Migration easier through AI and automation, including removal of the old agent and a dashboard. There's one page to see whether a VM uses the old or new agent. 

Thank you for your time and consideration, your thoughts on this and further internal checks with the PG and owners. 

My reply might be alarming, but as of today I believe it will be very hard to execute the retirement policy, due to the complexity and mentioned points.