removing blockers

Author: Ankita Dutta

articles/site-recovery/migrate-tutorial-windows-server-2008.md

@@ -3,8 +3,8 @@ title: Migrate Windows Server 2008 servers to Azure with Azure Migrate/Site Reco
 description: This article describes how to migrate on-premises Windows Server 2008 machines to Azure, and recommends Azure Migrate.
 ms.service: site-recovery
 ms.topic: tutorial
-ms.date: 07/27/2020
-ms.custom: MVC
+ms.date: 12/30/2022
+ms.custom: MVC, engagement-fy23
 ms.author: ankitadutta
 author: ankitaduttaMSFT
 ---
@@ -110,7 +110,7 @@ The new vault is added to the **Dashboard** under **All resources**, and on the
 ### Prepare your on-premises environment for migration
 
 - To migrate Windows Server 2008 virtual machines running on VMware, [setup the on-premises Configuration Server on VMware](vmware-azure-tutorial.md#set-up-the-source-environment).
-- If the Configuration Server cannot be setup as a VMware virtual machine, [setup the Configuration Server on an on-premises physical server or virtual machine](physical-azure-disaster-recovery.md#set-up-the-source-environment).
+- If the Configuration Server cannot be setup as a VMware virtual machine, [setup the Configuration Server on an on-premises physical server or virtual machine](physical-azure-disaster-recovery.md#source-settings).
 
 ### Set up the target environment
 

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

@@ -165,7 +165,7 @@ On the **Target settings** tab, do the following:
     Site Recovery checks that you have one or more compatible Azure storage accounts and networks.
 1. Select **Next**
 
-    :::image type="content" source="./media/physical-azure-disaster-recovery/target-setting.png" alt-text="Screenshot of the target setting page.":::
+    :::image type="content" source="./media/physical-azure-disaster-recovery/target-settings.png" alt-text="Screenshot of the target setting page.":::
 
 
 ## Replication policy
@@ -188,7 +188,7 @@ Under **Replication policy** tab, do the following:
         :::image type="content" source="./media/physical-azure-disaster-recovery/create-policy.png" alt-text="Screenshot of replication policy page.":::
 
 By default, a matching policy is automatically created for failback. For example, if the replication policy is **rep-policy** then a failback policy **rep-policy-failback** is created. This policy isn't used until you initiate a failback from Azure.
-![Screenshot of the options for creating a replication policy.](./media/physical-azure-disaster-recovery/replication-policy.png)
+
 
 ## Enable replication
 
@@ -200,7 +200,7 @@ By default, a matching policy is automatically created for failback. For example
     1. In **Machine type**, select **Physical machines**.
     1. In **Process server**, retain the default selection. Optionally, you can use the **Add Process Server** to add a new server for this step.
     1. Select **Next**.
-    :::image type="content" source="./media/physical-azure-disaster-recovery/enable-replication-source.png" alt-text="Screenshot of source setting page.":::
+    :::image type="content" source="./media/physical-azure-disaster-recovery/enable-replication-source.png" alt-text="Screenshot of enable replication source setting page.":::
 
 1. Under **Target environment** tab, do the following:
     1. In **Target subscription**, specify the subscription name.
@@ -220,9 +220,9 @@ By default, a matching policy is automatically created for failback. For example
        :::image type="content" source="./media/physical-azure-disaster-recovery/add-physical-machines.png" alt-text="Screenshot of add machine page.":::
 
 1. Under **Replication settings** tab, select and verify the the user account details.
-    :::image type="content" source="./media/physical-azure-disaster-recovery/enable-replication-settings.png" alt-text="Screenshot of replication setting page.":::
+    :::image type="content" source="./media/physical-azure-disaster-recovery/enable-replication-settings.png" alt-text="Screenshot of enable replication setting page.":::
 1. Under **Replication policy** tab, verify that the correct replication policy is selected.
-    :::image type="content" source="./media/physical-azure-disaster-recovery/enable-replication-policy.png" alt-text="Screenshot of replication policy page.":::
+    :::image type="content" source="./media/physical-azure-disaster-recovery/enable-replication-policy.png" alt-text="Screenshot of enable replication policy page.":::
 1. Under **Review** tab, review your selections and select **Enable Replication**. You can track progress of the **Enable Protection** job in **Settings** > **Jobs** > **Site Recovery Jobs**. After the **Finalize Protection** job runs the machine is ready for failover.
 
 

articles/site-recovery/region-move-cross-geos.md

@@ -4,9 +4,9 @@ description: Use Azure Site Recovery to move Azure VMs between Azure government
 author: ankitaduttaMSFT
 ms.service: site-recovery
 ms.topic: tutorial
-ms.date: 04/16/2019
+ms.date: 12/30/2022
 ms.author: ankitadutta
-ms.custom: MVC
+ms.custom: MVC, engagement-fy23
 ---
 # Move Azure VMs between Azure Government and Public regions 
 
@@ -118,12 +118,12 @@ The below steps will guide you how to use Azure Site Recovery to copy data to th
 Set up the configuration server, register it in the vault, and discover VMs.
 
 1. Click **Site Recovery** > **Prepare Infrastructure** > **Source**.
-2. If you don’t have a configuration server, click **+Configuration server**.
+2. If you don't have a configuration server ready, you can use the **Add Configuration Server** option.
 3. In **Add Server**, check that **Configuration Server** appears in **Server type**.
 4. Download the Site Recovery Unified Setup installation file.
 5. Download the vault registration key. You need this when you run Unified Setup. The key is valid for five days after you generate it.
 
-   ![Set up source](./media/physical-azure-disaster-recovery/source-environment.png)
+   :::image type="content" source="./media/physical-azure-disaster-recovery/add-server.png" alt-text="Screenshot of add server page.":::
 
 
 ### Register the configuration server in the vault
@@ -155,10 +155,12 @@ After registration finishes, the configuration server is displayed on the **Sett
 Select and verify target resources.
 
 1. Click **Prepare infrastructure** > **Target**, and select the Azure subscription you want to use.
-2. Specify the target deployment model.
-3. Site Recovery checks that you have one or more compatible Azure storage accounts and networks.
+2. On the **Target settings** tab, do the following:
 
-   ![Target](./media/physical-azure-disaster-recovery/network-storage.png)
+    1. Under **Subscription**, select the Azure subscription you want to use.
+    2. Under **Post-failover deployment model**, specify the target deployment model.
+3. Site Recovery checks that you have one or more compatible Azure storage accounts and networks.
+    :::image type="content" source="./media/physical-azure-disaster-recovery/target-settings.png" alt-text="Screenshot of the target setting page.":::
 
 
 ### Create a replication policy
@@ -168,8 +170,8 @@ Select and verify target resources.
 3. In **RPO threshold**, 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.
 4. In **Recovery point retention**, specify how long (in hours) the retention window is for each recovery point. Replicated VMs can be recovered to any point in a window. Up to 24 hours retention is supported for machines replicated to premium storage, and 72 hours for standard storage.
 5. In **App-consistent snapshot frequency**, specify how often (in minutes) recovery points containing application-consistent snapshots will be created. Click **OK** to create the policy.
+    :::image type="content" source="./media/physical-azure-disaster-recovery/create-policy.png" alt-text="Screenshot of replication policy page.":::
 
-    ![Replication policy](./media/physical-azure-disaster-recovery/replication-policy.png)
 
 
 The policy is automatically associated with the configuration server. By default, a matching policy is automatically created for failback. For example, if the replication policy is **rep-policy** then a failback policy **rep-policy-failback** is created. This policy isn't used until you initiate a failback from Azure.

articles/site-recovery/vmware-physical-large-deployment.md

@@ -3,9 +3,10 @@ title: Scale VMware/physical disaster recovery with Azure Site Recovery
 description: Learn how to set up disaster recovery to Azure for large numbers of on-premises VMware VMs or physical servers with Azure Site Recovery.
 ms.service: site-recovery
 ms.topic: conceptual
-ms.date: 11/14/2019
+ms.date: 12/30/2022
 ms.author: ankitadutta
 author: ankitaduttaMSFT
+ms.custom: engagement-fy23
 
 ---
 # Set up disaster recovery at scale for VMware VMs/physical servers
@@ -172,7 +173,7 @@ After planning capacity and deploying the required components and infrastructure
 
 2. If disk churn for a machine is high, or exceeds limits in  Deployment thePlanner, you can move non-critical files you don't need to replicate (such as log dumps or temp files) off the machine. For VMware VMs, you can move these files to a separate disk, and then [exclude that disk](vmware-azure-exclude-disk.md) from replication.
 3. Before you enable replication, check that machines meet [replication requirements](vmware-physical-azure-support-matrix.md#replicated-machines).
-4. Configure a replication policy for [VMware VMs](vmware-azure-set-up-replication.md#create-a-policy) or [physical servers](physical-azure-disaster-recovery.md#create-a-replication-policy).
+4. Configure a replication policy for [VMware VMs](vmware-azure-set-up-replication.md#create-a-policy) or [physical servers](physical-azure-disaster-recovery.md#replication-policy).
 5. Enable replication for [VMware VMs](vmware-azure-enable-replication.md) or [physical servers](physical-azure-disaster-recovery.md#enable-replication). This kicks off the initial replication for the selected machines.
 
 ## Monitor your deployment