Merge pull request #219635 from v-ksreedevan/28Nov-ContentFreshnessHyperV

Content freshness - Hyper-V Migration Tutorial

Author: v-ccolin

articles/migrate/tutorial-migrate-hyper-v.md

@@ -59,7 +59,7 @@ For migrating Hyper-V VMs, the Migration and modernization tool installs softwar
     - The registration key is needed to register the Hyper-V host with the Migration and modernization tool.
     - The key is valid for five days after you generate it.
 
-    ![Download provider and key](./media/tutorial-migrate-hyper-v/download-provider-hyper-v.png)
+    ![Screenshot of Download provider and key.](./media/tutorial-migrate-hyper-v/download-provider-hyper-v.png)
 
 1. Copy the provider setup file and registration key file to each Hyper-V host (or cluster node) running VMs you want to replicate.  
 
@@ -71,16 +71,16 @@ Copy the provider setup file and registration key file to each Hyper-V host (or
 
 Run the provider setup file on each host, as described below:
 
-1. Click the file icon in the taskbar to open the folder where the installer file and registration key are downloaded.
+1. Select the file icon in the taskbar to open the folder where the installer file and registration key are downloaded.
 1. Select **AzureSiteRecoveryProvider.exe** file.
-    - In the provider installation wizard, ensure **On (recommended)** is checked, and then click **Next**.
+    - In the provider installation wizard, ensure **On (recommended)** is checked, and then select **Next**.
     - Select **Install** to accept the default installation folder.
     - Select **Register** to register this server in Azure Site Recovery vault.
-    - Click **Browse**.
-    - Locate the registration key and click **Open**.
-    - Click **Next**.
-    - Ensure **Connect directly to Azure Site Recovery without a proxy server** is selected, and then click **Next**.
-    - Click **Finish**.
+    - Select **Browse**.
+    - Locate the registration key and select **Open**.
+    - Select **Next**.
+    - Ensure **Connect directly to Azure Site Recovery without a proxy server** is selected, and then select **Next**.
+    - Select **Finish**.
 
 
 # [Using commands](#tab/commands) 
@@ -130,31 +130,31 @@ Run the following commands on each host, as described below:
     ```
 ---
 
-After installing the provider on hosts, go to the Azure portal and in **Discover machines**, click **Finalize registration**.
+After installing the provider on hosts, go to the Azure portal and in **Discover machines**, select **Finalize registration**.
 
- ![Finalize registration](./media/tutorial-migrate-hyper-v/finalize-registration.png) 
+ ![Screenshot of the Finalize registration screen.](./media/tutorial-migrate-hyper-v/finalize-registration.png) 
 
-It can take up to 15 minutes after finalizing registration until discovered VMs appear in the Migration and modernization tool. As VMs are discovered, the **Discovered servers** count rises.
-
- ![Discovered servers](./media/tutorial-migrate-hyper-v/discovered-servers.png)
+It can take up to 15 minutes after finalizing registration until discovered VMs appear in the Migration and modernization tile. As VMs are discovered, the **Discovered servers** count rises.
 
 ## Replicate Hyper-V VMs
 
-With discovery completed, you can begin replication of Hyper-V VMs to Azure.
+With discovery completed, you can begin the replication of Hyper-V VMs to Azure.
 
 > [!NOTE]
 > You can replicate up to 10 machines together. If you need to replicate more, then replicate them simultaneously in batches of 10.
 
 1. In the Azure Migrate project > **Servers, databases and web apps** > **Migration and modernization**, select **Replicate**.
+
 1. In **Replicate** > **Source settings** > **Are your machines virtualized?**, select **Yes, with Hyper-V**. Then click **Next: Virtual machines**.
+
 1. In **Virtual machines**, select the machines you want to replicate.
     - If you've run an assessment for the VMs, you can apply VM sizing and disk type (premium/standard) recommendations from the assessment results. To do this, in **Import migration settings from an Azure Migrate assessment?**, select the **Yes** option.
-    - If you didn't run an assessment, or you don't want to use the assessment settings, select the **No** options.
+    - If you didn't run an assessment, or you don't want to use the assessment settings, select the **No** option.
     - If you selected to use the assessment, select the VM group, and assessment name.
 
-        ![Select assessment](./media/tutorial-migrate-hyper-v/select-assessment.png)
+        ![Screenshot of the Select assessment screen.](./media/tutorial-migrate-hyper-v/select-assessment.png)
 
-1. In **Virtual machines**, search for VMs as needed, and check each VM you want to migrate. Then, click **Next: Target settings**.
+1. In **Virtual machines**, search for VMs as needed, and check each VM you want to migrate. Then, select **Next: Target settings**.
 
     :::image type="content" source="./media/tutorial-migrate-hyper-v/select-vms-inline.png" alt-text="Screenshot shows the selected VMs in the Replicate dialog box." lightbox="./media/tutorial-migrate-hyper-v/select-vms-expanded.png":::
 
@@ -167,8 +167,8 @@ With discovery completed, you can begin replication of Hyper-V VMs to Azure.
     - No infrastructure redundancy required option if you don't need either of these availability configurations for the migrated machines.
 1. In **Azure Hybrid Benefit**:
 
-    - Select **No** if you don't want to apply Azure Hybrid Benefit. Then, click **Next**.
-    - Select **Yes** if you have Windows Server machines that are covered with active Software Assurance or Windows Server subscriptions, and you want to apply the benefit to the machines you're migrating. Then click **Next**.
+    - Select **No** if you don't want to apply Azure Hybrid Benefit. Then, select **Next**.
+    - Select **Yes** if you have Windows Server machines that are covered with active Software Assurance or Windows Server subscriptions, and you want to apply the benefit to the machines you're migrating. Then select **Next**.
 
     :::image type="content" source="./media/tutorial-migrate-hyper-v/target-settings.png" alt-text="Screenshot on target settings.":::
 
@@ -178,7 +178,7 @@ With discovery completed, you can begin replication of Hyper-V VMs to Azure.
     - **OS disk**: Specify the OS (boot) disk for the VM. The OS disk is the disk that has the operating system bootloader and installer.
     - **Availability Set**: If the VM should be in an Azure availability set after migration, specify the set. The set must be in the target resource group you specify for the migration.
 
-1. In **Disks**, specify the VM disks that need to be replicated to Azure. Then click **Next**.
+1. In **Disks**, specify the VM disks that need to be replicated to Azure. Then select **Next**.
     - You can exclude disks from replication.
     - If you exclude disks, won't be present on the Azure VM after migration.
 
@@ -188,28 +188,28 @@ With discovery completed, you can begin replication of Hyper-V VMs to Azure.
 
     :::image type="content" source="./media/tutorial-migrate-vmware/tags-inline.png" alt-text="Screenshot shows the tags tab of the Replicate dialog box." lightbox="./media/tutorial-migrate-vmware/tags-expanded.png":::
 
-1. In **Review and start replication**, review the settings, and click **Replicate** to start the initial replication for the servers.
+1. In **Review and start replication**, review the settings, and select **Replicate** to start the initial replication for the servers.
 
 > [!NOTE]
 > You can update replication settings any time before replication starts, in **Manage** > **Replicating machines**. Settings can't be changed after replication starts.
 
 ## Provision for the first time
 
 If this is the first VM you're replicating in the Azure Migrate project, the Migration and modernization tool automatically provisions these resources in same resource group as the project.
+
 - **Cache storage account**: The Azure Site Recovery provider software installed on Hyper-V hosts uploads replication data for the VMs configured for replication to a storage account (known as the cache storage account, or log storage account) in your subscription. The Azure Migrate service then copies the uploaded replication data from the storage account to the replica-managed disks corresponding to the VM. The cache storage account needs to be specified while configuring replication for a VM and The Azure Migrate portal automatically creates one for the Azure Migrate project when replication is configured for the first time in the project.
 
 ## Track and monitor
 
-
-- When you click **Replicate** a Start Replication job begins.
+- When you select **Replicate**, a Start Replication job begins.
 - When the Start Replication job finishes successfully, the machines begin their initial replication to Azure.
-- After initial replication finishes, delta replication begins. Incremental changes to on-premises disks are periodically replicated to  Azure.
+- After initial replication finishes, delta replication begins. Incremental changes to on-premises disks are periodically replicated to Azure.
 
 You can track job status in the portal notifications.
 
 You can monitor replication status by clicking on **Replicating servers** in **Migration and modernization**.
-![Monitor replication](./media/tutorial-migrate-hyper-v/replicating-servers.png)
 
+![Monitor replication](./media/tutorial-migrate-hyper-v/replicating-servers.png)
 
 
 ## Run a test migration
@@ -226,21 +226,21 @@ Do a test migration as follows:
 
 1. In **Migration goals** > **Servers, databases and web apps** > **Migration and modernization**, select **Test migrated servers**.
 
-     ![Test migrated servers](./media/tutorial-migrate-hyper-v/test-migrated-servers.png)
+     ![Screenshot of Test migrated servers in Migration and modernization tile.](./media/tutorial-migrate-hyper-v/test-migrated-servers.png)
 
-1. Right-click the VM to test, and click **Test migrate**.
+1. Right-click the VM to test, and select **Test migrate**.
 
-    ![Test migration](./media/tutorial-migrate-hyper-v/test-migrate.png)
+    ![Screenshot of Test migration screen.](./media/tutorial-migrate-hyper-v/test-migrate.png)
 
 1. In **Test Migration**, select the Azure virtual network in which the Azure VM will be located after the migration. We recommend you use a non-production virtual network.
 1. The **Test migration** job starts. Monitor the job in the portal notifications.
 1. After the migration finishes, view the migrated Azure VM in **Virtual Machines** in the Azure portal. The machine name has a suffix **-Test**.
-1. After the test is done, right-click the Azure VM in **Replicating machines**, and click **Clean up test migration**.
+1. After the test is done, right-click the Azure VM in **Replications**, and select **Clean up test migration**.
 
-    ![Clean up migration](./media/tutorial-migrate-hyper-v/clean-up.png)
+    ![Screenshot of Clean up migration option.](./media/tutorial-migrate-hyper-v/clean-up.png)
     > [!NOTE]
     > You can now register your servers running SQL server with SQL VM RP to take advantage of automated patching, automated backup and simplified license management using SQL IaaS Agent Extension.
-    >- Select **Manage** > **Replicating servers** > **Machine containing SQL server** > **Compute and Network** and select **yes** to register with SQL VM RP.
+    >- Select **Manage** > **Replications** > **Machine containing SQL server** > **Compute and Network** and select **yes** to register with SQL VM RP.
     >- Select Azure Hybrid benefit for SQL Server if you have SQL Server instances that are covered with active Software Assurance or SQL Server subscriptions and you want to apply the benefit to the machines you're migrating.hs.
 
 ## Migrate VMs
@@ -252,9 +252,10 @@ After you've verified that the test migration works as expected, you can migrate
     ![Replicating servers](./media/tutorial-migrate-hyper-v/replicate-servers.png)
 
 1. In **Replicating machines**, right-click the VM > **Migrate**.
+
 1. In **Migrate** > **Shut down virtual machines and perform a planned migration with no data loss**, select **Yes** > **OK**.
     - By default Azure Migrate shuts down the on-premises VM, and runs an on-demand replication to synchronize any VM changes that occurred since the last replication occurred. This ensures no data loss.
-    - If you don't want to shut down the VM, select **No**
+    - If you don't want to shut down the VM, select **No**.
 1. A migration job starts for the VM. Track the job in Azure notifications.
 1. After the job finishes, you can view and manage the VM from the **Virtual Machines** page.