Merge pull request #109466 from rayne-wiselman/raynemarch30

updating links and sections

Author: ShannonLeavitt

articles/migrate/migrate-appliance-architecture.md

@@ -8,18 +8,18 @@ ms.date: 03/23/2020
 
 # Azure Migrate appliance architecture
 
-This article describes the Azure Migrate appliance architecture and processes. The Azure Migrate appliance is a lightweight appliance that's deployed on premises, to discover VMs and physical servers that you want to assess for migration to Azure. 
+This article describes the Azure Migrate appliance architecture and processes. The Azure Migrate appliance is a lightweight appliance that's deployed on premises, to discover VMs and physical servers for migration to Azure. 
 
 ## Deployment scenarios
 
 The Azure Migrate appliance is used in the following scenarios.
 
 **Scenario** | **Tool** | **Used for** 
 --- | --- | ---
-**VMware VM assessment** | Azure Migrate: Server Assessment | Discover VMware VMs.<br/><br/> Discover machine apps and dependencies.<br/><br/> Collect machine metadata and performance metadata and send to Azure.
-**VMware VM migration (agentless)** | Azure Migrate: Server Migration | Discover VMware VMs<br/><br/>  Replicate VMware VMs with [agentless migration](server-migrate-overview.md).
-**Hyper-V VM assessment** | Azure Migrate: Server Assessment | Discover Hyper-V VMs.<br/><br/> Collect machine metadata and performance metadata and send to Azure.
-**Physical machine** |  Azure Migrate: Server Assessment |  Discover physical servers.<br/><br/> Collect machine metadata and performance metadata and send to Azure.
+**VMware VM assessment** | Azure Migrate:Server Assessment | Discover VMware VMs.<br/><br/> Discover machine apps and dependencies.<br/><br/> Collect machine metadata and performance metadata and send to Azure.
+**VMware VM migration (agentless)** | Azure Migrate:Server Migration | Discover VMware VMs<br/><br/>  Replicate VMware VMs with [agentless migration](server-migrate-overview.md).
+**Hyper-V VM assessment** | Azure Migrate:Server Assessment | Discover Hyper-V VMs.<br/><br/> Collect machine metadata and performance metadata and send to Azure.
+**Physical machine** |  Azure Migrate:Server Assessment |  Discover physical servers.<br/><br/> Collect machine metadata and performance metadata and send to Azure.
 
 ## Appliance components
 
@@ -36,25 +36,25 @@ The appliance has a number of components.
 
 ## Appliance deployment
 
-- The Azure Migrate appliance can be set up using a template (Hyper-V or VMware only) or a PowerShell script installer. [Learn more](deploy-appliance.md#deployment-options) about the options. 
+- The Azure Migrate appliance can be set up using a template for [Hyper-V](how-to-set-up-appliance-hyper-v.md) or [VMware](how-to-set-up-appliance-vmware.md) or using a PowerShell script installer for [VMware/Hyper-V](deploy-appliance-script.md), and for [physical servers](how-to-set-up-appliance-physical.md). 
 - Appliance support requirements and deployment prerequisites are summarized in the [appliance support matrix](migrate-appliance.md).
 
 
 ## Appliance registration
 
-During appliance setup, you register the appliance with Azure Migrate.During setup and registration the actions summarized in the table occur.
+During appliance setup, you register the appliance with Azure Migrate, and the actions summarized in the table occur.
 
 **Action** | **Details** | **Permissions**
 --- | --- | ---
 **Register source providers** | These resources providers are registered in the subscription you choose during appliance setup: Microsoft.OffAzure, Microsoft.Migrate and Microsoft.KeyVault.<br/><br/> Registering a resource provider configures your subscription to work with the resource provider. | To register the resource providers, you need a Contributor or Owner role on the subscription.
-**Create Azure AD app-communication** | Azure Migrate creates an Azure Active Directory (Azure AD) app for communication (authentication and authorization) between the agents running on the appliance, and their respective services running on Azure.<br/><br/> This app does not have privileges to make Azure resource manager calls, or RBAC access on any resource. | You need [these permissions](tutorial-prepare-vmware.md#assign-permissions-to-register-the-appliance) for Azure Migrate to create the app.
+**Create Azure AD app-communication** | Azure Migrate creates an Azure Active Directory (Azure AD) app for communication (authentication and authorization) between the agents running on the appliance, and their respective services running on Azure.<br/><br/> This app does not have privileges to make Azure Resource Manager calls, or RBAC access on any resource. | You need [these permissions](tutorial-prepare-vmware.md#assign-permissions-to-register-the-appliance) for Azure Migrate to create the app.
 **Create Azure AD apps-Key vault** | This app is created only for agentless migration of VMware VMs to Azure.<br/><br/> It's used exclusively to access the key vault created in the user's subscription for agentless migration.<br/><br/> It has RBAC access on the Azure key vault (created in customer's tenant), when discovery is initiated from the appliance. | You need [these permissions](tutorial-prepare-vmware.md#assign-permissions-to-register-the-appliance) for Azure Migrate to create the app.
 
 
 
 ## Collected data
 
-Data collected by the client for all deployment scenarios is captured fully in the [appliance support matrix](migrate-appliance.md).
+Data collected by the client for all deployment scenarios is summarized in the [appliance support matrix](migrate-appliance.md).
 
 ## Discovery and collection process
 
@@ -85,7 +85,8 @@ The appliance communicates with vCenter Servers and Hyper-V hosts/cluster using
 
 The appliance is upgraded as the Azure Migrate agents running on the appliance are updated. This happens automatically because auto-update is enabled on the appliance by default. You can change this default setting to update the agents manually.
 
-You turn off auto-update in the registry by setting HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AzureAppliance "AutoUpdate" key to 0 (DWORD). If you decide to use manual updates, it's important to update all agents on the appliance at the same time, using the  **Update** button for each outdated agent on the appliance.
+You turn off auto-update in the registry by setting the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AzureAppliance "AutoUpdate" key to 0 (DWORD).
+
 
 
 ## Next steps

articles/migrate/migrate-support-matrix-hyper-v.md

@@ -7,9 +7,9 @@ ms.date: 03/23/2020
 
 # Support matrix for Hyper-V assessment
 
-This article summarizes prerequisites and support requirements for assessing Hyper-V VMs in preparation for migration to Azure. If you want to migrate Hyper-V VMs to Azure, review the [migration support matrix](migrate-support-matrix-hyper-v-migration.md).
+This article summarizes prerequisites and support requirements when you assess Hyper-V VMs for migration to Azure, using the [Azure Migrate:Server Assessment](migrate-services-overview.md#azure-migrate-server-assessment-tool) tool. If you want to migrate Hyper-V VMs to Azure, review the [migration support matrix](migrate-support-matrix-hyper-v-migration.md).
 
-You assess Hyper-V VMs with the [Azure Migrate:Server Assessment](migrate-services-overview.md#azure-migrate-server-assessment-tool) tool. You create an Azure Migrate project, and then add the tool to the project. After the tool is added, you deploy the [Azure Migrate appliance](migrate-appliance.md). The appliance continuously discovers on-premises machines, and sends machine metadata and performance data to Azure. After machine discovery, you gather discovered machines into groups, and run an assessment for a group.
+To set up Hyper-V VM assessment, you create an Azure Migrate project, and add the Server Assessment tool to the project. After the tool is added, you deploy the [Azure Migrate appliance](migrate-appliance.md). The appliance continuously discovers on-premises machines, and sends machine metadata and performance data to Azure. After discovery is complete, you gather discovered machines into groups, and run an assessment for a group.
 
 
 ## Limitations
@@ -39,13 +39,13 @@ You assess Hyper-V VMs with the [Azure Migrate:Server Assessment](migrate-servic
 
 | **Support**                  | **Details**               
 | :----------------------------- | :------------------- |
-| **Operating system** | All [Windows](https://support.microsoft.com/help/2721672/microsoft-server-software-support-for-microsoft-azure-virtual-machines) and [Linux](https://docs.microsoft.com/azure/virtual-machines/linux/endorsed-distros) operating systems supported by Azure. |
+| **Operating system** | All [Windows](https://support.microsoft.com/help/2721672/microsoft-server-software-support-for-microsoft-azure-virtual-machines) and [Linux](https://docs.microsoft.com/azure/virtual-machines/linux/endorsed-distros) operating systems. |
 | **Integration Services**       | [Hyper-V Integration Services](https://docs.microsoft.com/virtualization/hyper-v-on-windows/reference/integration-services) must be running on VMs that you assess, in order to capture operating system information. |
 
 
 ## Azure Migrate appliance requirements
 
-Azure Migrate uses the [Azure Migrate appliance](migrate-appliance.md) for discovery and assessment. You can deploy the appliance using a compressed Hyper-V VHd that you download from the portal, or using an PowerShell script.
+Azure Migrate uses the [Azure Migrate appliance](migrate-appliance.md) for discovery and assessment. You can deploy the appliance using a compressed Hyper-V VHD that you download from the portal, or using a [PowerShell script](deploy-appliance-script.md).
 
 - Learn about [appliance requirements](migrate-appliance.md#appliance---hyper-v) for Hyper-V.
 - Learn about [URLs](migrate-appliance.md#url-access) the appliance needs to access.
@@ -59,29 +59,13 @@ The following table summarizes port requirements for assessment.
 **Appliance** | Inbound connections on TCP port 3389 to allow remote desktop connections to the appliance.<br/><br/> Inbound connections on port 44368 to remotely access the appliance management app using the URL: ``` https://<appliance-ip-or-name>:44368 ```<br/><br/> Outbound connections on ports 443 (HTTPS), to send discovery and performance metadata to Azure Migrate.
 **Hyper-V host/cluster** | Inbound connections on WinRM ports 5985 (HTTP) and 5986 (HTTPS), to pull metadata and performance data for Hyper-V VMs using a Common Information Model (CIM) session.
 
-## Agentless dependency analysis requirements
-
-[Dependency analysis](concepts-dependency-visualization.md) helps you to identify dependencies between on-premises machines that you want to assess and migrate to Azure. The table summarizes the requirements for setting up agentless dependency analysis. 
-
-**Requirement** | **Details** 
---- | --- 
-**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.<br/><br/> [Learn how](create-manage-projects.md) to create a project for the first time.<br/> [Learn how](how-to-assess.md) to add an assessment tool to an existing project.<br/> [Learn how](how-to-set-up-appliance-vmware.md) to set up the Azure Migrate appliance for assessment of VMware VMs.
-**VM support** | Currently supported for VMware VMs only.
-**Windows VMs** | Windows Server 2016<br/> Windows Server 2012 R2<br/> Windows Server 2012<br/> Windows Server 2008 R2 (64-bit).
-**Windows account** |  For dependency analysis, the Azure Migrate appliance needs a local or a domain Administrator account to access Windows VMs.
-**Linux VMs** | Red Hat Enterprise Linux 7, 6, 5<br/> Ubuntu Linux 14.04, 16.04<br/> Debian 7, 8<br/> Oracle Linux 6, 7<br/> CentOS 5, 6, 7.
-**Linux account** | For dependency analysis, on Linux machines the Azure Migrate appliance needs a user account with Root privilege.<br/><br/> Alternately, the user account needs these permissions on /bin/netstat and /bin/ls files: CAP_DAC_READ_SEARCH and CAP_SYS_PTRACE.
-**Required agents** | No agent required on machines you want to analyze.
-**VMware tools** | VMware Tools (later than 10.2) must be installed and running on each VM you want to analyze.
-**vCenter Server** | Dependency visualization needs a vCenter Server account with read-only access, and privileges enabled for Virtual Machines > Guest Operations.**ESXi hosts**: On ESXi hosts running VMs you want to analyze, the Azure Migrate appliance must be able to connect to TCP port 443.
-
 ## Agent-based dependency analysis requirements
 
-[Dependency analysis](concepts-dependency-visualization.md) helps you to identify dependencies between on-premises machines that you want to assess and migrate to Azure. The table summarizes the requirements for setting up agent-based dependency analysis. 
+[Dependency analysis](concepts-dependency-visualization.md) helps you to identify dependencies between on-premises machines that you want to assess and migrate to Azure. The table summarizes the requirements for setting up agent-based dependency analysis. Hyper-V currently only supports agent-based dependency visualization. 
 
 **Requirement** | **Details** 
 --- | --- 
-**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<br/><br/> [Learn how](create-manage-projects.md) to create a project for the first time.<br/> [Learn how](how-to-assess.md) to add an assessment tool to an existing project.<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.
+**Before deployment** | You should have an Azure Migrate project in place, with the 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<br/><br/> [Learn how](create-manage-projects.md) to create a project for the first time.<br/> [Learn how](how-to-assess.md) to add an assessment tool to an existing project.<br/> Learn how to set up the Azure Migrate appliance for assessment of [Hyper-V VMs](how-to-set-up-appliance-hyper-v.md).
 **Azure Government** | Dependency visualization isn't available in Azure Government.
 **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.
 **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/> 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.<br/><br/> 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).