Merge pull request #297899 from habibaum/09Apr-dep-map

v-regandowner · web-flow · commit 14647bf4e032 · 2025-04-09T15:25:31.000-04:00
feedback incorporated
diff --git a/articles/migrate/how-to-create-group-machine-dependencies-agentless.md b/articles/migrate/how-to-create-group-machine-dependencies-agentless.md
@@ -83,15 +83,16 @@ On reviewing the **Dependencies** column for any server, you see one of the foll
 
 1. **Credentials not available:** when no server credentials provided on the appliance configuration manager can be used to perform dependency analysis
 2. **Validation in progress:** when the prerequisite validation checks have still not been completed on the server 
-3. **Validation failed:** when the validation checks on the server have failed. You can select the status to review error message which would mostly be related to missing prerequisites like insufficient credential permissions or invalid credentials etc.
+3. **Validation failed:** when the validation checks on the server have failed. You can select the status to review error message which would mostly be related to missing prerequisites like insufficient credential permissions or invalid credentials etc. 
 
 After the validation succeeds, dependency analysis are auto-enabled and you see one of the following status:
 
-4. **View dependencies:** when validation checks have passed and the dependency analysis has been enabled. You can select this to go to the new visualization and review dependencies for this server.
-5. **Not initiated:** when dependency analysis couldn't be enabled as Azure Migrate has reached the scale limit of 1,000 servers per appliance for auto-enablement. If you want to perform dependency analysis on the specific servers, you can manually disable it on the other auto-enabled servers and enable for the ones you need by using the PowerShell module.
-6. **Disabled:** when dependency analysis has been manually disabled by you on this server using the PowerShell module. You can re-enable it any-time using the same PowerShell module. 
+- **View dependencies:** when validation checks have passed and the dependency analysis has been enabled. You can select this to go to the new visualization and review dependencies for this server.
+- **Not initiated:** when dependency analysis couldn't be enabled as Azure Migrate has reached the scale limit of 1,000 servers per appliance for auto-enablement. If you want to perform dependency analysis on the specific servers, you can manually disable it on the other auto-enabled servers and enable for the ones you need by using the PowerShell module.
+- **Disabled:** when dependency analysis has been manually disabled by you on this server using the PowerShell module. You can re-enable it any-time using the same PowerShell module. 
 
 ## Visualize dependencies
+::: moniker range="migrate-classic"
 
 1. In **Azure Migrate: Discovery and assessment**, select **Discovered servers**.
 1. Choose the **Appliance name** whose discovery you want to review.
@@ -106,50 +107,54 @@ After the validation succeeds, dependency analysis are auto-enabled and you see
 
 1. Expand the selected server to view process-level details for each dependency.
    :::image type="content" source="./media/how-to-create-group-machine-dependencies-agentless/expand-server-processes.png" alt-text="Expand server to show processes.":::
+::: moniker-end
 
+::: moniker range="migrate"
 1. In the new experience, go to project overview. Select the workloads count in **All inventory** to review the discovered workloads. In the view, you can see **Dependencies** column with status values as covered in section above.
-2. Search for the server whose dependencies, you want to review. If dependency analysis was successfully performed on that server, you can select on **View dependencies** to go to the dependency visualization. 
-3. The dependency visualization shows all incoming and outgoing dependencies for that server in a network diagram.
+1. Search for the server whose dependencies, you want to review. If dependency analysis was successfully performed on that server, you can select on **View dependencies** to go to the dependency visualization. 
+1. The dependency visualization shows all incoming and outgoing dependencies for that server in a network diagram.
 
     :::image type="content" source="./media/how-to-create-group-machine-dependencies-agentless/default-dep-view.png" alt-text="The screenshot shows the default dependency view for a server." lightbox="./media/how-to-create-group-machine-dependencies-agentless/default-dep-view.png":::
 
-4. The view is filtered for default time period of **Last 24 hours** and process type as **Resolvable**.
-5. Change the time period for which you want to view the map using the **Time range** filter. You can choose between **Last 7 days**/**Last 30 days** or select a **Custom range**.
-6. You can choose to change the process type from any of the following:
+1. The view is filtered for default time period of **Last 24 hours** and process type as **Resolvable**. 
+1. The view is filtered for default time period of **Last 24 hours** and process type as **Resolvable**. 
+1. Change the time period for which you want to view the map using the **Time range** filter. You can choose between **Last 7 days**/**Last 30 days** or select a **Custom range**. 
+1. You can choose to change the process type from any of the following:
 
-**Process** | **Type**
---- | --- 
-Resolvable (Default) | To filter by processes having resolvable connections
-Essentials | To filter by non-redundant key processes
-All | to filter by all processes including those with unresolved connections
+    **Process** | **Type**
+    --- | --- 
+    Resolvable (Default) | To filter by processes having resolvable connections
+    Essentials | To filter by non-redundant key processes
+    All | to filter by all processes including those with unresolved connections
 
-7. In the view, you find the servers and connections represented as follows:
+1. In the view, you find the servers and connections represented as follows:
 
-**Representation** | **Details**
---- | --- 
-Windows symbol | Representing a Windows server in the view
-Linux symbol | Representing a Linux server in the view
-Connection symbol | Representing the direction of dependency between servers with strength of the connection represented by grading of dots on the connection
-Process count | Representing the count of processes as per the process type filter
+    **Representation** | **Details**
+    --- | --- 
+    Windows symbol | Representing a Windows server in the view
+    Linux symbol | Representing a Linux server in the view
+    Connection symbol | Representing the direction of dependency between servers with strength of the connection represented by grading of dots on the connection
+    Process count | Representing the count of processes as per the process type filter
 
-8. You can hover on the Server name to see essential information about the server like IP address, Source, and Tags.
+1. You can hover on the Server name to see essential information about the server like IP address, Source, and Tags.
 
     :::image type="content" source="./media/how-to-create-group-machine-dependencies-agentless/server-hover-details.png" alt-text="The screenshot illustrated how the details are shown on hover." lightbox="./media/how-to-create-group-machine-dependencies-agentless/server-hover-details.png":::
 
-9. Similarly you can also hover on the connection to see essential information like strength and frequency of connections in the selected time range. 
-10. You can select the Server name to see more details like Operating system, Power Status, Software inventory discovered from the server and associated Tags.
+1. Similarly you can also hover on the connection to see essential information like strength and frequency of connections in the selected time range. 
+1. You can select the Server name to see more details like Operating system, Power Status, Software inventory discovered from the server and associated Tags.
 
     :::image type="content" source="./media/how-to-create-group-machine-dependencies-agentless/server-expand-details.png" alt-text="The screenshot shows the server details on expanding. " lightbox="./media/how-to-create-group-machine-dependencies-agentless/server-expand-details.png":::
 
-11. Similarly you can also select the connection to see more details like which source and destination processes have the dependency over which destination port no. 
-12. You can expand the Server to see the list of processes basis the selected process type filter.
-13. From the expanded list of processes, you can select on a Process name to see its incoming and outgoing dependencies with processes on other servers in the view. The process to process dependency also indicates the destination port no on the connection.
+1. Similarly you can also select the connection to see more details like which source and destination processes have the dependency over which destination port no. 
+1. You can expand the Server to see the list of processes basis the selected process type filter.
+1. From the expanded list of processes, you can select on a Process name to see its incoming and outgoing dependencies with processes on other servers in the view. The process to process dependency also indicates the destination port no on the connection.
 
     :::image type="content" source="./media/how-to-create-group-machine-dependencies-agentless/process-process-dep.png" alt-text="The screenshot shows the process to process dependencies." lightbox="./media/how-to-create-group-machine-dependencies-agentless/process-process-dep.png":::
 
 
 > [!NOTE]
 > Process information for a dependency isn't always available. If it's not available, the dependency is depicted with the process marked as "Unknown process".
+::: moniker-end
 
 ## Export dependency data
 
@@ -191,7 +196,7 @@ If you're an existing user who has already set up an Azure Migrate project, perf
     :::image type="content" source="./media/how-to-create-group-machine-dependencies-agentless/old-dep-view.png" alt-text="The screenshot shows the old dependency view." lightbox="./media/how-to-create-group-machine-dependencies-agentless/old-dep-view.png":::
 
 3. On the dependency view, you see an information box prompting you to complete some prerequisites for switching to the new visualization.
-4. As a prerequisite, you need to ensure that the discovery agent on the appliances registered with the project have been upgraded to version <> or above.
+4. As a prerequisite, you need to ensure that the discovery agent on the appliances registered with the project has been upgraded to version or above.
 5. Select proceed to create a new resource in the same Resource Group as the project. Ensure that you've atleast **Contributor** role on the Resource Group else this step isn't complete.
 
 > [!NOTE]
diff --git a/articles/migrate/how-to-review-discovered-inventory.md b/articles/migrate/how-to-review-discovered-inventory.md
@@ -1,17 +1,18 @@
 ---
-title: Review discovered inventory in Azure Migrate
-description:  Review discovered inventory across All inventory, Infrastructure, Databases, and web application inventory views
+title: Review discovered inventory (preview) in Azure Migrate 
+description:  This article describes how to review discovered inventory across All inventory, Infrastructure, Databases, and web application inventory views. 
 author: vikram1988
 ms.author: vibansa
 ms.manager: ronai
 ms.service: azure-migrate
 ms.topic: how-to
 ms.date: 03/15/2025
 ms.custom: engagement-fy23
----
+monikerRange: migrate
 
+---
 
-# Review discovered inventory
+# Review discovered inventory (preview)
 
 This article describes the new experience to review inventory discovered using Azure Migrate: Discovery and assessment tool. 
 
@@ -46,15 +47,15 @@ The new users need to follow steps given below:
 ## Deploy and configure the Azure Migrate appliance
 
 1. Deploy the Azure Migrate appliance to start discovery. To deploy the appliance, you can use the [deployment method](migrate-appliance.md#deployment-methods) as per your environment. After deploying the appliance, you need to register it with the project and configure it to initiate the discovery.
-2. As you configure the appliance, you need to specify the following in the appliance configuration manager:
+1. As you configure the appliance, you need to specify the following in the appliance configuration manager:
     - The details of the source environment (vCenter Server(s)/Hyper-V host(s) or cluster(s)/physical servers) which you want to discover.
     - Server credentials, which can be domain/ Windows (non-domain)/ Linux (non-domain) credentials. [Learn more](add-server-credentials.md) about how to provide credentials and how the appliance handles them.
     - Verify the permissions required to perform agentless dependency analysis. For Windows servers, you need to provide domain or non-domain (local) account with administrative permissions. For Linux servers, provide a sudo user account with permissions to execute ls and netstat commands or create a user account that has the CAP_DAC_READ_SEARCH and CAP_SYS_PTRACE permissions on /bin/netstat and /bin/ls files. If you're providing a sudo user account, ensure that you've enabled NOPASSWD for the account to run the required commands without prompting for a password every time sudo command is invoked.
 
 ### Add credentials and initiate discovery
 
 1. Open the appliance configuration manager, complete the prerequisite checks and registration of the appliance.
-2. Navigate to the **Manage credentials and discovery sources** panel.
+1. Navigate to the **Manage credentials and discovery sources** panel.
 1.  In **Step 1: Provide credentials for discovery source**, select on **Add credentials** to  provide credentials for the discovery source that the appliance uses to discover servers running in your environment.
 1. In **Step 2: Provide discovery source details**, select on **Add discovery source** to select the friendly name for credentials from the drop-down, specify the **IP address/FQDN** of the discovery source.
 
@@ -65,7 +66,7 @@ The new users need to follow steps given below:
     > [!Note]
     > If you want to perform guest based discovery features later, you can provide your intent by disabling the slider on the appliance configuration manager and proceed to start discovery of the servers from your environment.
 
-1. Select **Start discovery**, to initiate discovery.
+1. Select **Start discovery** to initiate discovery.
 
  After the discovery is complete, you can go to Azure portal and refresh the **Overview** in your project to see the count of the discovered workloads.
  
@@ -129,7 +130,7 @@ By default, searching for a workload also shows the associated workloads so that
 :::image type="content" source="./media/how-to-review-discovered-inventory/show-associated-workloads.png" alt-text="The screenshot shows the option to disable the show associated workloads option" lightbox="./media/how-to-review-discovered-inventory/show-associated-workloads.png":::
 
 
-### User actions on All inventory
+### User actions on all inventory
 
 You can perform any of the following actions after reviewing the inventory:
 
@@ -145,7 +146,7 @@ Columns | Choose optional attributes for the discovered workloads
 Refresh | Refresh the view to review any updates in discovery
 Feedback | Provide your feedback about the view and its utility
 
-### Export All inventory data
+### Export all inventory data
 
 You can export and review all inventoried workloads with associated attributes and tags. The following table summarizes the fields in the exported CSV.
 
@@ -177,11 +178,11 @@ DB engine status |
 User databases | Number of databases running on the instance
 HADR configuration | 
 
-## Review Infrastructure inventory
+## Review infrastructure inventory
 
 You can select **Infrastructure inventory** under **Explore inventory** from the menu on the left to see the list of infrastructure workloads, discovered from your environment either by using [Azure Migrate appliance](migrate-appliance.md) or using CSV import.
 
-**Infrastructure Inventory** view helps you review all the servers discovered from your datacenter including VMware VMs/Hyper-V VMs/Physical servers/servers running in other public clouds.
+**Infrastructure inventory** view helps you review all the servers discovered from your datacenter including VMware VMs/Hyper-V VMs/Physical servers/servers running in other public clouds.
 
 ### Default columns
 
@@ -232,7 +233,7 @@ You can perform actions on all or a scoped set of servers, similar to those list
  > [!Note]
  > When creating assessment for discovered servers, you can create assessment for Azure VMs and Azure VMware Solution (AVS) [Learn more]().
 
- ### Export Server inventory data
+ ### Export server inventory data
 
 You can export and review the server inventory with their associated attributes and tags. The following table summarizes the fields in the exported CSV.
 
@@ -270,7 +271,7 @@ Discovery source | Source of discovery between appliance and import
 Support ends in (Days) | Number of days for support to end
 Appliance name | Name of the appliance used to discover the workload.
 
-## Review Web apps inventory
+## Review web apps inventory
 
 You can select the name of a web app to see all the attributes and another metadata discovered for that workload in a detailed view. Here you can also add tags to an individual server. Here are the details you can review for each web app: 
 
@@ -279,7 +280,7 @@ You can select the name of a web app to see all the attributes and another metad
 Overview    |Provides overview of the Web App with basic details like Web app name, server, protocol framework, and discovery details. 
 Tags | List of custom tags applied to the web app with an option to edit or delete existing tags and add new tags. 
 
-### Scoping Web app data 
+### Scoping web app data 
 
 After reviewing the web apps and their attributes, you can either **Select all workloads across pages** or scope the list using **Search** and **Filter** capabilities to perform required action on the server inventory. 
 
diff --git a/articles/migrate/toc.yml b/articles/migrate/toc.yml
@@ -68,12 +68,14 @@ items:
             href: add-server-credentials.md
           - name: Discover SQL servers and Webapps
             href: how-to-discover-sql-existing-project.md
-          - name: Enable applications/roles/features discovery
+          - name: Discover software, databases, and web apps
             href: how-to-discover-applications.md
           - name: Appliance diagnostics
             href: troubleshoot-appliance-diagnostic.md
     - name: Discovered metadata
       href: discovered-metadata.md
+    - name: Review discovered inventory
+      href: how-to-review-discovered-inventory.md
     - name: Tags 
       href: resource-tagging.md
 - name: Create Business case
@@ -275,10 +277,6 @@ items:
       href: how-to-arc-enable-inventory.md
     - name: How to add server credentials
       href: add-server-credentials.md
-    - name: Discover applications/roles/features
-      href: how-to-discover-applications.md
-    - name: Discover SQL instances and web apps in an existing project
-      href: how-to-discover-sql-existing-project.md
     - name: Migrate to Azure Monitor agent
       href: azure-monitor-agent-migration.md
     - name: Analyze machine dependencies (agent-based)
diff --git a/articles/migrate/whats-new.md b/articles/migrate/whats-new.md
@@ -14,6 +14,10 @@ ms.custom: mvc, engagement-fy25
 
 [Azure Migrate](migrate-services-overview.md) helps you to discover, assess and migrate on-premises servers, apps, and data to the Microsoft Azure cloud. This article summarizes new releases and features in Azure Migrate.
 
+## Update (April 2025)
+
+Public Preview: Explore inventory of discovered workloads across the Infrastructure, Data, and Web tiers. Utilize the new experience of the dependency analysis to identify application boundaries and group workloads into applications using Tags. [Learn more](how-to-review-discovered-inventory.md).
+
 ## Update (February 2025)
 
 Public Preview: Azure Migrate now supports discovery and assessment of MySQL databases. You can use this capability to discover MySQL instances and their attributes within your environment, assess their readiness for migration to Azure Database for MySQL, and obtain recommendations on the suitable compute and storage options, along with the associated costs. [Learn more](assessments-overview-migrate-to-azure-db-mysql.md).
