updated the info as per PR - 289878

Author: SnehaSudhirG

articles/update-manager/migration-overview.md

@@ -4,7 +4,7 @@ description: A guidance overview on migration from Automation Update Management
 author: snehasudhirG
 ms.service: azure-update-manager
 ms.topic: overview
-ms.date: 08/01/2024
+ms.date: 12/06/2024
 ms.author: sudhirsneha
 ---
 
@@ -17,12 +17,12 @@ This article provides guidance to move virtual machines from Automation Update M
 Azure Update Manager provides a SaaS solution to manage and govern software updates to Windows and Linux machines across Azure, on-premises, and multicloud environments. It's an evolution of [Azure Automation Update management solution](../automation/update-management/overview.md) with new features and functionality, for assessment and deployment of software updates on a single machine or on multiple machines at scale.    
 
 > [!Note]
-> - On 31 August 2024, both Azure Automation Update Management and the Log Analytics agent it uses [will be retired](https://azure.microsoft.com/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/). Therefore, if you are using the Azure Automation Update Management solution, we recommend that you move to Azure Update Manager for your software update needs. Follow guidance in this document to move your machines and schedules from Automation Update Management to Azure Update Manager. For more information, see the [FAQs on retirement](https://aka.ms/aum-migration-faqs) You can [sign up](https://aka.ms/AUMLive) for monthly live sessions on migration including Q&A sessions.   
-> - If you are using Azure Automation Update Management Solution, we recommend that you don't remove MMA agents from the machines without completing the migration to Azure Update Manager for the machine's patch management needs. If you remove the MMA agent from the machine without moving to Azure Update Manager, it will break the patching workflows for that machine.      
+> - On 31 August 2024, both Azure Automation Update Management and the Log Analytics agent it uses [have retired](https://azure.microsoft.com/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/). If you are still using the Azure Automation Update Management solution, we recommend that you move to Azure Update Manager for your software update needs. Follow the guidance in this document to move your machines and schedules from Automation Update Management to Azure Update Manager. For more information, see the [FAQs on retirement](https://aka.ms/aum-migration-faqs).   
+> - If you are still using Azure Automation Update Management Solution, we recommend that you don't remove the the Microsoft Monitoring Agent (MMA) agents from the machines before completing the migration to Azure Update Manager as the migration tools expect the agent to be installed on the machines to be migrated. Additionally, if you remove the MMA agent from the machine before moving to Azure Update Manager, it will break the Automation Update Management patching workflows for that machine.      
 
-For the Azure Update Manager, both AMA and MMA aren't a requirement to manage software update workflows as it relies on the Microsoft Azure VM Agent for Azure VMs and Azure connected machine agent for Arc-enabled servers. When you perform an update operation for the first time on a machine, an extension is pushed to the machine, and it interacts with the agents to assess missing updates and install updates.     
+Azure Update Manager has no dependency on either the Azure Monitor Agent(AMA) or MMA agents. as it relies on the [Microsoft Azure Windows VM Agent](https://learn.microsoft.com/azure/virtual-machines/extensions/agent-windows) or the [Microsoft Azure Linux VM Agent](https://learn.microsoft.com/azure/virtual-machines/extensions/agent-linux) for Azure VMs and the [Azure connected machine agent](https://learn.microsoft.com/azure/azure-arc/servers/agent-overview) for Arc-enabled servers. When you perform an update operation for the first time on a machine, an extension is pushed to the machine, and it interacts with the agents to assess missing updates and install updates.      
 
-We provide three methods to move from Automation Update Management to Azure Update Manager which are explained in detail:   
+We provide three methods to move from Automation Update Management to Azure Update Manager which are explained in detail in the links below:   
 - [Portal migration tool](migration-using-portal.md)  
 - [Migration runbook scripts](migration-using-runbook-scripts.md)  
 - [Manual migration](migration-manual.md)