Merge pull request #103926 from bsiva/master

Correcting article.

Author: PRMerger17

articles/migrate/tutorial-migrate-physical-virtual-machines.md

@@ -56,9 +56,6 @@ Before you begin this tutorial, you should:
 Set up Azure permissions before you can migrate with Azure Migrate Server Migration.
 
 - **Create a project**: Your Azure account needs permissions to create an Azure Migrate project. 
-- **Register the Azure Migrate replication appliance**: The replication appliance creates and registers an Azure Active Directory app in your Azure account. Delegate permissions for this.
-- **Create Key Vault**: To migrate machines, Azure Migrate creates a Key Vault in the resource group, to manage access keys to the replication storage account in your subscription. To create the vault, you need role assignment permissions on the resource group in which the Azure Migrate project resides. 
-
 
 ### Assign permissions to create project
 
@@ -68,51 +65,14 @@ Set up Azure permissions before you can migrate with Azure Migrate Server Migrat
     - If you just created a free Azure account, you're the owner of your subscription.
     - If you're not the subscription owner, work with the owner to assign the role.
 
-### Assign permissions to register the replication appliance
-
-For agent-based migration, delegate permissions for Azure Migrate Server Migration to create and register an Azure AD app in your account. You can assign permissions using one of the following methods:
-
-- A tenant/global admin can grant permissions to users in the tenant, to create and register Azure AD apps.
-- A tenant/global admin can assign the Application Developer role (that has the permissions) to the account.
-
-It's worth noting that:
-
-- The apps don't have any other access permissions on the subscription other than those described above.
-- You only need these permissions when you register a new replication appliance. You can remove the permissions after the replication appliance is set up. 
-
-
-#### Grant account permissions
-
-The tenant/global admin can grant permissions as follows
-
-1. In Azure AD, the tenant/global admin should navigate to **Azure Active Directory** > **Users** > **User Settings**.
-2. The admin should set **App registrations** to **Yes**.
-
-    ![Azure AD permissions](./media/tutorial-migrate-physical-virtual-machines/aad.png)
-
-> [!NOTE]
-> This is a default setting that isn't sensitive. [Learn more](https://docs.microsoft.com/azure/active-directory/develop/active-directory-how-applications-are-added#who-has-permission-to-add-applications-to-my-azure-ad-instance).
-
-#### Assign Application Developer role 
-
-The tenant/global admin can assign the Application Developer role to an account. [Learn more](../active-directory/fundamentals/active-directory-users-assign-role-azure-portal.md).
-
-## Assign permissions to create Key Vault
-
-Assign role assignment permissions on the resource group in which the Azure Migrate project resides, as follows:
-
-1. In the resource group in the Azure portal, select **Access control (IAM)**.
-2. In **Check access**, find the relevant account, and click it to view permissions. You need **Owner** (or **Contributor** and **User Access Administrator**) permissions.
-3. If you don't have the required permissions, request them from the resource group owner. 
-
 ## Prepare for migration
 
 ### Check machine requirements for migration
 
 Make sure machines comply with requirements for migration to Azure. 
 
 > [!NOTE]
-> Agent-based migration with Azure Migrate Server Migration is based on features of the Azure Site Recovery service. Some requirements might link to Site Recovery documentation.
+> Agent-based migration with Azure Migrate Server Migration, has the same replication architecture as the agent based disaster recovery feature of the Azure Site Recovery service, and some of the components used share the same code base. Some requirements might link to Site Recovery documentation.
 
 1. [Verify](migrate-support-matrix-physical-migration.md#physical-server-requirements) physical server requirements.
 2. Verify VM settings. On-premises machines that you replicate to Azure must comply with [Azure VM requirements](migrate-support-matrix-physical-migration.md#azure-vm-requirements).