Merge pull request #17993 from MicrosoftDocs/main

5/20/2025 PM Publish

Author: Taojunshen

azure-local/manage/azure-site-recovery.md

@@ -4,7 +4,7 @@ description: Use Azure Site Recovery to protect Hyper-V VM workloads running on
 ms.topic: article
 author: alkohli
 ms.author: alkohli
-ms.date: 04/29/2025
+ms.date: 05/20/2025
 ---
 <!-- This article is used by the Windows Server Docs, all links must be site relative (except include files). For example, /azure-stack/hci/manage/azure-site-recovery -->
 
@@ -32,7 +32,7 @@ The disaster recovery strategy for Azure Site Recovery consists of the following
 In the current implementation of Azure Site Recovery integration with Azure Local, you can start the disaster recovery and prepare the infrastructure from the Azure Local resource in the Azure portal. After the preparation is complete, you can finish the remaining steps from the Site Recovery resource in the Azure portal.
 
 > [!NOTE]
-> Azure Site Recovery doesn't support the replication, failover, and failback of the Azure Arc resource bridge and Azure Local VMs enabled by Azure Arc.
+> To test Azure Site Recovery for Azure Local VMs, you can temporarily configure Application Control policy to **Audit** mode. However, using **Audit** policy mode isn't recommended for production environments. To set policy mode to **Audit**, follow the instructions in [Manage Application Control for Azure Local](./manage-wdac.md). Once the installation is complete, revert the policy mode to **Enforced**.
 
 ## Overall workflow
 
@@ -55,11 +55,11 @@ The following table lists the scenarios that are supported for Azure Site Recove
 
 **Fail over Azure Local VMs to Azure followed by failback**
 
-| **Azure Local VM details** | **Failover**      | **Failback**                                   |
-|--------------------------------|-------------------|------------------------------------------------|
-| Windows Gen 1                  | Failover to Azure | Failback on same host as failover |
-| Windows Gen 2                  | Failover to Azure | Failback on same host as failover |
-| Linux Gen 1                    | Failover to Azure | Failback on same host as failover |
+| **Azure Local VM details** | **Failover** | **Failback** |
+|--|--|--|
+| Windows Gen 1 | Failover to Azure | Failback on same host as failover |
+| Windows Gen 2 | Failover to Azure | Failback on same host as failover |
+| Linux Gen 1 | Failover to Azure | Failback on same host as failover |
 
 > [!NOTE]
 > If an Azure Local VM is deleted after a failover, manual intervention is needed to fail back to the same or a different host..
@@ -243,8 +243,8 @@ Here's a list of known issues and the associated workarounds in this release:
 |----|----------------------|---------------------------|
 | 1. | When you register Azure Site Recovery with a system, a machine fails to install Azure Site Recovery or register to the Azure Site Recovery service.  | In this instance, your VMs may not be protected. Verify that all machines in the system are registered in the Azure portal by going to the **Recovery Services vault** \> **Jobs** \> **Site Recovery Jobs**. |
 | 2. | Azure Site Recovery agent fails to install. No error details are seen at the system or machine levels in the Azure Local portal. | When the Azure Site Recovery agent installation fails, it is because of the one of the following reasons:  <br><br> - Installation fails as Hyper-V isn't set up on the host. </br><br> - The Hyper-V host is already associated to a Hyper-V site and you're trying to install the extension with a different Hyper-V site. </br>  |
-| 3. | Azure Site Recovery agent fails to install. Error message of "Microsoft Azure Site Recovery Provider installation has failed with exit code - 1." appears in the portal with the failed installation. | The installation fails when WDAC is enforced. <br><br> - Setting WDAC to "Audit" mode will allow the installation to complete. However, this isn't recommended for production environments. To set the WDAC mode to be Audit, you can follow the instructions in [Manage WDAC settings with PowerShell](/azure-stack/hci/manage/manage-wdac#manage-wdac-settings-with-powershell) |
-| 4. | Failback of an Azure Local VM to an alternate cluster fails. | Failback of an Azure Local VM to an alternate cluster is not supported |
+| 3. | Azure Site Recovery agent fails to install. Error message of "Microsoft Azure Site Recovery Provider installation has failed with exit code - 1." appears in the portal with the failed installation. | The installation fails when Application Control is enforced. <br><br> - Setting Application Control policy mode to **Audit** mode will allow the installation to complete. However, this isn't recommended for production environments. To set the policy mode to **Audit**, follow the instructions in [Manage Application Control for Azure Local](./manage-wdac.md#manage-application-control-settings-with-powershell). |
+| 4. | Failback of an Azure Local VM to an alternate cluster fails. | Failback of an Azure Local VM to an alternate cluster is not supported. |
 
 ## Next steps
 

azure-local/manage/sdn-log-collection.md

@@ -72,7 +72,7 @@ Follow these steps to install the `SdnDiagnostics` PowerShell module on the clie
 1. To confirm the version of `SdnDiagnostics` module loaded into the runspace, run the following cmdlet:
 
     ```powershell
-    Get-Module -Name SdnDiagmostics
+    Get-Module -Name SdnDiagnostics
     ```
     - If you have multiple versions loaded into the runspace, we recommend removing and then re-importing the module.