versions8.7 update

Author: Ankita Dutta

articles/site-recovery/avs-tutorial-dr-drill-azure.md

@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
 manager: rochakm
 ms.service: site-recovery
 ms.topic: tutorial
-ms.date: 09/30/2020
+ms.date: 01/05/2023
 ms.author: ankitadutta
 ms.custom: MVC
 
@@ -20,35 +20,35 @@ This is the fourth tutorial in a series that shows you how to set up disaster re
 In this tutorial, learn how to:
 
 > [!div class="checklist"]
-
 > * Set up an isolated network for the test failover
 > * Prepare to connect to the Azure VM after failover
 > * Run a test failover for a single machine.
 
 > [!NOTE]
 > Tutorials show you the simplest deployment path for a scenario. They use default options where possible, and don't show all possible settings and paths. If you want to learn about the disaster recovery drill steps in more detail, [review this article](site-recovery-test-failover-to-azure.md).
 
-## Before you start
+## Prerequisites
 
-Complete the previous tutorials:
+**Before you begin, complete the previous tutorials:**
 
 1. Make sure you've [set up Azure](avs-tutorial-prepare-azure.md) for disaster recovery to Azure.
 2. Follow [these steps](avs-tutorial-prepare-avs.md) to prepare your Azure VMware Solution deployment for disaster recovery to Azure.
 3. [Set up](avs-tutorial-replication.md) disaster recovery for Azure VMware Solution VMs.
 
 
-## Verify VM properties
+### Verify VM properties
 
 Before you run a test failover, verify the VM properties, and make sure that the  [VMware vSphere VM](vmware-physical-azure-support-matrix.md#replicated-machines) complies with Azure requirements.
 
-1. In **Protected Items**, click **Replicated Items** > and the VM.
+1. In **Protected Items**, select **Replicated Items** > and the VM.
 2. In the **Replicated item** pane, there's a summary of VM information, health status, and the
-   latest available recovery points. Click **Properties** to view more details.
+   latest available recovery points. Select **Properties** to view more details.
 3. In **Compute and Network**, you can modify the Azure name, resource group, target size, availability set, and managed disk settings.
 4. You can view and modify network settings, including the network/subnet in which the Azure VM
    will be located after failover, and the IP address that will be assigned to it.
 5. In **Disks**, you can see information about the operating system and data disks on the VM.
 
+
 ## Create a network for test failover
 
 We recommended that for test failover, you choose a network that's isolated from the production recovery site network specific in the  **Compute and Network** settings for each VM. By default, when you create an Azure virtual network, it is isolated from other networks. The test network should mimic your production network:
@@ -69,18 +69,18 @@ When you run a test failover, the following happens:
 
 Run the test failover as follows:
 
-1. In **Settings** > **Replicated Items**, click the VM > **+Test Failover**.
+1. In **Settings** > **Replicated Items**, select the VM > **+Test Failover**.
 2. Select the **Latest processed** recovery point for this tutorial. This fails over the VM to the latest available point in time. The time stamp is shown. With this option, no time is spent processing data, so it provides a low RTO (recovery time objective).
 3. In **Test Failover**, select the target Azure network to which Azure VMs will be connected after
    failover occurs.
-4. Click **OK** to begin the failover. You can track progress by clicking on the VM to open its
-   properties. Or you can click the **Test Failover** job in vault name > **Settings** > **Jobs** >
+4. Select **OK** to begin the failover. You can track progress by selecting on the VM to open its
+   properties. Or you can select the **Test Failover** job in vault name > **Settings** > **Jobs** >
    **Site Recovery jobs**.
 5. After the failover finishes, the replica Azure VM appears in the Azure portal > **Virtual
    Machines**. Check that the VM is the appropriate size, that it's connected to the right network,
    and that it's running.
 6. You should now be able to connect to the replicated VM in Azure.
-7. To delete Azure VMs created during the test failover, click **Cleanup test failover** on the
+7. To delete Azure VMs created during the test failover, select **Cleanup test failover** on the
   VM. In **Notes**, record and save any observations associated with the test failover.
 
 In some scenarios, failover requires additional processing that takes around eight to ten minutes
@@ -94,6 +94,5 @@ If you want to connect to Azure VMs using RDP/SSH after failover, [prepare to co
 
 ## Next steps
 
-> [!div class="nextstepaction"]
-> [Run a failover](avs-tutorial-failover.md)
+[Learn more](avs-tutorial-failover.md) about running a failover.
 

articles/site-recovery/azure-to-azure-support-matrix.md

@@ -109,8 +109,8 @@ Windows 7 (x64) with SP1 onwards | From version [9.30](https://support.microsoft
 
 **Operating system** | **Details**
 --- | ---
-Red Hat Enterprise Linux | 6.7, 6.8, 6.9, 6.10, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6,[7.7](https://support.microsoft.com/help/4528026/update-rollup-41-for-azure-site-recovery), [7.8](https://support.microsoft.com/help/4564347/), [7.9](https://support.microsoft.com/help/4578241/), [8.0](https://support.microsoft.com/help/4531426/update-rollup-42-for-azure-site-recovery), 8.1, [8.2](https://support.microsoft.com/help/4570609/), [8.3](https://support.microsoft.com/help/4597409/), [8.4](https://support.microsoft.com/topic/883a93a7-57df-4b26-a1c4-847efb34a9e8) (4.18.0-305.30.1.el8_4.x86_64 or higher), [8.5](https://support.microsoft.com/topic/883a93a7-57df-4b26-a1c4-847efb34a9e8) (4.18.0-348.5.1.el8_5.x86_64 or higher), [8.6](https://support.microsoft.com/en-us/topic/update-rollup-62-for-azure-site-recovery-e7aff36f-b6ad-4705-901c-f662c00c402b) 
-CentOS | 6.5, 6.6, 6.7, 6.8, 6.9, 6.10 </br> 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6, 7.7, [7.8](https://support.microsoft.com/help/4564347/), [7.9 pre-GA version](https://support.microsoft.com/help/4578241/), 7.9 GA version is supported from 9.37 hot fix patch** </br> 8.0, 8.1, [8.2](https://support.microsoft.com/help/4570609), [8.3](https://support.microsoft.com/help/4597409/), 8.4 (4.18.0-305.30.1.el8_4.x86_64 or later), 8.5 (4.18.0-348.5.1.el8_5.x86_64 or later), 8.6. 
+Red Hat Enterprise Linux | 6.7, 6.8, 6.9, 6.10, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6,[7.7](https://support.microsoft.com/help/4528026/update-rollup-41-for-azure-site-recovery), [7.8](https://support.microsoft.com/help/4564347/), [7.9](https://support.microsoft.com/help/4578241/), [8.0](https://support.microsoft.com/help/4531426/update-rollup-42-for-azure-site-recovery), 8.1, [8.2](https://support.microsoft.com/help/4570609/), [8.3](https://support.microsoft.com/help/4597409/), [8.4](https://support.microsoft.com/topic/883a93a7-57df-4b26-a1c4-847efb34a9e8) (4.18.0-305.30.1.el8_4.x86_64 or higher), [8.5](https://support.microsoft.com/topic/883a93a7-57df-4b26-a1c4-847efb34a9e8) (4.18.0-348.5.1.el8_5.x86_64 or higher), [8.6](https://support.microsoft.com/en-us/topic/update-rollup-62-for-azure-site-recovery-e7aff36f-b6ad-4705-901c-f662c00c402b), 8.7 (Not available in China regions).
+CentOS | 6.5, 6.6, 6.7, 6.8, 6.9, 6.10 </br> 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6, 7.7, [7.8](https://support.microsoft.com/help/4564347/), [7.9 pre-GA version](https://support.microsoft.com/help/4578241/), 7.9 GA version is supported from 9.37 hot fix patch** </br> 8.0, 8.1, [8.2](https://support.microsoft.com/help/4570609), [8.3](https://support.microsoft.com/help/4597409/), 8.4 (4.18.0-305.30.1.el8_4.x86_64 or later), 8.5 (4.18.0-348.5.1.el8_5.x86_64 or later), 8.6, 8.7 (Not available in China regions). 
 Ubuntu 14.04 LTS Server | Includes support for all 14.04.*x* versions; [Supported kernel versions](#supported-ubuntu-kernel-versions-for-azure-virtual-machines);
 Ubuntu 16.04 LTS Server | Includes support for all 16.04.*x* versions; [Supported kernel version](#supported-ubuntu-kernel-versions-for-azure-virtual-machines)<br/><br/> Ubuntu servers using password-based authentication and sign-in, and the cloud-init package to configure cloud VMs, might have password-based sign-in disabled on failover (depending on the cloudinit configuration). Password-based sign in can be re-enabled on the virtual machine by resetting the password from the Support > Troubleshooting > Settings menu (of the failed over VM in the Azure portal.
 Ubuntu 18.04 LTS Server | Includes support for all 18.04.*x* versions; [Supported kernel version](#supported-ubuntu-kernel-versions-for-azure-virtual-machines)<br/><br/> Ubuntu servers using password-based authentication and sign-in, and the cloud-init package to configure cloud VMs, might have password-based sign-in disabled on failover (depending on the cloudinit configuration). Password-based sign in can be re-enabled on the virtual machine by resetting the password from the Support > Troubleshooting > Settings menu (of the failed over VM in the Azure portal.

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

@@ -17,10 +17,7 @@ This tutorial shows you how to migrate on-premises servers running Windows Serve
 In this tutorial, you learn how to:
 
 > [!div class="checklist"]
-> * Prepare your on-premises environment for migration.
-> * Set up the target environment.
-> * Set up a replication policy.
-> * Enable replication.
+> * Migrate on-premises Windows Server 2008 machines to Azure.
 > * Run a test migration to make sure everything's working as expected.
 > * Fail over to Azure and complete the migration.
 
@@ -39,7 +36,7 @@ We recommend that you migrate machines to Azure using the [Azure Migrate](../mig
 
 
 |Operating System  | Environment  |
-|---------|---------|
+|------------------|--------------|
 |Windows Server 2008 SP2 - 32 bit and 64 bit(IA-32 and x86-64)</br>- Standard</br>- Enterprise</br>- Datacenter   |     VMware VMs, Hyper-V VMs, and Physical Servers    |
 |Windows Server 2008 R2 SP1 - 64 bit</br>- Standard</br>- Enterprise</br>- Datacenter     |     VMware VMs, Hyper-V VMs, and Physical Servers|
 
@@ -50,7 +47,7 @@ We recommend that you migrate machines to Azure using the [Azure Migrate](../mig
 
 ### Prerequisites
 
-Before you start, it's helpful to review the Azure Site Recovery architecture for [VMware and physical server migration](vmware-azure-architecture.md) or [Hyper-V virtual machine migration](hyper-v-azure-architecture.md) 
+Before you start, it's helpful to review the Azure Site Recovery architecture for [VMware and physical server migration](vmware-azure-architecture.md) or [Hyper-V virtual machine migration](hyper-v-azure-architecture.md).
 
 To migrate Hyper-V virtual machines running Windows Server 2008 or Windows Server 2008 R2, follow the steps in the [migrate on-premises machines to Azure](migrate-tutorial-on-premises-azure.md) tutorial.
 
@@ -79,7 +76,7 @@ The rest of this tutorial shows you how you can migrate on-premises VMware virtu
   > [!TIP]
   > A test failover is highly recommended before migrating servers. Ensure that  you've performed at least one successful test failover on each server that you  are migrating. As part of the test failover, connect to the test failed over  machine and ensure things work as expected.
   >
-  >The test failover operation is non-disruptive and helps you test migrations by  creating virtual machines in an isolated network of your choice. Unlike the  failover operation, during the test failover operation, data replication  continues to progres. You can perform as many test failovers as you like before  you are ready to migrate. 
+  >The test failover operation is non-disruptive and helps you test migrations by  creating virtual machines in an isolated network of your choice. Unlike the  failover operation, during the test failover operation, data replication  continues to progress. You can perform as many test failovers as you like before  you are ready to migrate. 
   >