Merge pull request #276148 from ankitaduttaMSFT/steps

v-dirichards · web-flow · commit 44c99a541bda · 2024-05-23T09:54:02.000-05:00
next steps aligned
diff --git a/articles/site-recovery/azure-to-azure-how-to-enable-zone-to-zone-disaster-recovery.md b/articles/site-recovery/azure-to-azure-how-to-enable-zone-to-zone-disaster-recovery.md
@@ -134,7 +134,5 @@ No. You must fail over to a different resource group.
 The steps that you follow to run a disaster recovery drill, fail over, reprotect, and failback are the same as the steps in an Azure-to-Azure disaster recovery scenario.
 
 - To perform a disaster recovery drill, follow the steps outlined in [Tutorial: Run a disaster recovery drill for Azure VMs](./azure-to-azure-tutorial-dr-drill.md).
-
 - To perform a failover and reprotect VMs in the secondary zone, follow the steps outlined in [Tutorial: Fail over Azure VMs to a secondary region](./azure-to-azure-tutorial-failover-failback.md).
-
 - To fail back to the primary zone, follow the steps outlined [Tutorial: Fail back Azure VMs to the primary region](./azure-to-azure-tutorial-failback.md).
diff --git a/articles/site-recovery/azure-to-azure-how-to-reprotect.md b/articles/site-recovery/azure-to-azure-how-to-reprotect.md
@@ -5,7 +5,7 @@ services: site-recovery
 author: ankitaduttaMSFT
 ms.service: site-recovery
 ms.topic: tutorial
-ms.date: 04/08/2024
+ms.date: 05/23/2024
 ms.author: ankitadutta
 ---
 
diff --git a/articles/site-recovery/how-to-move-from-classic-to-modernized-vmware-disaster-recovery.md b/articles/site-recovery/how-to-move-from-classic-to-modernized-vmware-disaster-recovery.md
@@ -3,19 +3,18 @@ title: How to move from classic to modernized VMware disaster recovery?
 description: This article describes how to move from classic to modernized VMware disaster recovery.
 ms.author: ankitadutta
 author: ankitaduttaMSFT
-manager: jsuri
 ms.service: site-recovery
 ms.topic: how-to
-ms.date: 01/13/2023
+ms.date: 05/23/2024
 ms.custom: engagement-fy23
 ---
 
 # How to move from classic to modernized VMware disaster recovery  
 
-This article provides information about how you can move/migrate your VMware or Physical machine replications from [classic](./vmware-azure-architecture.md) to [modernized](./vmware-azure-architecture-modernized.md) protection architecture. With this capability to migrate, you can successfully transfer your replicated items from a configuration server to an Azure Site Recovery replication appliance. This migration is guided by a smart replication mechanism which ensures that the complete initial replication is not performed again for non-critical replicated items, and only the differential data is transferred. 
+This article provides information about how you can move/migrate your VMware or Physical machine replications from [classic](./vmware-azure-architecture.md) to [modernized](./vmware-azure-architecture-modernized.md) protection architecture. With this capability to migrate, you can successfully transfer your replicated items from a configuration server to an Azure Site Recovery replication appliance. This migration is guided by a smart replication mechanism, which ensures that the complete initial replication is not performed again for noncritical replicated items, and only the differential data is transferred. 
 
-> [!Note]
-> - Recovery plans will not be migrated and will need to be created again in the modernized Recovery Services vault.   
+> [!NOTE]
+> - Recovery plans is not migrated and must be created again in the modernized Recovery Services vault.   
 
 ## Prerequisites  
 
@@ -33,9 +32,9 @@ Follow these steps to move the replicated items from classic architecture to mod
 
 2. Select **Upgrade to modernized VMware replication**. The **Pre-requisites** details are displayed. Ensure you read through the prerequisites and then select **Next** to proceed to configure the migration settings.
 
-    :::image type="Pre-requisites" source="media/migrate-tool/prerequisites-inline.png" alt-text="Screenshot showing prerequisites." lightbox="media/migrate-tool/prerequisites-expanded.png":::
+    :::image type="Prerequisites" source="media/migrate-tool/prerequisites-inline.png" alt-text="Screenshot showing prerequisites." lightbox="media/migrate-tool/prerequisites-expanded.png":::
 
-3. Select the modernized vault you plan to move to, machines from the current vault which will be moved to the modernized vault and an appliance for each of them.
+3. Select the modernized vault you plan to move to, machines from the current vault, which is moved to the modernized vault and an appliance for each of them.
 
    :::image type="Migration settings" source="media/migrate-tool/migration-settings-inline.png" alt-text="Screenshot showing migration settings." lightbox="media/migrate-tool/migration-settings-expanded.png":::
 
@@ -53,21 +52,21 @@ Follow these steps to move the replicated items from classic architecture to mod
 
 ### During the migration of machines   
 
-During the migration of a replicated item, continuous replication may get broken for some time. Replication continues as soon as the migration is complete. During migration, you will be allowed to do **Failover** operation. The last available recovery point will be present for selection and can be chosen for replication.   
+During the migration of a replicated item, continuous replication may get broken for some time. Replication continues as soon as the migration is complete. During migration, you are allowed to do **Failover** operation. The last available recovery point is present for selection and can be chosen for replication.   
 
-While the migration is in progress, you can only perform **Failover** operation. Once the migration is complete, data will start replicating using the modernized architecture and the new vault. All the operations will be available for you to perform from the new vault.   
+While the migration is in progress, you can only perform **Failover** operation. Once the migration is complete, data starts replicating using the modernized architecture and the new vault. All the operations are available for you to perform from the new vault.   
 
-> [!Note]
-> If the migration fails, then we will automatically rollback the changes and ensure the replication starts again from the classic vault.   
+> [!NOTE]
+> If the migration fails, Site Recovery automatically rolls back the changes and ensures the replication starts again from the classic vault.   
 
 ### Post migration operations from Classic vault  
 
-**Failover** and **Disable replication** operations will continue to be available from the classic vault even after migration is performed successfully. The classic vault will continue to exist till the retention period of last available recovery point has expired. Once the retention period is up, the vault will be cleaned up automatically. During this time, recovery points from both the vaults can be used for failover. It will depend on your failover needs to select a proper recovery point.  
+**Failover** and **Disable replication** operations continue to be available from the classic vault even after migration is performed successfully. The classic vault continues to exist until the retention period of last available recovery point has expired. Once the retention period is up, the vault is cleaned up automatically. During this time, recovery points from both the vaults can be used for failover. It depends on your failover needs to select a proper recovery point.  
 
-Till deletion of classic vault, you will continue to get charged for the retention points. Once the deletion has been done, no charges will be associated to the classic vault.  
+You can continue to get charged for the retention points until the deletion of classic vault, . Once the deletion is done, no charge is associated to the classic vault.  
 
-After migration, if the failover is performed using the classic vault, then the replicated items present in the modernized vault will be automatically cleaned up. Once done, all the further operations, such as commit, re-protect, failback, will only be possible via the classic vault.   
+After migration, if the failover is performed using the classic vault, then the replicated items present in the modernized vault is automatically cleaned up. Once done, all the further operations, such as commit, reprotect, failback, is only possible via the classic vault.   
 
 ## Next steps
 
-[move from classic to modernized VMware disaster recovery](move-from-classic-to-modernized-vmware-disaster-recovery.md)
+-  Learn to [move from classic to modernized VMware disaster recovery](move-from-classic-to-modernized-vmware-disaster-recovery.md).
diff --git a/articles/site-recovery/hyper-v-prepare-on-premises-tutorial.md b/articles/site-recovery/hyper-v-prepare-on-premises-tutorial.md
@@ -3,7 +3,7 @@ title: Prepare on-premises Hyper-V servers for disaster recovery by using Azure
 description: Learn how to prepare on-premises Hyper-V VMs for disaster recovery to Azure by using Azure Site Recovery.
 ms.service: site-recovery
 ms.topic: tutorial
-ms.date: 03/02/2023
+ms.date: 05/23/2024
 ms.custom: MVC, engagement-fy23
 ms.author: ankitadutta
 author: ankitaduttaMSFT
@@ -88,8 +88,5 @@ After failover, you can access Azure VMs by using the same IP address as the rep
 
 ## Next steps
 
-> [!div class="nextstepaction"]
-> [Set up disaster recovery to Azure for Hyper-V VMs](./hyper-v-azure-tutorial.md)
-
-> [!div class="nextstepaction"]
-> [Set up disaster recovery to Azure for Hyper-V VMs in Virtual Machine Manager clouds](./hyper-v-vmm-azure-tutorial.md)
+- [Set up disaster recovery to Azure for Hyper-V VMs](./hyper-v-azure-tutorial.md)
+- [Set up disaster recovery to Azure for Hyper-V VMs in Virtual Machine Manager clouds](./hyper-v-vmm-azure-tutorial.md).
diff --git a/articles/site-recovery/hyper-v-vmm-azure-tutorial.md b/articles/site-recovery/hyper-v-vmm-azure-tutorial.md
@@ -2,7 +2,7 @@
 title: Set up Hyper-V (with VMM) disaster recovery using Azure Site Recovery
 description: Learn how to set up disaster recovery of on-premises Hyper-V VMs in System Center VMM clouds to Azure by using Site Recovery.
 ms.topic: tutorial
-ms.date: 03/19/2020
+ms.date: 05/23/2024
 ms.custom: MVC
 ms.author: ankitadutta
 ms.service: site-recovery
@@ -156,5 +156,4 @@ Site Recovery checks that there's one or more compatible Azure storage accounts
 
 ## Next steps
 
-> [!div class="nextstepaction"]
-> [Run a disaster recovery drill](tutorial-dr-drill-azure.md)
+- [Run a disaster recovery drill](tutorial-dr-drill-azure.md).
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
@@ -3,7 +3,7 @@ title: Move from classic to modernized VMware disaster recovery.
 description: Learn about the architecture, necessary infrastructure, and FAQs about moving your VMware or Physical machine replications from classic to modernized protection architecture.
 ms.service: site-recovery
 ms.topic: conceptual
-ms.date: 04/01/2024
+ms.date: 05/23/2024
 author: ankitaduttaMSFT
 ms.author: ankitadutta
 ms.custom: engagement-fy23
@@ -198,4 +198,4 @@ Note that, non-private endpoint to private endpoint migration is not supported,
 
 ## Next steps
 
-[How to move from classic to modernized VMware disaster recovery](how-to-move-from-classic-to-modernized-vmware-disaster-recovery.md)
+- Learn [how to move from classic to modernized VMware disaster recovery](how-to-move-from-classic-to-modernized-vmware-disaster-recovery.md).
diff --git a/articles/site-recovery/quickstart-create-vault-bicep.md b/articles/site-recovery/quickstart-create-vault-bicep.md
@@ -4,7 +4,7 @@ description: In this quickstart, you learn how to create an Azure Recovery Servi
 author: ankitaduttaMSFT
 ms.service: site-recovery
 ms.author: ankitadutta
-ms.date: 12/15/2023
+ms.date: 05/23/2024
 ms.topic: quickstart
 ms.custom: subject-armqs, mode-arm, devx-track-bicep
 ---
@@ -102,7 +102,4 @@ Remove-AzResourceGroup -Name exampleRG
 
 ## Next steps
 
-In this quickstart, you created a Recovery Services vault using Bicep. To learn more about disaster recovery, continue to the next quickstart article.
-
-> [!div class="nextstepaction"]
-> [Set up disaster recovery](azure-to-azure-quickstart.md)
+In this quickstart, you created a Recovery Services vault using Bicep. To learn more about disaster recovery, continue to the next quickstart article - [Set up disaster recovery](azure-to-azure-quickstart.md).
diff --git a/articles/site-recovery/quickstart-create-vault-template.md b/articles/site-recovery/quickstart-create-vault-template.md
@@ -1,7 +1,7 @@
 ---
 title: Quickstart to create an Azure Recovery Services vault using an Azure Resource Manager template.
 description: In this quickstart, you learn how to create an Azure Recovery Services vault using an Azure Resource Manager template (ARM template).
-ms.date: 12/15/2023
+ms.date: 05/23/2024
 ms.topic: quickstart
 ms.custom: subject-armqs, mode-arm, devx-track-arm-template
 ms.author: ankitadutta
@@ -43,7 +43,7 @@ Two Azure resources are defined in the template:
 - [Microsoft.RecoveryServices/vaults/backupstorageconfig](/rest/api/backup/backup-resource-storage-configs): configures the vault's backup redundancy settings.
 
 The template includes optional parameters for the vault's backup configuration. The storage
-redundancy settings are locally-redundant storage (LRS) or geo-redundant storage (GRS). For more
+redundancy settings are locally redundant storage (LRS) or geo-redundant storage (GRS). For more
 information, see [Set storage redundancy](../backup/backup-create-rs-vault.md#set-storage-redundancy).
 
 For more Azure Recovery Services templates, see [Azure Quickstart Templates](https://azure.microsoft.com/resources/templates/?resourceType=Microsoft.Recoveryservices&pageNumber=1&sort=Popular).
@@ -167,7 +167,4 @@ Write-Host "Press [ENTER] to continue..."
 ## Next steps
 
 In this quickstart, you created a Recovery Services vault. To learn more about disaster recovery,
-continue to the next quickstart article.
-
-> [!div class="nextstepaction"]
-> [Set up disaster recovery](azure-to-azure-quickstart.md)
+continue to the next quickstart article - [Set up disaster recovery](azure-to-azure-quickstart.md).
diff --git a/articles/site-recovery/tutorial-dr-drill-azure.md b/articles/site-recovery/tutorial-dr-drill-azure.md
@@ -3,7 +3,7 @@ title: Run a disaster recovery drill to Azure with Azure Site Recovery
 description: Learn how to run a disaster recovery drill from on-premises to Azure, with Azure Site Recovery.
 ms.service: site-recovery
 ms.topic: tutorial
-ms.date: 11/12/2019
+ms.date: 05/23/2024
 ms.custom: MVC
 ms.author: ankitadutta
 author: ankitaduttaMSFT
@@ -92,7 +92,6 @@ If you want to connect to Azure VMs using RDP/SSH after failover, [prepare to co
 
 ## Next steps
 
-> [!div class="nextstepaction"]
-> [Run a failover and failback for VMware VMs](vmware-azure-tutorial-failover-failback.md)
-> [Run a failover and failback for Hyper-V VMs](hyper-v-azure-failover-failback-tutorial.md)
-> [Run a failover and failback for physical machines](physical-to-azure-failover-failback.md)
+- [Run a failover and failback for VMware VMs](vmware-azure-tutorial-failover-failback.md)
+- [Run a failover and failback for Hyper-V VMs](hyper-v-azure-failover-failback-tutorial.md)
+- [Run a failover and failback for physical machines](physical-to-azure-failover-failback.md).
diff --git a/articles/site-recovery/vmware-azure-set-up-replication-tutorial-modernized.md b/articles/site-recovery/vmware-azure-set-up-replication-tutorial-modernized.md
@@ -3,7 +3,7 @@ title: Set up VMware VM disaster recovery to Azure with Azure Site Recovery - Mo
 description: Learn how to set up disaster recovery to Azure for on-premises VMware VMs with Azure Site Recovery - Modernized.
 ms.service: site-recovery
 ms.topic: tutorial
-ms.date: 03/13/2024
+ms.date: 05/23/2024
 ms.custom: MVC
 ms.author: ankitadutta
 author: ankitaduttaMSFT
@@ -184,6 +184,5 @@ Follow these steps to enable replication:
 - Same replication appliance can be used both for forward and backward protection operations, if it is in a non-critical state. It should not impact the performance of the replications.
 
 ## Next steps
-After enabling replication, run a drill to make sure everything's working as expected.
-> [!div class="nextstepaction"]
-> [Run a disaster recovery drill](site-recovery-test-failover-to-azure.md)
+After enabling replication, [run a disaster recovery drill](site-recovery-test-failover-to-azure.md) to make sure everything's working as expected.
+
