Acro

v-sreedevank · v-sreedevank · commit 72ebf3f2c2d3 · 2024-11-29T17:30:01.000+05:30
diff --git a/articles/migrate/how-to-create-group-machine-dependencies-agentless.md b/articles/migrate/how-to-create-group-machine-dependencies-agentless.md
@@ -6,7 +6,7 @@ ms.author: vibansa
 ms.manager: abhemraj
 ms.service: azure-migrate
 ms.topic: how-to
-ms.date: 12/12/2022
+ms.date: 06/30/2023
 ms.custom: engagement-fy25
 ---
 
@@ -17,22 +17,22 @@ This article describes how to set up agentless dependency analysis using Azure M
 
 ## Current limitations
 
-- In the dependency analysis view, you currently cannot add or remove a server from a group.
+- In the dependency analysis view, you currently can't add or remove a server from a group.
 - A dependency map for a group of servers isn't currently available.
-- In an Azure Migrate project, you can enable dependency data collection concurrently for 1000 servers per appliance. 
-- You can analyze more than 1000 servers per project either by enabling dependency analysis concurrently on servers discovered by multiple appliances or by sequencing in batches of 1000 for servers discovered from one appliance.
+- In an Azure Migrate project, you can enable dependency data collection concurrently for 1,000 servers per appliance. 
+- You can analyze more than 1,000 servers per project either by enabling dependency analysis concurrently on servers discovered by multiple appliances or by sequencing in batches of 1000 for servers discovered from one appliance.
 
 ## Before you start
 
-- Ensure that you have [created a project](./create-manage-projects.md) with the Azure Migrate: Discovery and assessment tool added to it.
-- Review the requirements based on your environment and the appliance you are setting up to perform software inventory:
+- Ensure that you [created a project](./create-manage-projects.md) with the Azure Migrate: Discovery and assessment tool added to it.
+- Review the requirements based on your environment and the appliance you're setting up to perform software inventory:
 
     Environment | Requirements
     --- | ---
     Servers running in VMware environment | Review [VMware requirements](migrate-support-matrix-vmware.md#vmware-requirements) <br/> Review [appliance requirements](migrate-appliance.md#appliance---vmware)<br/> Review [port access requirements](migrate-support-matrix-vmware.md#port-access-requirements) <br/> Review [agentless dependency analysis requirements](migrate-support-matrix-vmware.md#dependency-analysis-requirements-agentless)
     Servers running in Hyper-V environment | Review [Hyper-V host requirements](migrate-support-matrix-hyper-v.md#hyper-v-host-requirements) <br/> Review [appliance requirements](migrate-appliance.md#appliance---hyper-v)<br/> Review [port access requirements](migrate-support-matrix-hyper-v.md#port-access)<br/> Review [agentless dependency analysis requirements](migrate-support-matrix-hyper-v.md#dependency-analysis-requirements-agentless)
     Physical servers or servers running on other clouds | Review [server requirements](migrate-support-matrix-physical.md#physical-server-requirements) <br/> Review [appliance requirements](migrate-appliance.md#appliance---physical)<br/> Review [port access requirements](migrate-support-matrix-physical.md#port-access)<br/> Review [agentless dependency analysis requirements](migrate-support-matrix-physical.md#dependency-analysis-requirements-agentless)
-- Review the Azure URLs that the appliance will need to access in the [public](migrate-appliance.md#public-cloud-urls) and [government clouds](migrate-appliance.md#government-cloud-urls).
+- Review the Azure URLs that the appliance need to access in the [public](migrate-appliance.md#public-cloud-urls) and [government clouds](migrate-appliance.md#government-cloud-urls).
 
 
 ## Deploy and configure the Azure Migrate appliance
@@ -41,19 +41,19 @@ This article describes how to set up agentless dependency analysis using Azure M
 2. 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 have enabled NOPASSWD for the account to run the required commands without prompting for a password every time sudo command is invoked.
+    - 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 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.  In **Step 1: Provide credentials for discovery source**, click on **Add credentials** to  provide credentials for the discovery source that the appliance will use to discover servers running in your environment.
-1. In **Step 2: Provide discovery source details**, click on **Add discovery source** to select the friendly name for credentials from the drop-down, specify the **IP address/FQDN** of the discovery source.
+2. Navigate to the **Managed credentials and discovery sources** panel.
+1.  In **Step 1: Provide credentials for discovery source**, select **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 **Add discovery source** to select the friendly name for credentials from the drop-down, specify the **IP address/FQDN** of the discovery source.
 :::image type="content" source="./media/tutorial-discover-vmware/appliance-manage-sources.png" alt-text="Panel 3 on appliance configuration manager for vCenter Server details.":::
-1. In **Step 3: Provide server credentials to perform software inventory and agentless dependency analysis**, click **Add credentials** to provide multiple server credentials to perform software inventory.
-1. Click on **Start discovery**, to initiate discovery.
+1. In **Step 3: Provide server credentials to perform software inventory and agentless dependency analysis**, select **Add credentials** to provide multiple server credentials to perform software inventory.
+1. Select **Start discovery**, to initiate discovery.
 
- 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.
+ 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.
  
  > [!Note]
  > You can enable agentless dependency analysis for discovered servers from Azure Migrate project. Only the servers where the validation succeeds can be selected to enable agentless dependency analysis.
@@ -64,28 +64,28 @@ This article describes how to set up agentless dependency analysis using Azure M
 
 Select the servers on which you want to enable dependency discovery.
 
-1. In **Azure Migrate: Discovery and assessment**, click **Discovered servers**.
+1. In **Azure Migrate: Discovery and assessment**, select **Discovered servers**.
 2. Choose the **Appliance name** whose discovery you want to review.
 1. You can see the validation status of the servers under **Dependencies (agentless)** column.
-1. Click the **Dependency analysis** drop-down.
-1. Click **Add servers**.
+1. Select the **Dependency analysis** drop-down.
+1. Select **Add servers**.
 1. In the **Add servers** page, select the servers where you want to enable dependency analysis. You can enable dependency mapping only on those servers where validation succeeded. The next validation cycle will run 24 hours after the last validation timestamp.
-1. After selecting the servers, click **Add servers**.
+1. After selecting the servers, select **Add servers**.
 
 :::image type="content" source="./media/how-to-create-group-machine-dependencies-agentless/start-dependency-discovery.png" alt-text="Screenshot of process to start dependency analysis.":::
 
 You can visualize dependencies around six hours after enabling dependency analysis on servers. If you want to simultaneously enable multiple servers for dependency analysis, you can use [PowerShell](#start-or-stop-dependency-analysis-using-powershell) to do so.
 
 ## Visualize dependencies
 
-1. In **Azure Migrate: Discovery and assessment**, click **Discovered servers**.
+1. In **Azure Migrate: Discovery and assessment**, select **Discovered servers**.
 1. Choose the **Appliance name** whose discovery you want to review.
 1. Search for the server whose dependencies, you want to review.
-1. Under the **Dependencies (agentless)** column, click **View dependencies**
+1. Under the **Dependencies (agentless)** column, select **View dependencies**
 1. Change the time period for which you want to view the map using the **Time duration** dropdown.
 1. Expand the **Client** group to list the servers with a dependency on the selected server.
 1. Expand the **Port** group to list the servers that have a dependency from the selected server.
-1. To navigate to the map view of any of the dependent servers, click on the server name > **Load server map**
+1. To navigate to the map view of any of the dependent servers, select the server name > **Load server map**
 :::image type="content" source="./media/how-to-create-group-machine-dependencies-agentless/load-server-map.png" alt-text="Screenshot to Expand Server port group and load server map.":::
 :::image type="content" source="./media/how-to-create-group-machine-dependencies-agentless/expand-client-group.png" alt-text="Expand client group.":::
 
@@ -97,12 +97,12 @@ You can visualize dependencies around six hours after enabling dependency analys
 
 ## Export dependency data
 
-1. In **Azure Migrate: Discovery and assessment**, click **Discovered servers**.
-2. Click the **Dependency analysis** drop-down.
-3. Click **Export application dependencies**.
+1. In **Azure Migrate: Discovery and assessment**, select **Discovered servers**.
+2. Select the **Dependency analysis** drop-down.
+3. Select **Export application dependencies**.
 4. In the **Export application dependencies** page, choose the appliance name that is discovering the desired servers.
 5. Select the start time and end time. Note that you can download the data only for the last 30 days.
-6. Click **Export dependency**.
+6. Select **Export dependency**.
 
 The dependency data is exported and downloaded in a CSV format. The downloaded file contains the dependency data across all servers enabled for dependency analysis. 
 :::image type="content" source="./media/how-to-create-group-machine-dependencies-agentless/export.png" alt-text="Screenshot to Export dependencies.":::
@@ -111,7 +111,7 @@ The dependency data is exported and downloaded in a CSV format. The downloaded f
 
 Each row in the exported CSV corresponds to a dependency observed in the specified time slot.
 
-The following table summarizes the fields in the exported CSV. Note that server name, application and process fields are populated only for servers that have agentless dependency analysis enabled.
+The following table summarizes the fields in the exported CSV. Note that server name, application, and process fields are populated only for servers that have agentless dependency analysis enabled.
 
 **Field name** | **Details**
 --- | --- 
@@ -129,12 +129,12 @@ Destination port | Port number on the destination server
 
 Select the servers on which you want to stop dependency discovery.
 
-1. In **Azure Migrate: Discovery and assessment**, click **Discovered servers**.
+1. In **Azure Migrate: Discovery and assessment**, select **Discovered servers**.
 1. Choose the **Appliance name** whose discovery you want to review.
-1. Click the **Dependency analysis** drop-down.
-1. Click **Remove servers**.
+1. Select the **Dependency analysis** drop-down.
+1. Select **Remove servers**.
 1. In the **Remove servers** page, select the server, which you want to stop for dependency analysis.
-1. After selecting the servers,click **Remove servers**.
+1. After selecting the servers, click **Remove servers**.
 
 If you want to stop dependency simultaneously on multiple servers, you can use [PowerShell](#start-or-stop-dependency-analysis-using-powershell) to do so.
 
@@ -144,7 +144,7 @@ Download the PowerShell module from [Azure PowerShell Samples](https://github.co
 
 ### Log in to Azure
 
-1. Log into your Azure subscription using the Connect-AzAccount cmdlet.
+1. Log in to your Azure subscription using the Connect-AzAccount cmdlet.
 
     ```PowerShell
     Connect-AzAccount
@@ -196,8 +196,8 @@ Azure Migrate offers a Power BI template that you can use to visualize network c
 
 1. Download the PowerShell module and the Power BI template from [Azure PowerShell Samples](https://github.com/Azure/azure-docs-powershell-samples/tree/master/azure-migrate/dependencies-at-scale) repo on GitHub.
 
-2. Log in to Azure using the below instructions: 
-    - Log into your Azure subscription using the Connect-AzAccount cmdlet.
+2. Sign in to Azure using the below instructions: 
+    - Log in to your Azure subscription using the Connect-AzAccount cmdlet.
 
         ```PowerShell
         Connect-AzAccount
@@ -221,7 +221,7 @@ Azure Migrate offers a Power BI template that you can use to visualize network c
     Import-Module .\AzMig_Dependencies.psm1
     ```
 
-4. Run the following command. This command downloads the dependencies data in a CSV and processes it to generate a list of unique dependencies that can be used for visualization in Power BI. In the example below the project name is FabrikamDemoProject, and the resource group it belongs to is FabrikamDemoRG. The dependencies will be downloaded for servers discovered by FabrikamAppliance. The unique dependencies will be saved in FabrikamDemo_Dependencies.csv
+4. Run the following command. This command downloads the dependencies data in a CSV and processes it to generate a list of unique dependencies that can be used for visualization in Power BI. In the example below the project name is FabrikamDemoProject, and the resource group it belongs to is FabrikamDemoRG. The dependencies will be downloaded for servers discovered by FabrikamAppliance. The unique dependencies are saved in FabrikamDemo_Dependencies.csv
 
     ```PowerShell
     Get-AzMigDependenciesAgentless -ResourceGroup FabrikamDemoRG -Appliance FabrikamAppliance -ProjectName FabrikamDemoProject -OutputCsvFile "FabrikamDemo_Dependencies.csv"
@@ -231,12 +231,12 @@ Azure Migrate offers a Power BI template that you can use to visualize network c
 
 6. Load the downloaded dependency data in Power BI.
     - Open the template in Power BI.
-    - Click on **Get Data** on the tool bar. 
+    - Select **Get Data** on the tool bar. 
     - Choose **Text/CSV** from Common data sources.
     - Choose the dependencies file downloaded.
-    - Click **Load**.
-    - You will see a table is imported with the name of the CSV file. You can see the table in the fields bar on the right. Rename it to AzMig_Dependencies
-    - Click on refresh from the tool bar.
+    - Select **Load**.
+    - You'll see a table is imported with the name of the CSV file. You can see the table in the fields bar on the right. Rename it to AzMig_Dependencies
+    - Select refresh from the tool bar.
 
     The Network Connections chart and the Source server name, Destination server name, Source process name, Destination process name slicers should light up with the imported data.
 
