Merge pull request #95495 from rayne-wiselman/raynenovember11

fixing issues

Author: PRMerger19

articles/migrate/how-to-set-up-appliance-physical.md

@@ -4,7 +4,7 @@ description: Describes how to set up an appliance for assessment of physical ser
 author: rayne-wiselman
 ms.service: azure-migrate
 ms.topic: article
-ms.date: 10/21/2019
+ms.date: 11/11/2019
 ms.author: raynew
 ---
 
@@ -13,6 +13,9 @@ ms.author: raynew
 
 This article describes how to set up the Azure Migrate appliance if you're assessing physical servers with the Azure Migrate: Server Assessment tool.
 
+> [!NOTE]
+> If features are mentioned here that you don't yet see in the Azure Migrate portal, hang on. They will appear over the next week or so.
+
 The Azure Migrate appliance is a lightweight appliance, used by Azure Migrate Server Assessment to do the following:
 
 - Discover on-premises servers.

articles/migrate/tutorial-migrate-physical-virtual-machines.md

@@ -118,7 +118,7 @@ Make sure machines comply with requirements for migration to Azure.
 > [!NOTE]
 > Agent-based migration with Azure Migrate Server Migration is based on features of the Azure Site Recovery service. Some requirements might link to Site Recovery documentation.
 
-1. [Verify](migrate-support-matrix-vmware.md#agent-based-migration-vmware-server-requirements) VMware server requirements.
+1. [Verify](migrate-support-matrix-vmware.md#agent-based-migration-vmware-server-requirements) server requirements.
 2. [Verify](migrate-support-matrix-vmware.md#agent-based-migration-vmware-vm-requirements) VM support requirements for migration.
 3. Verify VM settings. On-premises VMs you replicate to Azure must comply with [Azure VM requirements](migrate-support-matrix-vmware.md#azure-vm-requirements).
 
@@ -260,7 +260,7 @@ Now, select machines for migration.
 
     ![Replicate VMs](./media/tutorial-migrate-physical-virtual-machines/select-replicate.png)
 
-2. In **Replicate**, > **Source settings** > **Are your machines virtualized?**, select **Yes, with VMware vSphere**.
+2. In **Replicate**, > **Source settings** > **Are your machines virtualized?**, select **Not virtualized/Other**.
 3. In **On-premises appliance**, select the name of the Azure Migrate appliance that you set up.
 4. In **vCenter server**, specify the name of the vCenter server managing the VMs, or the vSphere server on which the VMs are hosted.
 5. In **Process Server**, select the name of the replication appliance.

articles/site-recovery/azure-to-azure-about-networking.md

@@ -57,7 +57,7 @@ If you are using an IP-based firewall proxy, or NSG rules to control outbound co
     - Allow these addresses so that data can be written to the cache storage account, from the VM.
 - Create a [Azure Active Directory (AAD) service tag](../virtual-network/security-overview.md#service-tags) based NSG rule for allowing access to all IP addresses corresponding to AAD
     - If new addresses are added to the Azure Active Directory (AAD) in the future, you need to create new NSG rules.
-- Site Recovery service endpoint IP addresses - available in an [XML file](https://aka.ms/site-recovery-public-ips) and depend on your target location. It is recommended to allow access to the tag **"AzureSiteRecovery"** for Site Recovery service access.
+- Site Recovery service endpoint IP addresses - available in an [XML file](https://aka.ms/site-recovery-public-ips) and depend on your target location. 
 - We recommend that you create the required NSG rules on a test NSG, and verify that there are no problems before you create the rules on a production NSG.
 
 
@@ -122,9 +122,6 @@ This example shows how to configure NSG rules for a VM to replicate.
 - If you're using NSG rules to control outbound connectivity, use "Allow HTTPS outbound" rules to port:443 for all the required IP address ranges.
 - The example presumes that the VM source location is "East US" and the target location is "Central US".
 
-> [!NOTE]
-> It is recommended to use **AzureSiteRecovery tag** instead of IP addresses to allow access to **Site Recovery service**.
-
 ### NSG rules - East US
 
 1. Create an outbound HTTPS (443) security rule for "Storage.EastUS" on the NSG as shown in the screenshot below.