Freshnes - Updated instances of Servers, databases and web apps

Author: v-sreedevank

articles/migrate/how-to-create-a-group.md

@@ -6,8 +6,8 @@ ms.author: rajosh
 ms.manager: abhemraj
 ms.service: azure-migrate
 ms.topic: how-to
-ms.date: 07/28/2021
-ms.custom: engagement-fy23
+ms.date: 08/21/2024
+ms.custom: engagement-fy25
 ---
 
 # Create a group for assessment
@@ -56,8 +56,8 @@ Dependency mapping helps you to visualize dependencies across servers. You typic
 
 If you've already [set up dependency mapping](how-to-create-group-machine-dependencies.md), and want to refine an existing group, do the following:
 
-1. In the **Servers** tab, in **Azure Migrate: Discovery and assessment** tile, click **Groups**.
-2. Click the group you want to refine.
+1. In the **Servers, databases and web apps** tab, in **Azure Migrate: Discovery and assessment** tile, select **Groups**.
+2. Select the group you want to refine.
     - If you haven't yet set up dependency mapping, the **Dependencies** column will show a **Requires installation** status. For each server for which you want to visualize dependencies, click **Requires installation**. Install a couple of agents on each server, before you can map the server dependencies. [Learn more](how-to-create-group-machine-dependencies.md).
 
         ![Add dependency mapping](./media/how-to-create-a-group/add-dependency-mapping.png)

articles/migrate/how-to-create-group-machine-dependencies.md

@@ -6,8 +6,8 @@ ms.author: rajosh
 ms.manager: abhemraj
 ms.topic: how-to
 ms.service: azure-migrate
-ms.date: 12/07/2023
-ms.custom: engagement-fy24
+ms.date: 08/21/2024
+ms.custom: engagement-fy25
 ---
 
 # Set up dependency visualization
@@ -37,7 +37,7 @@ This article describes how to set up agent-based dependency analysis in Azure Mi
 
 ## Associate a workspace
 
-1. After you've discovered servers for assessment, in **Servers** > **Azure Migrate: Discovery and assessment**, click **Overview**.  
+1. After you've discovered servers for assessment, in **Servers, databases and web apps** > **Azure Migrate: Discovery and assessment**, select **Overview**.  
 2. In **Azure Migrate: Discovery and assessment**, click **Essentials**.
 3. In **OMS Workspace**, click **Requires configuration**.
 

articles/migrate/how-to-migrate.md

@@ -6,8 +6,8 @@ ms.author: sunishvohra
 ms.manager: vijain
 ms.topic: how-to
 ms.service: azure-migrate
-ms.date: 12/12/2022
-ms.custom: engagement-fy23
+ms.date: 08/21/2024
+ms.custom: engagement-fy25
 ---
 
 
@@ -36,11 +36,11 @@ This article describes how to add migration tools in [Azure Migrate](./migrate-s
 
 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**, next to **Migration tools**, select **Add more tools**.
+    - 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** > **Migration tools**, select **Click here**.
+    - 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)
 

articles/migrate/troubleshoot-discovery.md

@@ -6,8 +6,8 @@ ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: troubleshooting
 ms.service: azure-migrate
-ms.date: 04/20/2023
-ms.custom: engagement-fy23
+ms.date: 08/21/2024
+ms.custom: engagement-fy25
 ---
 
 # Troubleshoot ongoing server discovery, software inventory, and SQL and web apps discovery
@@ -24,7 +24,7 @@ If the servers don't appear in the portal, wait for a few minutes because it tak
 
 If the state still doesn't change:
 
-- Select **Refresh** on the **Servers** tab to see the count of the discovered servers in Azure Migrate: Discovery and assessment and Migration and modernization.
+- Select **Refresh** on the **Servers, databases and web apps** tab to see the count of the discovered servers in Azure Migrate: Discovery and assessment and Migration and modernization.
 
 If the preceding step doesn't work and you're discovering VMware servers:
 

articles/migrate/tutorial-assess-gcp.md

@@ -5,7 +5,7 @@ author: rashi-ms
 ms.author: rajosh
 ms.manager: abhemraj
 ms.topic: tutorial
-ms.date: 08/08/2024
+ms.date: 08/21/2024
 ms.service: azure-migrate
 ms.custom: MVC, engagement-fy25
 #Customer intent: As a server admin, I want to assess my GCP instances in preparation for migration to Azure.
@@ -115,7 +115,7 @@ Run an assessment as follows:
 
 1. In **Review + create assessment**, review the assessment details, and select **Create Assessment** to create the group and run the assessment.
 
-1. After the assessment is created, view it in **Servers** > **Azure Migrate: Discovery and assessment** > **Assessments**.
+1. After the assessment is created, view it in **Servers, databases and web apps** > **Azure Migrate: Discovery and assessment** > **Assessments**.
 
 1. Select **Export assessment** to download it as an Excel file.
     > [!NOTE]

articles/migrate/tutorial-assess-physical.md

@@ -5,7 +5,7 @@ author: rashi-ms
 ms.author: rajosh
 ms.manager: abhemraj
 ms.topic: tutorial
-ms.date: 08/08/2024
+ms.date: 08/21/2024
 ms.service: azure-migrate
 ms.custom: MVC, engagement-fy25
 #Customer intent: As a server admin, I want to assess my on-premises physical servers in preparation for migration to Azure.
@@ -119,7 +119,7 @@ Run an assessment as follows:
 
 1. In **Review + create assessment**, review the assessment details, and select **Create Assessment** to create the group and run the assessment.
 
-1. After the assessment is created, view it in **Servers** > **Azure Migrate: Discovery and assessment** > **Assessments**.
+1. After the assessment is created, view it in **Servers, databases and web apps** > **Azure Migrate: Discovery and assessment** > **Assessments**.
 
 1. Select **Export assessment**, to download it as an Excel file.
 

articles/migrate/tutorial-discover-import.md

@@ -5,9 +5,9 @@ author: rashi-ms
 ms.author: rajosh
 ms.manager: ronai
 ms.topic: tutorial
-ms.date: 07/05/2024
+ms.date: 08/21/2024
 ms.service: azure-migrate
-ms.custom: engagement-fy24
+ms.custom: engagement-fy25
 
 ---
 
@@ -103,15 +103,13 @@ Set up a new Azure Migrate project if you don't have one.
 
 The **Azure Migrate: Discovery and assessment** tool is added by default to the new project.
 
-![Page showing Server Assessment tool added by default](./media/tutorial-discover-import/added-tool.png)
-
 ## Prepare the CSV
 
 Download the CSV template and add server information to it.
 
 ### Download the template
 
-1. In **Migration goals** > **Servers** > **Azure Migrate: Discovery and assessment**, select **Discover**.
+1. In **Migration goals** > **Servers, databases and web apps** > **Azure Migrate: Discovery and assessment**, select **Discover**.
 2. In **Discover machines**, select **Import using CSV**.
 3. Select **Download** to download the CSV template. Alternatively, you can [download it directly](https://go.microsoft.com/fwlink/?linkid=2109031).
 
@@ -175,7 +173,7 @@ For example, to specify all fields for a second disk, add these columns:
 
 After adding information to the CSV template, import the CSV file.
 
-1. In **Migration goals** > **Servers** > **Azure Migrate: Discovery and assessment**, select **Discover**.
+1. In **Migration goals** > **Servers, databases and web apps** > **Azure Migrate: Discovery and assessment**, select **Discover**.
 1. In **Discover machines**, select **Import using CSV** 
 1. Upload the .csv file and select **Import**.
 3. The import status is shown.

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

@@ -6,8 +6,8 @@ ms.author: vijain
 ms.manager: kmadnani
 ms.topic: tutorial
 ms.service: azure-migrate
-ms.date: 06/17/2024
-ms.custom: MVC, engagement-fy24
+ms.date: 08/21/2024
+ms.custom: MVC, engagement-fy25
 ---
 
 # Migrate machines as physical servers to Azure
@@ -268,7 +268,7 @@ When delta replication begins, you can run a test migration for the VMs before y
 
 To do a test migration:
 
-1. In **Migration goals**, select **Servers** > **Migration and modernization**, select **Replicated servers** under **Replications**.
+1. In **Migration goals**, select **Servers, databases and web apps** > **Migration and modernization**, select **Replicated servers** under **Replications**.
 
 1. In the **Replicating machines** tab, right-click the VM to test and select **Test migrate**.
 

articles/migrate/vmware/tutorial-migrate-vmware-agent.md

@@ -6,8 +6,8 @@ ms.author: vijain
 ms.manager: kmadnani
 ms.topic: tutorial
 ms.service: azure-migrate
-ms.date: 03/20/2024
-ms.custom: vmware-scenario-422, MVC, engagement-fy23
+ms.date: 08/20/2024
+ms.custom: vmware-scenario-422, MVC, engagement-fy25
 ---
 
 # Migrate VMware vSphere VMs to Azure (agent-based)
@@ -343,7 +343,7 @@ When delta replication begins, you can run a test migration for the VMs, before
 Do a test migration as follows:
 
 
-1. In **Migration goals** > **Servers** > **Migration and modernization**, select **Test migrated servers**.
+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.":::