Merge pull request #17296 from v-sissondan/migrate-march-changes

Azure Migrate 3/07 changes

Author: JillGrant615

azure-local/migrate/migrate-faq.yml

@@ -6,7 +6,7 @@ metadata:
   author: alkohli
   ms.author: alkohli
   ms.service: azure-local
-  ms.date: 02/10/2025
+  ms.date: 03/07/2025
 
 
 title: FAQ - Migration of Hyper-V and VMware VMs to Azure Local using Azure Migrate (preview)
@@ -115,6 +115,9 @@ sections:
 
           When the VM is migrated, it will be created as a native Azure Arc virtual machine in the Azure Local instance. Removing the Azure Connected Machine Agent from the source VMs before migration ensures that the migrated VM is the only valid projection of the virtual machine in Azure.
 
+          ### How can I throttle the bandwidth used for replicating and migrating VMs with Azure Migrate?
+
+          See the FAQ at [Common Questions About the Migration and Modernization Tool](/azure/migrate/common-questions-server-migration#how-do-i-throttle-replication-when-using-the-azure-migrate-appliance-for-agentless-vmware-replication) for details on throttling replication and migration bandwidth.
         
           ## [VMware VMs only](#tab/vmware-vms)
           

azure-local/migrate/migrate-vmware-requirements.md

@@ -3,7 +3,7 @@ title: Review requirements for VMware VM migration to Azure Local using Azure Mi
 description: Learn the system requirements for VMware migration to Azure Local using Azure Migrate (preview).
 author: alkohli
 ms.topic: how-to
-ms.date: 02/10/2025
+ms.date: 03/11/2025
 ms.author: alkohli
 ms.custom: references_regions
 ---
@@ -63,9 +63,11 @@ For any subscriptions hosting resources used in migration, such as Azure Migrate
 
 ## Source VMware server requirements
 
-- The source VMware server used for migration should have sufficient resources to create a Windows Server 2022 VM with a minimum of 16 GB memory, 80 GB disk, and 8 vCPUs.
+- The source VMware server used for migration should have sufficient resources to create a Windows Server 2022 VM with a minimum of 16 GB memory, 80 GB disk, and 8 vCPUs. For more information, see [Enable your VMware vCenter resources in Azure](/azure/azure-arc/vmware-vsphere/browse-and-enable-vcenter-resources-in-azure).
 
-- In this release, you can only migrate VMs that have disks attached to the VMFS Datastores. If the VM disks aren't attached to the VMFS Datastore, the disks can’t be migrated
+- Ensure that adequate vCenter Server permissions are met. For more information, see [VMware vSphere agentless requirements](/azure/migrate/vmware/migrate-support-matrix-vmware-migration#vmware-vsphere-requirements-agentless).
+
+- In this release, you can only migrate VMs that have disks attached to the VMFS Datastores. If the VM disks aren't attached to the VMFS Datastore, the disks can’t be migrated.
 
 - Before you begin, for all VMware VMs, bring all the disks online and persist the drive letter. For more information, see how to [configure a SAN policy](/azure/migrate/prepare-for-migration#configure-san-policy) to bring the disks online.