Merge pull request #291873 from v-sreedevank/12Dec-SFIVMware

SFI Global admin - VMware update

Author: prmerger-automator[bot]

articles/migrate/vmware/tutorial-migrate-vmware-agent.md

@@ -1,9 +1,8 @@
 ---
 title: Migrate VMware vSphere VMs with agent-based the Migration and modernization tool
 description: Learn how to run an agent-based migration of VMware vSphere VMs with Azure Migrate.
-author: vijain
-ms.author: vijain
-ms.manager: kmadnani
+author: piyushdhore-microsoft 
+ms.author: piyushdhore
 ms.topic: tutorial
 ms.service: azure-migrate
 ms.date: 09/26/2024
@@ -70,9 +69,6 @@ Assign the Virtual Machine Contributor role to the account, so that you have per
 
 If you are following the least privilege principle, assign the **Application Developer** Microsoft Entra role to the user registering the Replication Appliance. Follow the [Assign administrator and non-administrator roles to users with Microsoft Entra ID](../../active-directory/fundamentals/active-directory-users-assign-role-azure-portal.md) guide to do so.
 
-> [!IMPORTANT]
-> If the user registering the Replication Appliance is a Microsoft Entra Global Administrator, that user already has the required permissions.
-
 ### Set up an Azure network
 
 [Set up an Azure network](/azure/virtual-network/manage-virtual-network). On-premises machines are replicated to Azure managed disks. When you fail over to Azure for migration, Azure VMs are created from these managed disks, and joined to the Azure network you set up.