removed blockers

Ankita Dutta · Ankita Dutta · commit 41d629d28350 · 2023-08-23T16:53:27.000+05:30
diff --git a/articles/site-recovery/deploy-vmware-azure-replication-appliance-modernized.md b/articles/site-recovery/deploy-vmware-azure-replication-appliance-modernized.md
@@ -3,13 +3,24 @@ title: Deploy Azure Site Recovery replication appliance - Modernized
 description: This article describes how to replicate appliance for VMware disaster recovery to Azure with Azure Site Recovery - Modernized
 ms.service: site-recovery
 ms.topic: article
-ms.date: 08/01/2023
+ms.date: 08/23/2023
 ms.author: ankitadutta
 author: ankitaduttaMSFT
 ---
 
 # Deploy Azure Site Recovery replication appliance - Modernized
 
+>[!NOTE]
+> The information in this article applies to Azure Site Recovery - Modernized. For information about configuration server requirements in Classic releases, [see this article](vmware-azure-configuration-server-requirements.md).
+
+>[!NOTE]
+> Ensure you create a new and exclusive Recovery Services vault for setting up the ASR replication appliance. Don't use an existing vault.
+
+You deploy an on-premises replication appliance when you use [Azure Site Recovery](site-recovery-overview.md) for disaster recovery of VMware VMs or physical servers to Azure.
+
+- The replication appliance coordinates communications between on-premises VMware and Azure. It also manages data replication.
+- [Learn more](vmware-azure-architecture-modernized.md) about the Azure Site Recovery replication appliance components and processes.
+
 ## Prepare Azure account
 
 To create and register the Azure Site Recovery replication appliance, you need an Azure account with:
@@ -85,7 +96,7 @@ The OVF template spins up a machine with the required specifications.
 
 ### Set up the appliance through PowerShell
 
-If there is any organizational restrictions, you can manually set up the Site Recovery replication appliance through PowerShell. Follow these steps:
+If there are any organizational restrictions, you can manually set up the Site Recovery replication appliance through PowerShell. Follow these steps:
 
 1. Download the installers from [here](https://aka.ms/V2ARcmApplianceCreationPowershellZip) and place this folder on the Azure Site Recovery replication appliance.
 2. After successfully copying the zip folder, unzip and extract the components of the folder.
@@ -136,9 +147,9 @@ If there is any organizational restrictions, you can manually set up the Site Re
 
   - **Azure Site Recovery replication appliance key**: Copy the key from the portal by navigating to **Recovery Services vault** > **Getting started** > **Site Recovery** > **VMware to Azure: Prepare Infrastructure**.
 
-  - After pasting the key, select **Login.** You'll be redirected to a new authentication tab.
+  - After pasting the key, select **Login.** You're redirected to a new authentication tab.
 
-      By default, an authentication code will be generated as highlighted below, in the **Appliance configuration manager** page. Use this code in the authentication tab.
+      By default, an authentication code is generated as highlighted below, in the **Appliance configuration manager** page. Use this code in the authentication tab.
 
   - Enter your Microsoft Azure credentials to complete registration.
 
@@ -158,7 +169,7 @@ If there is any organizational restrictions, you can manually set up the Site Re
 
     :::image type="Configuration of vCenter" source="./media/deploy-vmware-azure-replication-appliance-modernized/vcenter-information.png" alt-text="Screenshot showing configuration of vCenter.":::
 
-7. Select **Add vCenter Server** to add vCenter information. Enter the server name or IP address of the vCenter and port information. Post that, provide username, password, and friendly name. This is used to fetch details of [virtual machine managed through the vCenter](vmware-azure-tutorial-prepare-on-premises.md#prepare-an-account-for-automatic-discovery). The user account details will be encrypted and stored locally in the machine.
+7. Select **Add vCenter Server** to add vCenter information. Enter the server name or IP address of the vCenter and port information. Post that, provide username, password, and friendly name. This is used to fetch details of [virtual machine managed through the vCenter](vmware-azure-tutorial-prepare-on-premises.md#prepare-an-account-for-automatic-discovery). The user account details are encrypted and stored locally in the machine.
 
     >[!NOTE]
     >If  you're trying to add the same vCenter Server to multiple appliances, then ensure that the same friendly name is used in all the appliances.
diff --git a/articles/site-recovery/hyper-v-azure-support-matrix.md b/articles/site-recovery/hyper-v-azure-support-matrix.md
@@ -30,8 +30,8 @@ Hyper-V without Virtual Machine Manager | You can perform disaster recovery to A
 
 **Server** | **Requirements** | **Details**
 --- | --- | ---
-Hyper-V (running without Virtual Machine Manager) | Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2 with latest updates <br/><br/> **Note:** Server core installation of these operating systems are also supported. | If you have already configured Windows Server 2012 R2 with/or SCVMM 2012 R2 with Azure Site Recovery and plan to upgrade the OS, please follow the guidance [documentation.](upgrade-2012R2-to-2016.md)
-Hyper-V (running with Virtual Machine Manager) | Virtual Machine Manager 2022  (Server core not supported), Virtual Machine Manager 2019, Virtual Machine Manager 2016, Virtual Machine Manager 2012 R2 <br/><br/> **Note:** Server core installation of these operating systems are also supported.  | If Virtual Machine Manager is used, Windows Server 2019 hosts should be managed in Virtual Machine Manager 2019. Similarly, Windows Server 2016 hosts should be managed in Virtual Machine Manager 2016.
+Hyper-V (running without Virtual Machine Manager) | Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2 with latest updates <br/><br/> **Note:** Server core installations of these operating systems are also supported. | If you have already configured Windows Server 2012 R2 with/or SCVMM 2012 R2 with Azure Site Recovery and plan to upgrade the OS, please follow the guidance [documentation.](upgrade-2012R2-to-2016.md)
+Hyper-V (running with Virtual Machine Manager) | Virtual Machine Manager 2022  (Server core not supported), Virtual Machine Manager 2019, Virtual Machine Manager 2016, Virtual Machine Manager 2012 R2 <br/><br/> **Note:** Server core installations of these operating systems are also supported.  | If Virtual Machine Manager is used, Windows Server 2019 hosts should be managed in Virtual Machine Manager 2019. Similarly, Windows Server 2016 hosts should be managed in Virtual Machine Manager 2016.
 
 > [!NOTE]
 > Ensure that .NET Framework 4.6.2 or higher is present on the on-premises server.
diff --git a/articles/site-recovery/move-from-classic-to-modernized-vmware-disaster-recovery.md b/articles/site-recovery/move-from-classic-to-modernized-vmware-disaster-recovery.md
@@ -57,7 +57,7 @@ Ensure the following for the replicated items you're planning to move:
 - The replicated item isn't replicating the data from Azure to on-premises.  
 - The initial replication isn't under progress and has already been completed.   
 - The replicated item isn't in the ‘resynchronization’ state.  
-- The configuration server’s version is 9.50 or later and its health is in a non critical state.  
+- The configuration server’s version is 9.50 or later and its health is in a noncritical state.  
 - The configuration server has a healthy heartbeat.  
 - The mobility service agent’s version, installed on the source machine, is 9.50 or later.  
 - The Recovery Services vaults with MSI enabled are supported.  
@@ -103,7 +103,7 @@ The same formula is used to calculate time for migration and is shown on the por
 
 When migrating machines from classic to modernized architecture, you'll need to make sure that the required infrastructure has already been registered in the modernized Recovery Services vault. Refer to the replication appliance’s [sizing and capacity details](./replication-appliance-support-matrix.md#sizing-and-capacity) to help define the required infrastructure.  
 
-As a rule, you should set up the same number of replication appliances, as the number of process servers in your classic Recovery Services vault. In the classic vault, if there was one configuration server and four process servers, then you should set up four replication appliances in the modernized Recovery Services vault.  
+As a rule, you should setup the same number of replication appliances, as the number of process servers in your classic Recovery Services vault. In the classic vault, if there was one configuration server and four process servers, then you should setup four replication appliances in the modernized Recovery Services vault.  
 
 ## Pricing 
 
diff --git a/articles/site-recovery/replication-appliance-support-matrix.md b/articles/site-recovery/replication-appliance-support-matrix.md
@@ -103,9 +103,9 @@ C:\Program Files\Microsoft Azure Recovery Services Agent <br>
 C:\Program Files\Microsoft Azure Server Discovery Service <br>
 C:\Program Files\Microsoft Azure Site Recovery Process Server <br>
 C:\Program Files\Microsoft Azure Site Recovery Provider <br>
-C:\Program Files\Microsoft Azure to On-Premises Reprotect agent <br>
+C:\Program Files\Microsoft Azure to on-Premises Reprotect agent <br>
 C:\Program Files\Microsoft Azure VMware Discovery Service <br>
-C:\Program Files\Microsoft On-Premise to Azure Replication agent <br>
+C:\Program Files\Microsoft on-Premise to Azure Replication agent <br>
 E:\ <br>
 
 #### If Antivirus software is active on source machine
diff --git a/articles/site-recovery/site-recovery-whats-new.md b/articles/site-recovery/site-recovery-whats-new.md
@@ -54,7 +54,7 @@ For Site Recovery components, we support N-4 versions, where N is the latest rel
 **Providers and agents** | Updates to Site Recovery agents and providers as detailed in the rollup KB article.
 **Issue fixes/improvements** | Many fixes and improvement as detailed in the rollup KB article.
 **Azure VM disaster recovery** | Added support for Oracle Linux 8.7 with UEK7 kernel, RHEL 9 and Cent OS 9 Linux distros.
-**VMware VM/physical disaster recovery to Azure** | Added support for Oracle Linux 8.7 with UEK7 kernel, RHEL 9, Cent OS 9 and Oracle Linux 9 Linux distros. <br> <br/> Added support for Windows Server 2019 as the ASR replication appliance. <br> <br/> Added support for Microsoft Edge to be the default browser in Appliance Configuration Manager. <br> <br/> Added support to select an Availability set or a Proximity Placement group, after enabling replication using modernized VMware/Physical machine replication scenario.
+**VMware VM/physical disaster recovery to Azure** | Added support for Oracle Linux 8.7 with UEK7 kernel, RHEL 9, Cent OS 9 and Oracle Linux 9 Linux distros. <br> <br/> Added support for Windows Server 2019 as the Azure Site Recovery replication appliance. <br> <br/> Added support for Microsoft Edge to be the default browser in Appliance Configuration Manager. <br> <br/> Added support to select an Availability set or a Proximity Placement group, after enabling replication using modernized VMware/Physical machine replication scenario.
 
 
 ## Updates (February 2023)
