Merge branch 'rayneapril15' of https://github.com/rayne-wiselman/azure-docs-pr into rayneapril15

rayne-wiselman · rayne-wiselman · commit 5a31cd8b4a51 · 2020-04-16T20:36:53.000+03:00
diff --git a/articles/migrate/concepts-dependency-visualization.md b/articles/migrate/concepts-dependency-visualization.md
@@ -25,7 +25,7 @@ There are two options for deploying dependency analysis
 - **Agentless**: With agentless analysis, 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.
 
 > [!NOTE]
-> Dependency analysis isn't available in Azure Government.
+> Agent-based dependency analysis isn't available in Azure Government. You can use agentless dependency analysis.
 
 ## Agentless analysis
 
diff --git a/articles/migrate/migrate-appliance.md b/articles/migrate/migrate-appliance.md
@@ -121,6 +121,7 @@ download.microsoft.com/download | Allow downloads from Microsoft download.
 *.discoverysrv.windowsazure.us <br/> *.migration.windowsazure.us | Connect to Azure Migrate service URLs.
 *.hypervrecoverymanager.windowsazure.us | **Used for VMware agentless migration**<br/><br/> Connect to Azure Migrate service URLs.
 *.blob.core.usgovcloudapi.net  |  **Used for VMware agentless migration**<br/><br/>Upload data to storage for migration.
+*.applicationinsights.us | Used by Gateway agent on the appliance to access the Application Insights endpoitn for diagnostic monitoring.
 
 
 
diff --git a/articles/migrate/migrate-support-matrix-hyper-v.md b/articles/migrate/migrate-support-matrix-hyper-v.md
@@ -74,7 +74,7 @@ The following table summarizes port requirements for assessment.
 **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.
 **Internet connectivity** | If machines aren't connected to the internet, you need to install the Log Analytics gateway on them.
-**Azure Government** | Dependency analysis isn't supported.
+**Azure Government** | Agent-based dependency analysis isn't supported.
 
 ## Next steps
 
diff --git a/articles/migrate/migrate-support-matrix-physical.md b/articles/migrate/migrate-support-matrix-physical.md
@@ -63,7 +63,7 @@ The following table summarizes port requirements for assessment.
 **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.
 **Internet connectivity** | If machines aren't connected to the internet, you need to install the Log Analytics gateway on them.
-**Azure Government** | Dependency analysis isn't supported.
+**Azure Government** | Agent-based dependency analysis isn't supported.
 
 ## Next steps
 
diff --git a/articles/migrate/migrate-support-matrix-vmware.md b/articles/migrate/migrate-support-matrix-vmware.md
@@ -37,7 +37,7 @@ In addition to discovering machines, Server Assessment can discover apps, role,
 **PowerShell** | VMs must have PowerShell version 2.0 or later installed.
 **Port access** | On ESXi hosts running VMs you want to discover, the Azure Migrate appliance must be able to connect to TCP port 443.
 **Limits** | For app-discovery, you can discover up to 10000 VMs on each Azure Migrate appliance.
-**Azure Government** | Application discovery isn't supported.
+
 
 
 ## VMware requirements
@@ -85,7 +85,7 @@ ESXi hosts (app discovery/agentless dependency analysis) | If you want to do [ap
 **vCenter Server credentials** | Dependency visualization needs a vCenter Server account with read-only access, and privileges enabled for Virtual Machines > Guest Operations. 
 **PowerShell** | VMs must have PowerShell version 2.0 or above installed.
 **Port access** | On ESXi hosts running VMs you want to analyze, the Azure Migrate appliance must be able to connect to TCP port 443.
-**Azure Government** | Dependency analysis isn't supported.
+
 
 ## Agent-based dependency analysis requirements
 
@@ -101,7 +101,7 @@ ESXi hosts (app discovery/agentless dependency analysis) | If you want to do [ap
 **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.
 **Internet connectivity** | If machines aren't connected to the internet, you need to install the Log Analytics gateway on them.
-**Azure Government** | Dependency analysis isn't supported.
+**Azure Government** | Agent-based dependency analysis isn't supported.
 
 
 ## Next steps
diff --git a/articles/migrate/tutorial-assess-vmware.md b/articles/migrate/tutorial-assess-vmware.md
@@ -62,7 +62,7 @@ Set up a new Azure Migrate project as follows:
 Azure Migrate:Server Assessment uses a lightweight Azure Migrate appliance. The appliance performs VM discovery and sends VM metadata and performance data to Azure Migrate. The appliance can be set up in a number of ways.
 
 - Set up on a VMware VM using a downloaded OVA template. This is the method used in this tutorial.
-- Set up on a VMware VM or physical machine with a PowerShell installer script. [This method](migrate-appliance-script.md) should be used if you can't set up a VM using an OVA template, or if you're in Azure Government.
+- Set up on a VMware VM or physical machine with a PowerShell installer script. [This method](deploy-appliance-script.md) should be used if you can't set up a VM using an OVA template, or if you're in Azure Government.
 
 After creating the appliance, you check that it can connect to Azure Migrate:Server Assessment, configure it for the first time, and register it with the Azure Migrate project.
 
diff --git a/articles/migrate/tutorial-migrate-physical-virtual-machines.md b/articles/migrate/tutorial-migrate-physical-virtual-machines.md
@@ -99,7 +99,7 @@ Azure Migrate:Server Migration uses a replication appliance to replicate machine
 
 Prepare for appliance deployment as follows:
 
-- You prepare a machine to host the replication appliance. [Review](migrate-replication-appliance.md#appliance-requirements.md) the machine requirements. The appliance shouldn't be installed on a source machine that you want to replicate.
+- You prepare a machine to host the replication appliance. [Review](migrate-replication-appliance.md#appliance-requirements) the machine requirements. The appliance shouldn't be installed on a source machine that you want to replicate.
 - The replication appliance uses MySQL. Review the [options](migrate-replication-appliance.md#mysql-installation) for installing MySQL on the appliance.
 - Review the Azure URLs required for the replication appliance to access [public](migrate-replication-appliance.md#url-access) and [government](migrate-replication-appliance.md#azure-government-url-access) clouds.
 - Review [port] (migrate-replication-appliance.md#port-access) access requirements for the replication appliance.
diff --git a/articles/migrate/tutorial-prepare-physical.md b/articles/migrate/tutorial-prepare-physical.md
@@ -150,7 +150,7 @@ Review the requirements for migration of physical servers.
 - [Review](migrate-support-matrix-physical-migration.md#physical-server-requirements) physical server requirements for migration.
 - Azure Migrate:Server Migration uses a replication server for physical server migration:
     - [Review](migrate-replication-appliance.md#appliance-requirements) the deployment requirements for the replication appliance, and the [options](migrate-replication-appliance.md#mysql-installation) for installing MySQL on the appliance.
-    - Review the [Azure URLs](migrate-appliance.md#azure-government-url-access) required for the replication appliance to access public and government clouds.
+    - Review the [Azure URLs](migrate-appliance.md#url-access) required for the replication appliance to access public and government clouds.
     - Review [port] (migrate-replication-appliance.md#port-access) access requirements for the replication appliance.
 
 
diff --git a/articles/migrate/whats-new.md b/articles/migrate/whats-new.md
@@ -19,7 +19,7 @@ Azure Migrate supports deployments in Azure Government.
 - For VMware migration, you can use agentless or agent-based migration. [Learn more](server-migrate-overview.md).
 - [Review](migrate-support-matrix.md#supported-geographies-azure-government) supported geographies and regions for Azure Government.
 - [Agent-based dependency analysis](concepts-dependency-visualization.md#agent-based-analysis) isn't supported in Azure Government.
-- Features in preview aren't supported in Azure Government, specifically [agentless dependency analysis](concepts-dependency-visualization.md#agentless-analysis), and [application discovery](how-to-discover-applications.md).
+- Features in preview are supported in Azure Government, specifically [agentless dependency analysis](concepts-dependency-visualization.md#agentless-analysis), and [application discovery](how-to-discover-applications.md).
 
 ## Update (March 2020)
 
