Merge pull request #105274 from rayne-wiselman/raynefebruary24

Raynefebruary24

Author: ttorble

articles/migrate/common-questions-discovery-assessment.md

@@ -88,7 +88,7 @@ You don't need these agents unless you're using dependency visualization.
 
 ## Can I use an existing workspace?
 
-Yes, you can attach an existing workspace to the migration project and use it for dependency visualization. [Learn more](concepts-dependency-visualization.md#how-does-it-work).
+Yes, you can attach an existing workspace to the migration project and use it for dependency visualization. 
 
 ## Can I export the dependency visualization report?
 

articles/migrate/concepts-dependency-visualization.md

@@ -2,89 +2,60 @@
 title: Dependency visualization in Azure Migrate
 description: Provides an overview of assessment calculations in the Server Assessment service in Azure Migrate
 ms.topic: conceptual
-ms.date: 02/17/2020
+ms.date: 02/24/2020
 ---
 
 # Dependency visualization
 
-This article describes the dependency visualization feature in Azure Migrate: Server Assessment.
+This article describes dependency visualization in Azure Migrate:Server Assessment.
 
-Dependency visualization helps you to understand dependencies across machines that you want to assess and migrate. You typically use dependency mapping when you want to assess machines with higher levels of confidence.
+## What is dependency visualization?
 
-- In Azure Migrate: Server Assessment, you gather machines together into groups for assessment. Groups usually consist of machines that you want to migrate together, and dependency visualization helps you to cross-check machine dependencies, so that you can group machines accurately.
-- Using visualization, you can discover interdependent systems that need to migrate together. You can identify whether running systems are still in use, or whether systems can be decommissioned instead of migrated.
+Dependency visualization helps you to identify dependencies between on-premises machines that you want to assess and migrate to Azure. 
+
+- In Azure Migrate:Server Assessment, you gather machines into a group, and then assess the group. Dependency visualization helps you to group machines more accurately, with high confidence for assessment.
+- Dependency visualization enables you to identify machines that must be migrated together. You can identify whether machines are in use, or if they can be decommissioned instead of migrated.
 - Visualizing dependencies helps ensure that nothing is left behind, and avoid surprise outages during migration.
-- This feature is especially useful if you're not completely aware of machines that are part of apps, and thus should be migrated together to Azure.
+- Visualization is especially useful if you're not sure whether machines are part of an app deployment that you want to migrate to Azure.
 
 
 > [!NOTE]
-> The dependency visualization functionality is not available in Azure Government.
+> Dependency visualization isn't available in Azure Government.
 
-## Agent-based and agentless
+## Agent-based/agentless visualization
 
 There are two options for deploying dependency visualization:
 
-- **Agentless dependency visualization**: This option is currently in preview and is available only for VMware VMs. It doesn't require you to install any agents on machines. 
-    - It works by capturing the TCP connection data from machines for which it's enabled. [Learn more](how-to-create-group-machine-dependencies-agentless.md).
-After dependency discovery is started, the appliance gathers data from machines at a polling interval of five minutes.
-    - The following data is collected:
-        - TCP connections
-        - Names of processes that have active connections
-        - Names of installed applications that run the above processes
-        - No. of connections detected at every polling interval
-- **Agent-based dependency visualization**: To use agent-based dependency visualization, you need to download and install the following agents on each on-premises machine that you want to analyze.  
-    - [Microsoft Monitoring agent (MMA)](https://docs.microsoft.com/azure/log-analytics/log-analytics-agent-windows) needs to be installed on each machine. [Learn more](https://docs.microsoft.com/azure/migrate/how-to-create-group-machine-dependencies#install-the-mma) about how to install the MMA agent.
-    - The [Dependency agent](../azure-monitor/platform/agents-overview.md#dependency-agent) needs to be installed on each machine. [Learn more](https://docs.microsoft.com/azure/migrate/how-to-create-group-machine-dependencies#install-the-dependency-agent) about how to install the dependency agent.
-    - In addition, if you have machines with no internet connectivity, you need to download and install Log Analytics gateway on them.
-
-## Agent-based requirements
-
-### What do I need to deploy dependency visualization?
-
-Before you deploy dependency visualization you should have an Azure Migrate project in place, with the Azure Migrate: Server Assessment tool added to the project. You deploy dependency visualization after setting up an Azure Migrate appliance to discover your on-premises machines.
-
-[Learn more](how-to-assess.md) about adding the tool, and deploying an appliance for [Hyper-V](how-to-set-up-appliance-hyper-v.md), [VMware](how-to-set-up-appliance-vmware.md), or physical servers.
-
-
-### How does it work?
-
-Azure Migrate uses the [Service Map](../operations-management-suite/operations-management-suite-service-map.md) solution in [Azure Monitor logs](../log-analytics/log-analytics-overview.md) for dependency visualization.
+- **Agent-based**: Agent-based dependency visualization requires agents to be installed on each on-premises machine that you want to analyze.
+- **Agentless**: With this option, you don't need to install agents on machines you want to cross-check. This option is currently in preview, and is only available for VMware VMs.
 
-- To leverage dependency visualization, you need to associate a Log Analytics workspace (new or existing), with an Azure Migrate project.
-- The workspace must be in the same subscription as that in which you create the Azure Migrate project.
-- Azure Migrate supports workspaces residing in the East US, Southeast Asia and West Europe regions. Workspaces in other regions can't be associated with a project. Also, note that the workspace must be in a region in which [Service Map is supported](../azure-monitor/insights/vminsights-enable-overview.md#prerequisites).
-- The workspace for an Azure Migrate project can't be modified after it's added.
-- In Log Analytics, the workspace associated with Azure Migrate is tagged with the Migration Project key, and the project name.
 
-    ![Navigate Log Analytics workspace](./media/concepts-dependency-visualization/oms-workspace.png)
+## Agent-based visualization
 
+**Requirement** | **Details** | **Learn more**
+--- | --- | ---
+**Before deployment** | You should have an Azure Migrate project in place, with the Azure Migrate: Server Assessment tool added to the project.<br/><br/>  You deploy dependency visualization after setting up an Azure Migrate appliance to discover your on-premises machines. | [Learn how](create-manage-projects.md) to create a project for the first time.<br/><br/> [Learn how](how-to-assess.md) to add an assessment tool to an existing project.<br/><br/> Learn how to set up the Azure Migrate appliance for assessment of [Hyper-V](how-to-set-up-appliance-hyper-v.md), [VMware](how-to-set-up-appliance-vmware.md), or physical servers.
+**Required agents** | On each machine you want to analyze, install the following agents:<br/><br/> The [Microsoft Monitoring agent (MMA)](https://docs.microsoft.com/azure/log-analytics/log-analytics-agent-windows).<br/><br/> The [Dependency agent](../azure-monitor/platform/agents-overview.md#dependency-agent).<br/><br/> If on-premises machines aren't connected to the internet, you need to download and install Log Analytics gateway on them. | Learn more about installing the [Dependency agent](how-to-create-group-machine-dependencies.md#install-the-dependency-agent) and [MMA](how-to-create-group-machine-dependencies.md#install-the-mma).
+**Log Analytics** | Azure Migrate uses the [Service Map](../operations-management-suite/operations-management-suite-service-map.md) solution in [Azure Monitor logs](../log-analytics/log-analytics-overview.md) for dependency visualization.<br/><br/> You associate a new or existing Log Analytics workspace with an Azure Migrate project. The workspace for an Azure Migrate project can't be modified after it's added. <br/><br/> The workspace must be in the same subscription as the Azure Migrate project.<br/><br/> The workspace must reside in the East US, Southeast Asia, or West Europe regions. Workspaces in other regions can't be associated with a project.<br/><br/> The workspace must be in a region in which [Service Map is supported](../azure-monitor/insights/vminsights-enable-overview.md#prerequisites).<br/><br/> In Log Analytics, the workspace associated with Azure Migrate is tagged with the Migration Project key, and the project name.
+**Costs** | The Service Map solution doesn't incur any charges for the first 180 days (from the day that you associate the Log Analytics workspace with the Azure Migrate project)/<br/><br/> After 180 days, standard Log Analytics charges will apply.<br/><br/> Using any solution other than Service Map in the associated Log Analytics workspace will incur [standard charges](https://azure.microsoft.com/pricing/details/log-analytics/) for Log Analytics.<br/><br/> When the Azure Migrate project is deleted, the workspace is not deleted along with it. After deleting the project, Service Map usage isn't free, and each node will be charged as per the paid tier of Log Analytics workspace/<br/><br/>If you have projects that you created before Azure Migrate general availability (GA- 28 February 2018), you might have incurred additional Service Map charges. To ensure payment after 180 days only, we recommend that you create a new project, since existing workspaces before GA are still chargeable.
+**Management** | When you register agents to the workspace, you use the ID and key provided by the Azure Migrate project.<br/><br/> You can use the Log Analytics workspace outside Azure Migrate.<br/><br/> If you delete the associated Azure Migrate project, the workspace isn't deleted automatically. [Delete it manually](../azure-monitor/platform/manage-access.md).<br/><br/> Don't delete the workspace created by Azure Migrate, unless you delete the Azure Migrate project. If you do, the dependency visualization functionality will not work as expected.
 
-
-### Do I need to pay for it?
-
-Dependency visualization requires Service Map and an associated Log Analytics workspace. 
-
-- The Service Map solution doesn't incur any charges for the first 180 days. This is from the day that you associated the Log Analytics workspace with the Azure Migrate project.
-- After 180 days, standard Log Analytics charges will apply.
-- Using any solution other than Service Map in the associated Log Analytics workspace will incur [standard Log Analytics](https://azure.microsoft.com/pricing/details/log-analytics/) charges.
-- When the Azure Migrate project is deleted, the workspace is not deleted along with it. After deleting the project, Service Map usage isn't free, and each node will be charged as per the paid tier of Log Analytics workspace.
-
-Learn more about Azure Migrate pricing [here](https://azure.microsoft.com/pricing/details/azure-migrate/).
-
-> [!NOTE]
-> If you have projects that you created before Azure Migrate general availability in 28 February 2018, you might have incurred additional Service Map charges. To ensure you only pay after 180 days, we recommend that you create a new project, since existing workspaces before general availability are still chargeable.
-
+## Agentless visualization
 
 
-### How do I manage the workspace?
+**Requirement** | **Details** | **Learn more**
+--- | --- | ---
+**Before deployment** | You should have an Azure Migrate project in place, with the Azure Migrate: Server Assessment tool added to the project.<br/><br/>  You deploy dependency visualization after setting up an Azure Migrate appliance to discover your on-premises VMWare machines. | [Learn how](create-manage-projects.md) to create a project for the first time.<br/><br/> [Learn how](how-to-assess.md) to add an assessment tool to an existing project.<br/><br/> Learn how to set up the Azure Migrate appliance for assessment of [VMware](how-to-set-up-appliance-vmware.md) VMs.
+**Required agents** | No agent required on machines you want to analyze.
+**Supported operating systems** | Review the [operating systems](migrate-support-matrix-vmware.md#agentless-dependency-visualization) supported for agentless visualization.
+**VMs** | **VMware tools**: VMware Tools must be installed and running on VMs you want to analyze.<br/><br/> **Account**: On the Azure Migrate appliance, you need to add a user account that can be used to access VMs for analysis.<br/><br/> **Windows VMs**: The user account needs to be a local or a domain administrator on the machine.<br/><br/> **Linux VMs**: The root privilege is required on the account. Alternately, the user account requires these two capabilities on /bin/netstat and /bin/ls files: CAP_DAC_READ_SEARCH and CAP_SYS_PTRACE. | [Learn about](migrate-appliance.md) the Azure Migrate appliance.
+**VMware** | **vCenter**: The appliance needs a vCenter Server account with read-only access, and privileges enabled for Virtual Machines > Guest Operations.<br/><br/> **ESXi hosts**: On ESXi hosts running VMs you want to analyze, the Azure Migrate appliance must be able to connect to TCP port 443.
+**Collected data** |  Agentless dependency visualization works by capturing TCP connection data from machines for which it's enabled. After dependency discovery starts, the appliance gathers this data from machines by polling every five minutes:<br/> - TCP connections.<br/> - Names of processes that have active connections.<br/> - Names of installed applications that run the process with active connections.<br/> - The number of connections detected at every polling interval.
 
-- When you register agents to the workspace, you use the ID and key provided by the Azure Migrate project.
-- You can use the Log Analytics workspace outside Azure Migrate.
-- If you delete the associated Azure Migrate project, the workspace isn't deleted automatically. You need to [delete it manually](../azure-monitor/platform/manage-access.md).
-- Don't delete the workspace created by Azure Migrate, unless you delete the Azure Migrate project. If you do, the dependency visualization functionality will not work as expected.
 
 ## Next steps
-- [Group machines using machine dependencies](how-to-create-group-machine-dependencies.md)
-- [Learn more](common-questions-discovery-assessment.md#what-is-dependency-visualization) about the FAQs on dependency visualization.
+- [Set up dependency visualization](how-to-create-group-machine-dependencies.md)
+- [Try out agentless dependency visualization](how-to-create-group-machine-dependencies-agentless.md) for VMware VMs.
+- Review [common questions](common-questions-discovery-assessment.md#what-is-dependency-visualization) about dependency visualization.