Merge pull request #306506 from Dhananjayanr98/patch-21

Update snapshot guidance for Azure Migrate replication

Author: prmerger-automator[bot]

articles/migrate/concepts-vmware-agentless-migration.md

@@ -37,7 +37,8 @@ After the migration is successful and the VM restarts in Azure, ensure that you
 ## Replication cycles
 
 > [!NOTE]
-> Be sure to check for snapshots present from earlier replication attempts or from partner apps. You can't enable change tracking on the VM if snapshots are already present for the VM. Delete the existing snapshots or enable CBT on the VM.
+> Be sure to check for any existing snapshots on the VM from earlier replication attempts, partner apps, or active backup tools (e.g., VEEAM), as this will block agentless replication setup in Azure Migrate.
+> Snapshot-based backups conflict with Azure Migrate’s agentless change tracking and replication process and should not be used concurrently.
 
 A replication cycle is the periodic process of transferring data from an on-premises environment to Azure managed disks. A full replication cycle consists of the following steps: