Merge pull request #292455 from v-sreedevank/30Dec-Freshness

Freshness - Removed stale screenshots

Author: prmerger-automator[bot]

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

@@ -5,7 +5,7 @@ author: vijain
 ms.author: vijain
 ms.topic: tutorial
 ms.service: azure-migrate
-ms.date: 12/10/2024
+ms.date: 12/30/2024
 ms.custom: MVC, engagement-fy24
 ---
 
@@ -133,9 +133,6 @@ The first step of migration is to set up the replication appliance. To set up th
 ### Download the replication appliance installer
 
 1. In the Azure Migrate project, select **Servers, databases, and web apps** > **Migration and modernization** > **Discover**.
-
-    ![Screenshot that shows the Discover button.](./media/tutorial-migrate-physical-virtual-machines/migrate-discover.png)
-
 1. In **Discover machines** > **Are your machines virtualized?**, select **Not virtualized/Other**.
 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\>**.
@@ -281,8 +278,6 @@ You can track job status in the portal notifications.
 
 You can monitor replication status by selecting **Replicating servers** in **Azure Migrate: Server Migration**.
 
-![Screenshot that shows the Replicating servers option.](./media/tutorial-migrate-physical-virtual-machines/replicating-servers.png)
-
 ## Run a test migration
 
 When delta replication begins, you can run a test migration for the VMs before you run a full migration to Azure. We highly recommend the test migration. It provides an opportunity to discover any potential issues and fix them before you proceed with the actual migration. We recommend that you do this step at least once for each VM before you migrate it.
@@ -295,8 +290,6 @@ To do a test migration:
 
 1. In **Migration goals**, select **Servers, databases, and web apps** > **Migration and modernization** > **Test migrated servers**.
 
-     ![Screenshot that shows Test migrated servers.](./media/tutorial-migrate-physical-virtual-machines/test-migrated-servers.png)
-
 1. Right-click the VM you want to test and select **Test migrate**.
 
     ![Screenshot that shows Test migrate.](./media/tutorial-migrate-physical-virtual-machines/test-migrate.png)
@@ -318,9 +311,6 @@ To do a test migration:
 After you verify that the test migration works as expected, you can migrate the AWS VMs.
 
 1. In the Azure Migrate project, select **Servers, databases, and web apps** > **Migration and modernization** > **Replicating servers**.
-
-    ![Screenshot that shows Replicating servers.](./media/tutorial-migrate-physical-virtual-machines/replicate-servers.png)
-
 1. In **Replicating machines**, right-click the VM and select **Migrate**.
 1. In **Migrate** > **Shut down virtual machines and perform a planned migration with no data loss**, select **Yes** > **OK**.
 

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

@@ -4,7 +4,7 @@ description: This article describes how to migrate GCP VMs to Azure with Azure M
 author: vijain
 ms.author: vijain
 ms.topic: tutorial
-ms.date: 09/18/2024
+ms.date: 12/30/2024
 ms.service: azure-migrate
 ms.custom: MVC, engagement-fy24
 ---
@@ -125,9 +125,6 @@ The first step of migration is to set up the replication appliance. To set up th
 ### Download the replication appliance installer
 
 1. In the Azure Migrate project, select **Servers, databases, and web apps** > **Migration and modernization** > **Discover**.
-
-    ![Screenshot that shows the Discover button.](./media/tutorial-migrate-physical-virtual-machines/migrate-discover.png)
-
 1. In **Discover machines** > **Are your machines virtualized?**, select **Not virtualized/Other**.
 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\>**.
@@ -196,9 +193,6 @@ A Mobility service agent must be preinstalled on the source GCP VMs to be migrat
 > Through the portal, you can add up to 10 VMs for replication at once. To replicate more VMs simultaneously, you can add them in batches of 10.
 
 1. In the Azure Migrate project, select **Servers, databases, and web apps** > **Migration and modernization** > **Replicate**.
-
-    ![Screenshot that shows selecting Replicate.](./media/tutorial-migrate-physical-virtual-machines/select-replicate.png)
-
 1. In **Replicate**, > **Source settings** > **Are your machines virtualized?**, select **Not virtualized/Other**.
 1. In **On-premises appliance**, select the name of the Azure Migrate appliance that you set up.
 1. In **Process Server**, select the name of the replication appliance.
@@ -283,8 +277,6 @@ To do a test migration:
 
 1. In **Migration goals**, select **Servers, databases, and web apps** > **Migration and modernization** > **Test migrated servers**.
 
-     ![Screenshot that shows Test migrated servers.](./media/tutorial-migrate-physical-virtual-machines/test-migrated-servers.png)
-
 1. Right-click the VM to test and select **Test migrate**.
 
     :::image type="content" source="./media/tutorial-migrate-physical-virtual-machines/test-migrate-inline.png" alt-text="Screenshot that shows the result after selecting test migration." lightbox="./media/tutorial-migrate-physical-virtual-machines/test-migrate-expanded.png":::
@@ -306,9 +298,6 @@ To do a test migration:
 After you verify that the test migration works as expected, you can migrate the GCP VMs.
 
 1. In the Azure Migrate project, select **Servers, databases, and web apps** > **Migration and modernization** > **Replicating servers**.
-
-    ![Screenshot that shows Replicating servers.](./media/tutorial-migrate-physical-virtual-machines/replicate-servers.png)
-
 1. In **Replicating machines**, right-click the VM and select **Migrate**.
 1. In **Migrate** > **Shut down virtual machines and perform a planned migration with no data loss**, select **Yes** > **OK**.