1912 EEE tasks

Ankita Dutta · Ankita Dutta · commit b8a6abf5521f · 2024-12-19T22:49:01.000+05:30
diff --git a/articles/site-recovery/failover-failback-overview-modernized.md b/articles/site-recovery/failover-failback-overview-modernized.md
@@ -2,7 +2,7 @@
 title: About failover and failback in Azure Site Recovery - Modernized
 description: Learn about failover and failback in Azure Site Recovery - Modernized.
 ms.topic: overview
-ms.date: 02/13/2024
+ms.date: 12/19/2024
 ms.author: ankitadutta
 ms.service: azure-site-recovery
 author: ankitaduttaMSFT
@@ -11,7 +11,7 @@ author: ankitaduttaMSFT
 
 This article provides an overview of failover and failback during disaster recovery of on-premises machines to Azure with [Azure Site Recovery](site-recovery-overview.md) - Modernized.
 
-For information about failover and failback in Azure Site Recovery Classic releases, [see this article](failover-failback-overview.md).
+For information about failover and failback in Azure Site Recovery Classic releases, [see this article](vmware-azure-architecture.md#failover-and-failback-process).
 
 ## Recovery stages
 
@@ -160,16 +160,9 @@ Once you have initiated the planned failover and it completes successfully, your
 
 ## Next steps
 
-> [!div class="nextstepaction"]
-> [Failover VMware VMs to Azure (modernized)](vmware-azure-tutorial-failover-failback-modernized.md#run-a-failover-to-azure)
-
-> [!div class="nextstepaction"]
-> [Planned failover (modernized)](vmware-azure-tutorial-failover-failback-modernized.md#planned-failover-from-azure-to-on-premises)
-
-> [!div class="nextstepaction"]
-> [Reprotect (modernized)](vmware-azure-tutorial-failover-failback-modernized.md#re-protect-the-on-premises-machine-to-azure-after-successful-planned-failover)
-
-> [!div class="nextstepaction"]
-> [Cancel failover (modernized)](vmware-azure-tutorial-failover-failback-modernized.md#cancel-planned-failover)
+- [Failover VMware VMs to Azure (modernized)](vmware-azure-tutorial-failover-failback-modernized.md)
+- [Planned failover (modernized)](vmware-azure-tutorial-failover-failback-modernized#planned-failover-from-azure-to-on-premises.md)
+- [Reprotect (modernized)](vmware-azure-tutorial-failover-failback-modernized.md#re-protect-the-on-premises-machine-to-azure-after-successful-planned-failover)
+- [Cancel failover (modernized)](vmware-azure-tutorial-failover-failback-modernized.md#cancel-planned-failover)
 
 
diff --git a/articles/site-recovery/hybrid-how-to-enable-replication-private-endpoints.md b/articles/site-recovery/hybrid-how-to-enable-replication-private-endpoints.md
@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
 ms.author: ankitadutta
 ms.service: azure-site-recovery
 ms.topic: how-to
-ms.date: 04/08/2024
+ms.date: 12/19/2024
 ms.custom: subject-rbac-steps, engagement-fy23
 ---
 # Replicate on-premises machines by using private endpoints
diff --git a/articles/site-recovery/hyper-v-azure-failback.md b/articles/site-recovery/hyper-v-azure-failback.md
@@ -1,12 +1,10 @@
 ---
 title: Fail back Hyper-V VMs from Azure with Azure Site Recovery 
 description: How to fail back Hyper-V VMs to an on-premises site from Azure with Azure Site Recovery.
-services: site-recovery
 author: ankitaduttaMSFT
-manager: gaggupta
 ms.service: azure-site-recovery
 ms.topic: tutorial
-ms.date: 12/14/2023
+ms.date: 12/19/2024
 ms.author: ankitadutta
 ms.custom: engagement-fy23
 
@@ -22,7 +20,7 @@ This article describes how to fail back Azure VMs that were created after failov
 
 ## Before you start
 
-1. [Review the types of failback](failover-failback-overview.md#hyper-v-reprotectionfailback) you can use - original location recovery and alternate location recovery.
+1. [Review the types of failback](concepts-types-of-failback.md) you can use - original location recovery and alternate location recovery.
 2. Ensure that the Azure VMs are using managed disks. Failback of Hyper-V virtual machines, that failed over to Azure machines using managed disks, is supported. It is not recommended to use storage accounts, as they will be [fully retired on September 30, 2025](/azure/virtual-machines/unmanaged-disks-deprecation).
 3. Check that the on-premises Hyper-V host (or System Center VMM server if you're using with Site Recovery) is running and connected to Azure. 
 4. Make sure that failover and commit are complete for the VMs. You don't need to set up any specific Site Recovery components for failback of Hyper-V VMs from Azure.
@@ -35,7 +33,7 @@ This article describes how to fail back Azure VMs that were created after failov
 
 To fail back Hyper-V VMs in Azure to the original on-premises VM, run a planned failover from Azure to the on-premises site as follows:
 
-1. In the vault > **Replicated items**, select the VM. Right-click the VM > **Planned Failover**. If you're failing back a recovery plan, select the plan name and click **Failover** > **Planned Failover**.
+1. In the vault > **Replicated items**, select the VM. Right-click the VM > **Planned Failover**. If you're failing back a recovery plan, select the plan name and select **Failover** > **Planned Failover**.
 2. In **Confirm Planned Failover**, choose the source and target locations. Note the failover direction. If the failover from primary worked as expected and all virtual machines are in the secondary location this is for information only.
 3. In **Data Synchronization**, select an option:
 	- **Synchronize data before failover (synchronize delta changes only)**—This option minimizes downtime for VMs as it synchronizes without shutting them down.
@@ -47,13 +45,13 @@ To fail back Hyper-V VMs in Azure to the original on-premises VM, run a planned
 
 4. For VMM only, if data encryption is enabled for the cloud, in **Encryption Key**, select the certificate that was issued when you enabled data encryption during Provider installation on the VMM server.
 5. Initiate the failover. You can follow the failover progress on the **Jobs** tab.
-6. If you selected the option to synchronize the data before the failover, after the initial data synchronization is complete and you're ready to shut down the virtual machines in Azure, click **Jobs** > job name > **Complete Failover**. This does the following:
+6. If you selected the option to synchronize the data before the failover, after the initial data synchronization is complete and you're ready to shut down the virtual machines in Azure, select **Jobs** > job name > **Complete Failover**. This does the following:
     - Shuts down the Azure machine.
 	- Transfers the latest changes to the on-premises VM.
 	- Starts the on-premises VM.
 7. You can now sign into the on-premises VM machine to check that it's available as expected.
-8. The virtual machine is in a commit pending state. Click **Commit** to commit the failover.
-9. To complete the failback, click **Reverse Replicate** to start replicating the on-premises VM to Azure again.
+8. The virtual machine is in a commit pending state. Select **Commit** to commit the failover.
+9. To complete the failback, select **Reverse Replicate** to start replicating the on-premises VM to Azure again. You can [failback to original location](hyper-v-azure-failback.md#fail-back-to-the-original-location).
 
 
 
@@ -70,11 +68,11 @@ Fail back to an alternate location as follows:
 	- **Phase 1**: Takes snapshot of the Azure VM and copies it to the on-premises Hyper-V host. The machine continues running in Azure.
 	- **Phase 2**: Shuts down the Azure VM so that no new changes occur there. The final set of changes is transferred to the on-premises server and the on-premises virtual machine is started up.
 	
-7. Click the checkmark to begin the failover (failback).
-8. After the initial synchronization finishes and you're ready to shut down the Azure VM, click **Jobs** > \<planned failover job> > **Complete Failover**. This shuts down the Azure machine, transfers the latest changes to the on-premises VM, and starts it.
+7. Select the checkmark to begin the failover (failback).
+8. After the initial synchronization finishes and you're ready to shut down the Azure VM, select **Jobs** > \<planned failover job> > **Complete Failover**. This shuts down the Azure machine, transfers the latest changes to the on-premises VM, and starts it.
 9. You can sign into the on-premises VM to verify that everything is working as expected.
-10. Click **Commit** to finish the failover. Commit deletes the Azure VM and its disks, and prepares the on-premises VM to be protected again.
-10. Click **Reverse Replicate** to start replicating the on-premises VM to Azure. Only the delta changes since the VM was turned off in Azure will be replicated.
+10. Select **Commit** to finish the failover. Commit deletes the Azure VM and its disks, and prepares the on-premises VM to be protected again.
+11. Select **Reverse Replicate** to start replicating the on-premises VM to Azure. Only the delta changes since the VM was turned off in Azure will be replicated. You can now [fail back to the alternate location](hyper-v-azure-failback.md#fail-back-to-an-alternate-location).
 
     > [!NOTE]
     > - If you cancel the failback job during data synchronization, the on-premises VM will be in a corrupted state. This is because data synchronization copies the latest data from Azure VM disks to the on-premises data disks, and until the synchronization completes, the disk data may not be in a consistent state. If the on-premises VM starts after data synchronization is canceled, it might not boot. In this case, rerun the failover to complete data synchronization.
diff --git a/articles/site-recovery/toc.yml b/articles/site-recovery/toc.yml
@@ -65,8 +65,6 @@
       href: tutorial-dr-drill-azure.md
     - name: Fail over to Azure
       href: hyper-v-azure-failover-failback-tutorial.md
-    - name: Enable on-premises replication with private endpoints
-      href: ./hybrid-how-to-enable-replication-private-endpoints.md
   - name: Set up replication for Hyper-V VMs
     href: hyper-v-azure-tutorial.md
   - name: Azure VMware Solution disaster recovery to Azure
@@ -91,6 +89,8 @@
       href: move-from-classic-to-modernized-vmware-disaster-recovery.md
     - name: Move from classic to modernized VMware disaster recovery
       href: how-to-move-from-classic-to-modernized-vmware-disaster-recovery.md
+    - name: Deploy Azure Site Recovery replication appliance (modernized)
+      href: deploy-vmware-azure-replication-appliance-modernized.md
   - name: Set up disaster recovery for Azure Public Multi-Access Edge Compute (MEC) VMs  
     items:
     - name: Disaster recovery using the Recovery Services vault
@@ -177,8 +177,6 @@
     items:
     - name: Deprecation of classic experience
       href: vmware-physical-azure-classic-deprecation.md
-    - name: Deploy Azure Site Recovery replication appliance (modernized)
-      href: deploy-vmware-azure-replication-appliance-modernized.md
     - name: Failover and failback - Modernized
       href: failover-failback-overview-modernized.md
     - name: VMware to Azure architecture - Modernized
@@ -424,7 +422,9 @@
     - name: Set up disaster recovery at scale
       href: vmware-physical-large-deployment.md
     - name: Run failover and failback
-      href: physical-to-azure-failover-failback.md           
+      href: physical-to-azure-failover-failback.md 
+    - name: Enable on-premises replication with private endpoints
+      href: ./hybrid-how-to-enable-replication-private-endpoints.md          
     - name: Manage
       items:
       - name: Manage the Mobility service
