Merge pull request #202132 from v-ksreedevan/20Jun-Image

Image update and UI changes

Author: v-ccolin

articles/migrate/media/tutorial-migrate-hyper-v/disks.png

@@ -151,18 +151,18 @@ The first step of migration is to set up the replication appliance. To set up th
 
 8. Copy the appliance setup file and key file to the Windows Server 2016 or Windows Server 2012 AWS VM you created for the replication appliance.
 9. Run the replication appliance setup file, as described in the next procedure.  
-    9.1. Under **Before You Begin**, select **Install the configuration server and process server**, and then select **Next**.   
-    9.2 In **Third-Party Software License**, select **I accept the third-party license agreement**, and then select **Next**.   
-    9.3 In **Registration**, select **Browse**, and then go to where you put the vault registration key file. Select **Next**.  
-    9.4 In **Internet Settings**, select **Connect to Azure Site Recovery without a proxy server**, and then select **Next**.  
-    9.5 The **Prerequisites Check** page runs checks for several items. When it's finished, select **Next**.  
-    9.6 In **MySQL Configuration**, provide a password for the MySQL DB, and then select **Next**.  
-    9.7 In **Environment Details**, select **No**. You don't need to protect your VMs. Then, select **Next**.  
-    9.8 In **Install Location**, select **Next** to accept the default.  
-    9.9 In **Network Selection**, select **Next** to accept the default.  
-    9.10 In **Summary**, select **Install**.   
-    9.11 **Installation Progress** shows you information about the installation process. When it's finished, select **Finish**. A window displays a message about a reboot. Select **OK**.   
-    9.12 Next, a window displays a message about the configuration server connection passphrase. Copy the passphrase to your clipboard and save the passphrase in a temporary text file on the source VMs. You’ll need this passphrase later, during the mobility service installation process.
+    1.  Under **Before You Begin**, select **Install the configuration server and process server**, and then select **Next**.   
+    2. In **Third-Party Software License**, select **I accept the third-party license agreement**, and then select **Next**.   
+    3. In **Registration**, select **Browse**, and then go to where you put the vault registration key file. Select **Next**.  
+    4. In **Internet Settings**, select **Connect to Azure Site Recovery without a proxy server**, and then select **Next**.  
+    5. The **Prerequisites Check** page runs checks for several items. When it's finished, select **Next**.  
+    6. In **MySQL Configuration**, provide a password for the MySQL DB, and then select **Next**.  
+    7. In **Environment Details**, select **No**. You don't need to protect your VMs. Then, select **Next**.  
+    8. In **Install Location**, select **Next** to accept the default.  
+    9. In **Network Selection**, select **Next** to accept the default.  
+    10. In **Summary**, select **Install**.   
+    11. **Installation Progress** shows you information about the installation process. When it's finished, select **Finish**. A window displays a message about a reboot. Select **OK**.   
+    12. Next, a window displays a message about the configuration server connection passphrase. Copy the passphrase to your clipboard and save the passphrase in a temporary text file on the source VMs. You’ll need this passphrase later, during the mobility service installation process.
 
 10. After the installation completes, the Appliance configuration wizard will be launched automatically (You can also launch the wizard manually by using the cspsconfigtool shortcut that is created on the desktop of the appliance). In this tutorial, we'll be manually installing the Mobility Service on source VMs to be replicated, so create a dummy account in this step and proceed. You can provide the following details for creating the dummy account - "guest" as the friendly name, "username" as the username, and "password" as the password for the account. You will be using this dummy account in the Enable Replication stage.
 
@@ -240,7 +240,7 @@ A Mobility service agent must be installed on the source AWS VMs to be migrated.
 6. In **Virtual Machines**, in **Import migration settings from an assessment?**, leave the default setting **No, I'll specify the migration settings manually**.
 7. Check each VM you want to migrate. Then click **Next: Target settings**.
 
-    ![Select VMs](./media/tutorial-migrate-physical-virtual-machines/select-vms.png)
+    :::image type="content" source="./media/tutorial-migrate-physical-virtual-machines/select-vms-inline.png" alt-text="Screenshot on selecting VMs." lightbox="./media/tutorial-migrate-physical-virtual-machines/select-vms-expanded.png":::
 
 8. In **Target settings**, select the subscription, and target region to which you'll migrate, and specify the resource group in which the Azure VMs will reside after migration.
 9. In **Virtual Network**, select the Azure VNet/subnet to which the Azure VMs will be joined after migration.  
@@ -276,13 +276,15 @@ A Mobility service agent must be installed on the source AWS VMs to be migrated.
     - **Availability Zone**: Specify the Availability Zone to use.
     - **Availability Set**: Specify the Availability Set to use.
 
-![Compute settings](./media/tutorial-migrate-physical-virtual-machines/compute-settings.png)
-
 15. In **Disks**, specify whether the VM disks should be replicated to Azure, and select the disk type (standard SSD/HDD or premium managed disks) in Azure. Then click **Next**.
     - You can exclude disks from replication.
     - If you exclude disks, won't be present on the Azure VM after migration.
 
-    ![Disk settings](./media/tutorial-migrate-physical-virtual-machines/disks.png)
+    :::image type="content" source="./media/tutorial-migrate-physical-virtual-machines/disks-inline.png" alt-text="Screenshot shows the Disks tab of the Replicate dialog box." lightbox="./media/tutorial-migrate-physical-virtual-machines/disks-expanded.png":::
+
+1. In **Tags**, choose to add tags to your Virtual machines, Disks, and NICs.
+
+    :::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":::
 
 16. In **Review and start replication**, review the settings, and click **Replicate** to start the initial replication for the servers.
 

articles/migrate/media/tutorial-migrate-hyper-v/select-assessment.png

@@ -234,7 +234,7 @@ A Mobility service agent must be installed on the source GCP VMs to be migrated.
 6. In **Virtual Machines**, in **Import migration settings from an assessment?**, leave the default setting **No, I'll specify the migration settings manually**.
 7. Check each VM you want to migrate. Then click **Next: Target settings**.
 
-    ![Select VMs](./media/tutorial-migrate-physical-virtual-machines/select-vms.png)
+    :::image type="content" source="./media/tutorial-migrate-physical-virtual-machines/select-vms-inline.png" alt-text="Screenshot on selecting VMs." lightbox="./media/tutorial-migrate-physical-virtual-machines/select-vms-expanded.png":::
 
 8. In **Target settings**, select the subscription, and target region to which you'll migrate, and specify the resource group in which the Azure VMs will reside after migration.
 9. In **Virtual Network**, select the Azure VNet/subnet to which the Azure VMs will be joined after migration.  
@@ -269,13 +269,15 @@ A Mobility service agent must be installed on the source GCP VMs to be migrated.
     - **Availability Zone**: Specify the Availability Zone to use.
     - **Availability Set**: Specify the Availability Set to use.
 
-![Compute settings](./media/tutorial-migrate-physical-virtual-machines/compute-settings.png)
-
 15. In **Disks**, specify whether the VM disks should be replicated to Azure, and select the disk type (standard SSD/HDD or premium managed disks) in Azure. Then click **Next**.
     - You can exclude disks from replication.
     - If you exclude disks, won't be present on the Azure VM after migration.
 
-    ![Disk settings](./media/tutorial-migrate-physical-virtual-machines/disks.png)
+    :::image type="content" source="./media/tutorial-migrate-physical-virtual-machines/disks-inline.png" alt-text="Screenshot shows the Disks tab of the Replicate dialog box." lightbox="./media/tutorial-migrate-physical-virtual-machines/disks-expanded.png":::
+
+1. In **Tags**, choose to add tags to your Virtual machines, Disks, and NICs.
+
+    :::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":::
 
 16. In **Review and start replication**, review the settings, and click **Replicate** to start the initial replication for the servers.
 

articles/migrate/media/tutorial-migrate-hyper-v/select-vms-expanded.png

@@ -5,13 +5,13 @@ author: bsiva
 ms.author: bsiva
 ms.manager: abhemraj
 ms.topic: tutorial
-ms.date: 03/18/2021
+ms.date: 06/20/2022
 ms.custom: [ "MVC", "fasttrack-edit"]
 ---
 
 # Migrate Hyper-V VMs to Azure
 
-This article shows you how to migrate on-premises Hyper-V VMs to Azure with the [Azure Migrate:Server Migration](migrate-services-overview.md#azure-migrate-server-migration-tool) tool.
+This article shows you how to migrate on-premises Hyper-V VMs to Azure with the [Azure Migrate: Server Migration](migrate-services-overview.md#azure-migrate-server-migration-tool) tool.
 
 This tutorial is the third in a series that demonstrates how to assess and migrate machines to Azure.
 
@@ -21,7 +21,7 @@ This tutorial is the third in a series that demonstrates how to assess and migra
  In this tutorial, you learn how to:
 
 > [!div class="checklist"]
-> * Add the Azure Migrate:Server Migration tool.
+> * Add the Azure Migrate: Server Migration tool.
 > * Discover VMs you want to migrate.
 > * Start replicating VMs.
 > * Run a test migration to make sure everything's working as expected.
@@ -44,19 +44,19 @@ Before you begin this tutorial, you should:
 
 ## Download the provider
 
-For migrating Hyper-V VMs, Azure Migrate:Server Migration installs software providers (Microsoft Azure Site Recovery provider and Microsoft Azure Recovery Service agent) on Hyper-V Hosts or cluster nodes. Note that the [Azure Migrate appliance](migrate-appliance.md) isn't used for Hyper-V migration.
+For migrating Hyper-V VMs, Azure Migrate: Server Migration installs software providers (Microsoft Azure Site Recovery provider and Microsoft Azure Recovery Service agent) on Hyper-V Hosts or cluster nodes. Note that the [Azure Migrate appliance](migrate-appliance.md) isn't used for Hyper-V migration.
 
 1. In the Azure Migrate project > **Servers**, in **Azure Migrate: Server Migration**, click **Discover**.
 1. In **Discover machines** > **Are your machines virtualized?**, select **Yes, with Hyper-V**.
 1. In **Target region**, select the Azure region to which you want to migrate the machines.
 1. Select **Confirm that the target region for migration is region-name**.
 1. Click **Create resources**. This creates an Azure Site Recovery vault in the background.
-    - If you've already set up migration with Azure Migrate Server Migration, this option won't appear since resources were set up previously.
+    - If you've already set up migration with Azure Migrate: Server Migration, this option won't appear since resources were set up previously.
     - You can't change the target region for this project after clicking this button.
     - All subsequent migrations are to this region.
 
 1. In **Prepare Hyper-V host servers**, download the Hyper-V Replication provider, and the registration key file.
-    - The registration key is needed to register the Hyper-V host with Azure Migrate Server Migration.
+    - The registration key is needed to register the Hyper-V host with Azure Migrate: Server Migration.
     - 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)
@@ -131,7 +131,7 @@ After installing the provider on hosts, go to the Azure portal and in **Discover
 
  ![Finalize registration](./media/tutorial-migrate-hyper-v/finalize-registration.png) 
 
-It can take up to 15 minutes after finalizing registration until discovered VMs appear in Azure Migrate Server Migration. As VMs are discovered, the **Discovered servers** count rises.
+It can take up to 15 minutes after finalizing registration until discovered VMs appear in Azure Migrate: Server Migration. As VMs are discovered, the **Discovered servers** count rises.
 
  ![Discovered servers](./media/tutorial-migrate-hyper-v/discovered-servers.png)
 
@@ -153,7 +153,7 @@ With discovery completed, you can begin replication of Hyper-V VMs to Azure.
 
 1. In **Virtual machines**, search for VMs as needed, and check each VM you want to migrate. Then, click **Next: Target settings**.
 
-    ![Select VMs](./media/tutorial-migrate-hyper-v/select-vms.png)
+    :::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":::
 
 1. In **Target settings**, select the target region to which you'll migrate, the subscription, and the resource group in which the Azure VMs will reside after migration.
 1. In **Replication Storage Account**, select the Azure Storage account in which replicated data will be stored in Azure.
@@ -175,8 +175,6 @@ 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.
 
-    ![VM compute settings](./media/tutorial-migrate-hyper-v/compute-settings.png)
-
 1. In **Disks**, specify the VM disks that needs to be replicated to Azure. Then click **Next**.
     - You can exclude disks from replication.
     - If you exclude disks, won't be present on the Azure VM after migration.