Removed stale images

v-sreedevank · v-sreedevank · commit 7e303eea6721 · 2024-08-21T17:30:22.000+05:30
diff --git a/articles/migrate/how-to-create-a-group.md b/articles/migrate/how-to-create-a-group.md
@@ -36,14 +36,10 @@ If you want to create a group manually outside of creating an assessment, do the
     - If you haven't yet added the Azure Migrate: Discovery and assessment tool, click to add it. [Learn more](how-to-assess.md).
     - If you haven't yet created an Azure Migrate project, [learn more](./create-manage-projects.md).
 
-    ![Select groups](./media/how-to-create-a-group/select-groups.png)
-
 2. Click the **Group** icon.
 3. In **Create group**, specify a group name, and in **Appliance name**, select the Azure Migrate appliance you're using for server discovery.
 4. From the server list, select the servers you want to add to the group > **Create**.
 
-    ![Create group](./media/how-to-create-a-group/create-group.png)
-
 You can now use this group when you [create an Azure VM assessment](how-to-create-assessment.md) or [an Azure VMware Solution (AVS) assessment](how-to-create-azure-vmware-solution-assessment.md) or [an Azure SQL assessment](how-to-create-azure-sql-assessment.md) or [an Azure App Service assessment](how-to-create-azure-app-service-assessment.md).
 
 ## Refine a group with dependency mapping
diff --git a/articles/migrate/how-to-migrate.md b/articles/migrate/how-to-migrate.md
@@ -24,59 +24,36 @@ This article describes how to add migration tools in [Azure Migrate](./migrate-s
 1. In the Azure Migrate project, select **Overview**.
 2. Select the migration scenario you want to use:
 
-    - To migrate machines and workloads to Azure, select **Assess and migrate servers**.
+    - To migrate machines and workloads to Azure, select **Discover, assess and migrate**.
     - To migrate on-premises databases, select **Assess and migrate databases**.
     - To migrate on-premises web apps, select **Explore more** > **Web Apps**.
     - To migrate data to Azure using Data box, select **Explore more** > **Data box**.
 
-    ![Options for selecting a migrate scenario](./media/how-to-migrate/migrate-scenario.png)
-
-
 ## Select a migration tool
 
 1. Add a tool:
 
-    - If you created an Azure Migrate project using the **Assess and migrate servers** option in the portal, the Migration and modernization tool is automatically added to the project. To add additional migration tools, in **Servers, databases and web apps**, next to **Migration tools**, select **Add more tools**.
-    
-         ![Button to add additional migration tools](./media/how-to-migrate/add-migration-tools.png)
-
-    - If you created a project using a different option, and don't yet have any migration tools, in **Servers, databases and web apps** > **Migration tools**, select **Click here**.
-
-    ![Button to add first migration tools](./media/how-to-migrate/no-migration-tool.png)
-
-2. In **Azure Migrate** > **Add tools**, select the tools you want to add. Then select **Add tool**.
-
-    ![Select assessment tools from list](./media/how-to-migrate/select-migration-tool.png)
+    - If you created an Azure Migrate project using the **Discover, assess and migrate** option in the portal, the Migration and modernization tool is automatically added to the project. To add additional migration tools, in **Servers, databases and web apps** > **Migration and modernization**, select **Click here**.
 
+2. In **Azure Migrate** > **Add tools**, select the tools you want to add. Then select **Add tool*.
 
 ## Select a database migration tool
 
 If you created an Azure Migrate project using the **Assess and migrate database** option in the portal, the Database Migration tool is automatically added to the project. 
 
 1. If the Database Migration tool isn't in the project, in **Databases** > **Assessment tools**, select **Click here**.
-    
-    ![Add database migration tools](./media/how-to-migrate/no-database-migration-tool.png)
-
 
 2. In **Azure Migrate** > **Add tools**, select the Database Migration tool. Then select **Add tool**.
 
-    ![Select the database migration tool from list](./media/how-to-migrate/select-database-migration-tool.png)
-
-    
-
 ## Select a web app migration tool
 
-If you created an Azure Migrate project using the **Explore more** > **WebApps** option in the portal, the Web app migration tool is automatically added to the project. 
+If you created an Azure Migrate project using the **Explore more** > **Web apps** option in the portal, the Web app migration tool is automatically added to the project. 
 
 1. If the Web app migration tool isn't in the project, in **Web apps** > **Assessment tools**, select **Click here**.
-
-    ![Add web app migration tools](./media/how-to-migrate/no-web-app-migration-tool.png)
  
 
 2. In **Azure Migrate** > **Add tools**, select the Web App Migration tool. Then select **Add tool**.
 
-    ![Select webapp assessment tools from list](./media/how-to-migrate/select-web-app-migration-tool.png)
-
 
 ## Order an Azure Data Box
 
diff --git a/articles/migrate/tutorial-assess-gcp.md b/articles/migrate/tutorial-assess-gcp.md
@@ -51,9 +51,6 @@ Run an assessment as follows:
    ![Location of Assess and migrate servers button](./media/tutorial-assess-vmware-azure-vm/assess.png)
 
 2. In **Azure Migrate: Discovery and assessment**, select **Assess**.
-
-    ![Location of the Assess button](./media/tutorial-assess-vmware-azure-vm/assess-servers.png)
-
 3. In **Assess servers** > **Assessment type**, select **Azure VM**.
 4. In **Discovery source**:
 
diff --git a/articles/migrate/tutorial-assess-physical.md b/articles/migrate/tutorial-assess-physical.md
@@ -56,9 +56,6 @@ Run an assessment as follows:
    ![Location of Assess and migrate servers button.](./media/tutorial-assess-vmware-azure-vm/assess.png)
 
 2. In **Azure Migrate: Discovery and assessment**, select **Assess** > **Azure VM**.
-
-    ![Location of the Assess button](./media/tutorial-assess-vmware-azure-vm/assess-servers.png)
-
 3. In **Assess servers** > **Assessment type**, select **Azure VM**.
 4. In **Discovery source**:
 
diff --git a/articles/migrate/vmware/tutorial-migrate-vmware-agent.md b/articles/migrate/vmware/tutorial-migrate-vmware-agent.md
@@ -153,24 +153,18 @@ Download the template as follows:
 
 1. In the Azure Migrate project, select **Servers, databases and web apps** under **Migration goals**.
 2. In **Servers, databases and web apps** > **Migration and modernization**, click **Discover**.
-
-    ![Discover VMs](../media/tutorial-migrate-vmware-agent/migrate-discover.png)
-
 3. In **Discover machines** > **Are your machines virtualized?**, click **Yes, with VMware vSphere hypervisor**.
 4. In **How do you want to migrate?**, select **Using agent-based replication**.
 5. In **Target region**, select the Azure region to which you want to migrate the machines.
 6. Select **Confirm that the target region for migration is region-name**.
 7. Click **Create resources**. This creates an Azure Site Recovery vault in the background. You can't change the target region for this project after clicking this button, and all subsequent migrations are to this region.
 
-    ![Create Recovery Services vault](../media/tutorial-migrate-vmware-agent/create-resources.png)  
-
     > [!NOTE]
     > If you selected private endpoint as the connectivity method for the Azure Migrate project when it was created, the Recovery Services vault will also be configured for private endpoint connectivity. Ensure that the private endpoints are reachable from the replication appliance: [**Learn more**](../troubleshoot-network-connectivity.md)
 
 
 8. In **Do you want to install a new replication appliance?**, select **Install a replication appliance**.
 9. Click **Download**. This downloads an OVF template.
-    ![Download OVA](../media/tutorial-migrate-vmware-agent/download-ova.png)
 10. Note the name of the resource group and the Recovery Services vault. You need these during appliance deployment.
 
 
@@ -242,16 +236,12 @@ Select VMs for migration.
 
 1. In the Azure Migrate project > **Servers, databases and web apps** > **Migration and modernization**, click **Replicate**.
 
-    :::image type="content" source="../media/tutorial-migrate-vmware-agent/select-replicate.png" alt-text="Screenshot  of the Servers screen in Azure Migrate. The Replicate button is selected in the Migration and modernization tool under Migration tools.":::
-
 2. In **Replicate**, > **Source settings** > **Are your machines virtualized?**, select **Yes, with VMware vSphere**.
 3. In **On-premises appliance**, select the name of the Azure Migrate appliance that you set up.
 4. In **vCenter server**, specify the name of the vCenter server managing the VMs, or the vSphere server on which the VMs are hosted.
 5. In **Process Server**, select the name of the replication appliance.
 6. In **Guest credentials**, specify the VM admin account that will be used for push installation of the Mobility service. Then click **Next: Virtual machines**.
 
-    :::image type="content" source="../media/tutorial-migrate-vmware-agent/source-settings.png" alt-text="Screenshot of the Source settings tab in the Replicate screen. The Guest credentials field is highlighted and the value is set to VM-admin-account.":::
-
 7. In **Virtual Machines**, select the machines that 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.
@@ -263,8 +253,6 @@ Select VMs for migration.
     - No infrastructure redundancy required option if you don't need either of these availability configurations for the migrated machines.
 9. Check each VM you want to migrate. Then click **Next: Target settings**.
 
-    :::image type="content" source="../media/tutorial-migrate-vmware-agent/select-vms-inline.png" alt-text="Screenshot on selecting VMs." lightbox="../media/tutorial-migrate-vmware-agent/select-vms-expanded.png":::
-
 10. 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.
 11. In **Virtual Network**, select the Azure VNet/subnet to which the Azure VMs will be joined after migration.  
 12. In  **Cache storage account**, keep the default option to use the cache storage account that is automatically created for the project. Use the dropdown if you'd like to specify a different storage account to use as the cache storage account for replication. <br/>
@@ -290,8 +278,6 @@ Select VMs for migration.
     - 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**.
 
-        :::image type="content" source="../media/tutorial-migrate-vmware/target-settings.png" alt-text="Screenshot on target settings.":::
-
 16. In **Compute**, review the VM name, size, OS disk type, and availability configuration (if selected in the previous step). VMs must conform with [Azure requirements](migrate-support-matrix-vmware-migration.md#azure-vm-requirements).
 
    - **VM size**: If you're using assessment recommendations, the VM size dropdown shows the recommended size. Otherwise Azure Migrate picks a size based on the closest match in the Azure subscription. Alternatively, pick a manual size in **Azure VM size**.
@@ -302,14 +288,10 @@ Select VMs for migration.
 17. 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, they won't be present on the Azure VM after migration.
-
-    :::image type="content" source="../media/tutorial-migrate-vmware-agent/disks-inline.png" alt-text="Screenshot shows the Disks tab of the Replicate dialog box." lightbox="../media/tutorial-migrate-vmware-agent/disks-expanded.png":::
     - You can exclude disks if the mobility agent is already installed on that server. [Learn more](../../site-recovery/exclude-disks-replication.md#exclude-limitations).
 
 18. 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":::
-
 19. In **Review and start replication**, review the settings, and click **Replicate** to start the initial replication for the servers.
 
 > [!NOTE]
@@ -320,12 +302,8 @@ Select VMs for migration.
 
 1. Track job status in the portal notifications.
 
-    ![Track job](../media/tutorial-migrate-vmware-agent/jobs.png)
-
 2. To monitor replication status, click **Replicating servers** in **Migration and modernization**.
 
-    ![Monitor replication](../media/tutorial-migrate-vmware-agent/replicate-servers.png)
-
 Replication occurs as follows:
 - 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 the replica disks in Azure.
@@ -345,19 +323,13 @@ Do a test migration as follows:
 
 1. In **Migration goals** > **Servers, databases and web apps** > **Migration and modernization**, select **Test migrated servers**.
 
-     :::image type="content" source="../media/tutorial-migrate-vmware-agent/test-migrated-servers.png" alt-text="Screenshot of Test migrated servers.":::
-
 2. Right-click the VM to test, and click **Test migrate**.
 
-    :::image type="content" source="../media/tutorial-migrate-vmware-agent/test-migrate-inline.png" alt-text="Screenshot of Test migration." lightbox="../media/tutorial-migrate-vmware-agent/test-migrate-expanded.png":::
-
 3. In **Test Migration**, select the Azure VNet in which the Azure VM will be located after the migration. We recommend you use a non-production VNet.
 4. The **Test migration** job starts. Monitor the job in the portal notifications.
 5. After the migration finishes, view the migrated Azure VM in **Virtual Machines** in the Azure portal. The machine name has a suffix **-Test**.
 6. After the test is done, right-click the Azure VM in **Replicating machines**, and click **Clean up test migration**.
 
-    :::image type="content" source="../media/tutorial-migrate-vmware-agent/clean-up-inline.png" alt-text="Screenshot of Clean up migration." lightbox="../media/tutorial-migrate-vmware-agent/clean-up-expanded.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.
@@ -368,9 +340,6 @@ Do a test migration as follows:
 After you've verified that the test migration works as expected, you can migrate the on-premises machines.
 
 1. In the Azure Migrate project > **Servers, databases and web apps** > **Migration and modernization**, select **Replicating servers**.
-
-    ![Replicating servers](../media/tutorial-migrate-vmware-agent/replicate-servers.png)
-
 2. In **Replicating machines**, right-click the VM > **Migrate**.
 3. 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 to ensure minimum data loss.
