What are the potential impacts of migrating Change Tracking and Inventory from Log Analytics Agent to Azure Monitor Agent?

Question

Hi all,

I received an email (https://learn.microsoft.com/en-us/azure/automation/change-tracking/guidance-migration-log-analytics-monitoring-agent?tabs=ps-policy%2Climit-single-vm) to migrate our change tracking and inventory from using log analytics to Azure Monitoring Agent instead. My question would be are there any effects I need to be aware of before we transition from Log Analytics workspace to Azure Monitoring Agent? (i.e. would anything break, price increase/decrease in using AMA etc.). I just want to make sure after running the PowerShell script Microsoft provided for transitioning to AMA that we do not get hit with any surprises just to be safe.

The code in question (https://github.com/Azure/ChangeTrackingAndInventory/blob/main/MigrateToChangeTrackingAndInventoryUsingAMA/CTAndIMigrationFromMMAToAMA.ps1)

From my observation, the code will simply do the following below where it retrieves a list of Azure VMs and Arc-enabled non-Azure machines that are onboarded to a specified Log Analytics Workspace using the MMA agent and migrates the configurations for Change Tracking & Inventory from the older MMA agent to the newer AMA agent so I am assuming it should not affect my resources negatively other than to just switch to using AMA, would I be correct to assume that?

migrate all Azure Machines and Arc enabled Non-Azure Machines onboarded to LA Agent Change Tracking solution for the Input Log Analytics Workspace to the Change Tracking using AMA agent for the Output Log Analytics Workspace

Answer 1

Hello Aaron Chan,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you would like to know the potential impacts of migrating Change Tracking and Inventory from Log Analytics Agent to Azure Monitor Agent.

There are many things to put into consideration if you would like to be certain of potential impacts and mitigations, however the best practices are here below:

Impacts:

• Disruption to Operations
• Data Integrity and Security Risks
• User Resistance
• Compatibility Issues
• Cost Overruns

Mitigate Impacts with the following:

• Mitigate Impacts
• Thorough Planning
• Incremental Implementation
• Stakeholder Engagement
• Data Backup and Security Measures
• Training and Support
• Compatibility Testing
• Budget Management

To read more or study compressively, use the below links that cover the above:

• https://learn.microsoft.com/en-us/power-bi/guidance/fabric-adoption-roadmap-change-management
• https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/get-started/migrate

I hope this is helpful! Do not hesitate to let me know if you have any other questions.

---

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.