PM comments incorporated

Author: Ankita Dutta

articles/site-recovery/hybrid-how-to-enable-replication-private-endpoints.md

@@ -38,7 +38,7 @@ then create private endpoints in the bypass network. You can choose any form of
 **Before you start, note the following:**
 
 - Private links are supported in Site Recovery 9.35 and later.
-- You can create private endpoints only for new Recovery Services vaults that don't have any items registered to them. So you must create private endpoints before any items are added to the vault. See [Azure Private Link pricing](https://azure.microsoft.com/pricing/details/private-link/) for pricing information.
+- You can create private endpoints only for new Recovery Services vaults that don't have any items registered to them. Therefore, you must create private endpoints before any items are added to the vault. See [Azure Private Link pricing](https://azure.microsoft.com/pricing/details/private-link/) for pricing information.
 - When you create a private endpoint for a vault, the vault is locked down. It can be accessed only from networks that have private endpoints.
 - Azure Active Directory doesn't currently support private endpoints. So you need to allow outbound access from the secured Azure virtual network to IPs and fully qualified domain names that are required for Azure Active Directory to work in a region. As applicable, you can also use network security group tag "Azure Active Directory" and Azure Firewall tags to allow access to Azure Active Directory.
 - Five IP addresses are required in the bypass network where you create your private endpoint. When you create a private endpoint for the vault, Site Recovery creates five private links for access to its microservices.
@@ -49,7 +49,7 @@ then create private endpoints in the bypass network. You can choose any form of
 
 ### URLs to be allowed
 
-When using the private link with modernized experience for VMware VMs, public access is needed for a few resources. Below are all URLs to be included in the allowlist. If proxy-based configuration is used then make sure that the proxy resolves any CNAME records received while looking up the URLs.
+When using the private link with modernized experience for VMware VMs, public access is needed for a few resources. Below are all URLs to be included in the allowlist. If proxy-based configuration is used, make sure that the proxy resolves any CNAME records received while looking up the URLs.
 
   |  **URL**                  |     **Details**                            |
   | ------------------------- | -------------------------------------------|
@@ -100,7 +100,7 @@ To protect the machines in the on-premises source network, you'll need one priva
 
 1. In the [Azure portal](https://portal.azure.com), select **Create a resource**.
 1. Search the Azure Marketplace for *Private link*.
-1. Select **Private Link** from the search results, and in the Backup and Site Recovery page, click **Create**.
+1. Select **Private Link** from the search results, and in the Backup and Site Recovery page, select **Create**.
 
    :::image type="content" source="./media/hybrid-how-to-enable-replication-private-endpoints/marketplace.png" alt-text="Screenshot that shows searching the Azure portal for Private Link Center.":::
 
@@ -267,10 +267,9 @@ Create one private DNS zone to allow the Site Recovery provider (for Hyper-V mac
 
    1. Continue to the **Review \+ create** tab to review and create the DNS zone.
 
-1. Link the private DNS zone to your virtual network.
-
-   You now need to link the private DNS zone that you created to the bypass.
+1. To link the private DNS zone to your virtual network, follow these steps: 
 
+   
    1. Go to the private DNS zone that you created in the previous step and then go to **Virtual
       network links** in the left pane. Select **Add**.
 
@@ -304,5 +303,5 @@ Create one private DNS zone to allow the Site Recovery provider (for Hyper-V mac
 
 Now that you've enabled private endpoints for your virtual machine replication, see these other articles for additional and related information:
 
-- [Deploy an on-premises configuration server](./vmware-azure-deploy-configuration-server.md)
-- [Set up disaster recovery of on-premises Hyper-V VMs to Azure](./hyper-v-azure-tutorial.md)
+- [Deploy an on-premises configuration server](./vmware-azure-deploy-configuration-server.md).
+- [Set up disaster recovery of on-premises Hyper-V VMs to Azure](./hyper-v-azure-tutorial.md).

articles/site-recovery/physical-azure-disaster-recovery.md

@@ -3,7 +3,7 @@ title: Set up disaster recovery of physical on-premises servers with Azure Site
 description: Learn how to set up disaster recovery to Azure for on-premises Windows and Linux servers, with the Azure Site Recovery service.
 ms.service: site-recovery
 ms.topic: article
-ms.date: 12/29/2022
+ms.date: 01/16/2023
 ms.author: ankitadutta
 author: ankitaduttaMSFT
 ms.custom: engagement-fy23
@@ -88,16 +88,6 @@ The Mobility service must be installed on each server you want to replicate. Sit
 
 [!INCLUDE [site-recovery-create-vault](../../includes/site-recovery-create-vault.md)]
 
-## Select a protection goal
-
-Select what to replicate, and to replicate it to.
-
-1. In the [Azure portal](https://portal.azure.com), search **Recovery Services vaults** and select the vault. 
-2. In the Resource Menu, click **Site Recovery** > **Prepare Infrastructure** > **Protection goal**.
-3. In **Protection goal**, select **To Azure** > **Not virtualized/Other**.
-
-To set up the source environment, set up the configuration server, register it in the vault, and discover VMs.
-
 ## Prepare Infrastructure
 
 It is important to prepare the infrastructure before you set up disaster recovery of physical VMware machines to Azure.
@@ -163,6 +153,8 @@ On the **Target settings** tab, do the following:
 1. Under **Subscription**, select the Azure subscription you want to use.
 2. Under **Post-failover deployment model**, specify the target deployment model.
     Site Recovery checks that you have one or more compatible Azure storage accounts and networks.
+    > ![!NOTE]
+    > Only Resource Manager deployment model should be selected, as Classic deployment model will be deprecated by 01, March, 2023.
 1. Select **Next**
 
     :::image type="content" source="./media/physical-azure-disaster-recovery/target-settings.png" alt-text="Screenshot of the target setting page.":::
@@ -180,7 +172,7 @@ Under **Replication policy** tab, do the following:
 3.	In the **Create and associate policy** page, do the following:
     1. **Name** - specify a policy name.
     1. **Source type** - select **VMware / Physical machines**.
-    1. **Target type** - select the subscription and the resource group in which you want to create the Azure VMs after failover. Choose the deployment model that you want to use in Azure (classic or resource management).
+    1. **Target type** - select the subscription and the resource group in which you want to create the Azure VMs after failover. 
     1. **RPO threshold in mins** - specify the recovery point objective (RPO) limit. This value specifies how often data recovery points are created. An alert is generated if continuous replication exceeds this limit..
     1. **Retention period (in days)** - specify how long (in days) the retention window is for each recovery point. Replicated VMs can be recovered to any point in a window. Up to 15 days retention is supported.
     1. In **App-consistent snapshot frequency**, specify how often (in hours) recovery points containing application-consistent snapshots will be created. 

includes/media/site-recovery-create-vault/new-vault-settings.png

@@ -1,17 +1,21 @@
 ---
-author: rayne-wiselman
+author: ankitaduttaMSFT
 ms.service: site-recovery
 ms.topic: include
-ms.date: 10/26/2018
-ms.author: raynew
+ms.date: 01/16/2023
+ms.author: ankitadutta
 ---
 
-1. Sign in to the [Azure portal](https://portal.azure.com) > **Recovery Services**.
-2. Click **Create a resource** > **Monitoring + Management** > **Backup and Site Recovery**.
-3. In **Name**, specify a friendly name to identify the vault. If you have more than one subscription, select the appropriate one.
-4. [Create a resource group](../articles/azure-resource-manager/templates/deploy-portal.md), or select an existing one. Specify an Azure region. 
-5. To quickly access the vault from the dashboard, click **Pin to dashboard** > **Create**.
+1. Sign in to the [Azure portal](https://portal.azure.com).
+1. In the **Marketplace** search for **Backup and Site Recovery**
+1. In the **Create Recovery Services vault** page, do the following:
+    1. Under **Subscription**, select the appropriate subscription name.
+    1. [Create a resource group](../articles/azure-resource-manager/templates/deploy-portal.md), or select an existing one. 
+    1. Under **Vault name**, specify a friendly name to identify the vault. 
+    1. Under **Region**, specify an Azure region.
+    1. Select **Review + create** to finish. 
+1. To quickly access the vault from the dashboard, click **Pin to dashboard** > **Create**.
 
-   ![Screenshot of the Rescovery Services vault creation options.](./media/site-recovery-create-vault/new-vault-settings.png)
+   ![Screenshot of the Recovery Services vault creation options.](./media/site-recovery-create-vault/new-vault-settings.png)
 
    The new vault will appear on the **Dashboard** > **All resources**, and on the main **Recovery Services vaults** page.