Merge branch 'release-migrate-new-structure' into 09Apr-new-article-update

Author: habibaum

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

@@ -15,23 +15,31 @@ ms.custom: engagement-fy25
 
 This article describes how to set up agentless dependency analysis using Azure Migrate: Discovery and assessment tool. [Dependency analysis](concepts-dependency-visualization.md) helps you to identify and understand dependencies across servers for assessment and migration to Azure.
 
+::: moniker range="migrate"
  > [!Note]
  > In this article, you'll explore the new experience with agentless dependency analysis. You should continue only if you've upgraded to the new experience by following these [prerequisites](./how-to-create-group-machine-dependencies-agentless.md#switch-to-new-visualization).
+::: moniker-end
 
+::: moniker range="migrate-classic"
 ## Current limitations
 
 - In the dependency analysis view, currently you can't add or remove a server from a group.
 - A dependency map for a group of servers isn't currently available.
+::: moniker-end
 
+::: moniker range="migrate"
 ## What's New?
 
 - Dependency analysis is automatically enabled on 1,000 servers discovered by each Azure Migrate appliance that has passed the prerequisite checks. You no longer need to enable the dependency analysis on servers manually as before.
 - The enhanced dependency visualization helps you review additional information about the servers, connections, and processes. You can filter the view by process type to analyze key dependencies in the visualization.
 - In the new visualization, after identifying key dependencies, you can group servers into an application by tagging them.
+::: moniker-end
 
 ## Before you start
 
+::: moniker range="migrate"
 The existing users can follow steps provided [here](how-to-create-group-machine-dependencies-agentless.md#switch-to-new-visualization)
+::: moniker-end
 
 The new users need to follow the below steps:
 
@@ -68,30 +76,43 @@ The new users need to follow the below steps:
 
  After the server discovery is complete, appliance initiates the discovery of installed applications, roles, and features (software inventory) on the servers. During software inventory, the discovered servers are validated to check if they meet the prerequisites and can be enabled for agentless dependency analysis.
 
+::: moniker range="migrate"
  > [!Note]
  > Agentless dependency analysis feature is automatically enabled for the discovered servers when the prerequisite checks are successful. Unlike before, you no longer need to manually enable this feature on servers.
+::: moniker-end
 
- After servers are automatically enabled for agentless dependency analysis, appliance collects dependency data from the server every 5 mins. It then sends a combined data point every six hours. You can review the [data](discovered-metadata.md#application-dependency-data) collected by appliance during analysis.
+::: moniker range="migrate-classic" 
+After servers are enabled for agentless dependency analysis, appliance collects dependency data from the server every 5 mins. It then sends a combined data point every six hours. You can review the [data](discovered-metadata.md#application-dependency-data) collected by appliance during analysis.
+::: moniker-end
+
+::: moniker range="migrate"
+After servers are automatically enabled for agentless dependency analysis, appliance collects dependency data from the server every 5 mins. It then sends a combined data point every six hours. You can review the [data](discovered-metadata.md#application-dependency-data) collected by appliance during analysis.
+::: moniker-end
 
 ## Review dependency status
 
-After initiating discovery from the appliance, you can come to Migrate project on the Azure portal and review the dependency data. It's recommended to wait for **atleast 24 hours** to allow for enough dependendency data to be gathered for your servers and show in a visualization. 
+After initiating discovery from the appliance, you can come to Migrate project on the Azure portal and review the dependency data. We recommend that you wait for **atleast 24 hours** to allow for enough dependendency data to be gathered for your servers and show in a visualization. 
 
 In the project, you can review dependencies for each server either through the **All inventory** or **Infrastructure inventory** view. 
 
 On reviewing the **Dependencies** column for any server, you see one of the following status:
 
 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. 
 
+::: moniker range="migrate"
 After the validation succeeds, dependency analysis are auto-enabled and you see one of the following status:
+::: moniker-end
 
-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.
+::: moniker range="migrate"
+- **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. 
+::: moniker-end
 
 ## 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 +127,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
 
@@ -181,6 +206,7 @@ Destination application | Name of the application on the destination server
 Destination process | Name of the process on the destination server  
 Destination port | Port number on the destination server
 
+::: moniker range="migrate"
 ## Switch to new visualization
 
 If you're an existing user who has already set up an Azure Migrate project, performed discovery and manually enabled dependency analysis on some servers, you need to perform following steps to get the new enhanced visualization:
@@ -191,7 +217,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]
@@ -221,6 +247,7 @@ Dependency analysis is auto-enabled on all discovered servers which have passed
 
 > [!NOTE]
 > Currently, it isn't possible to disable dependendency analysis on servers from portal so you need to install the PowerShell module to disable for servers that you don't want.
+::: moniker-end
 
 ### Log in to Azure