Merge pull request #292318 from ankitaduttaMSFT/eeetasks

prmerger-automator[bot] · web-flow · commit e92284d329ad · 2024-12-27T11:26:30.000Z
2312 EEE tasks
diff --git a/articles/migrate/migrate-support-matrix-hyper-v-migration.md b/articles/migrate/migrate-support-matrix-hyper-v-migration.md
@@ -58,7 +58,6 @@ You can select up to 10 VMs at once for replication. If you want to migrate more
 | **IPv6** | Not supported.|
 | **NIC teaming** | Not supported.|
 | **Azure Site Recovery and/or Hyper-V** | You can't replicate using Migration and modernization if the VM is enabled for replication with Azure Site Recovery or with Hyper-V replica.|
-| **Ports** | Outbound connections on HTTPS port 443 to send VM replication data.|
 
 
 ### URL access (public cloud)
diff --git a/articles/site-recovery/azure-to-azure-how-to-enable-replication-cmk-disks.md b/articles/site-recovery/azure-to-azure-how-to-enable-replication-cmk-disks.md
@@ -2,11 +2,10 @@
 title: Enable replication of encrypted Azure VMs in Azure Site Recovery
 description: This article describes how to configure replication for VMs with customer-managed key (CMK) enabled disks from one Azure region to another by using Site Recovery.
 author: ankitaduttaMSFT
-manager: rochakm
 ms.service: azure-site-recovery
 ms.custom: devx-track-azurepowershell
 ms.topic: how-to
-ms.date: 03/27/2024
+ms.date: 12/23/2024
 ms.author: ankitadutta
 ---
 
@@ -17,6 +16,9 @@ This article describes how to replicate Azure VMs with Customer-Managed Keys (CM
 ## Prerequisite
 You must create the Disk Encryption set(s) in the target region for the target subscription before enabling replication for your virtual machines that have CMK-enabled managed disks.
 
+> [!NOTE]
+> Azure Site Recovery doesn't support rotating the key for an encrypted virtual machine while it is protected. If you rotate the keys, you must disable and re-enable the replication.
+
 ## Enable replication
 
 Use the following procedure to replicate machines with Customer-Managed Keys (CMK) enabled disks. 
diff --git a/articles/site-recovery/azure-to-azure-how-to-enable-replication.md b/articles/site-recovery/azure-to-azure-how-to-enable-replication.md
@@ -3,9 +3,8 @@ title: Configure replication for Azure VMs in Azure Site Recovery
 description: Learn how to configure replication to another region for Azure VMs, using Site Recovery.
 author: ankitaduttaMSFT
 ms.author: ankitadutta
-manager: rochakm
 ms.topic: how-to
-ms.date: 03/27/2024
+ms.date: 12/23/2024
 ms.service: azure-site-recovery
 ---
 
@@ -28,10 +27,13 @@ Use the following procedure to replicate Azure VMs to another Azure region. As a
 
 1. In the vault > **Site Recovery** page, under **Azure virtual machines**, select **Enable replication**.
 1. In the **Enable replication** page, under **Source**, do the following:
-   - **Region**: Select the Azure region from where you want to protect your VMs. 
+   - **Region**: Select the source Azure region where VMs are currently running.  If the source resource group is in a different region from the VM, enable replication from the VM > *Disaster Recovery* blade.
    For example, the source location is *East Asia*.
      >[!NOTE]
+     > Only resource groups in the same region as the selected source region will be visible from the Recovery Services Blade to enable replication.
+     >
      >For cross-regional disaster recovery, the source location should be different from the Recovery Services Vault and its Resource Group's location. However, it can be the same as any of them for zonal disaster recovery.
+
    - **Subscription**: Select the subscription to which your source VMs belong. This can be any subscription within the same Microsoft Entra tenant where your recovery services vault exists.
    - **Resource group**: Select the resource group to which your source virtual machines belong. All the VMs in the selected resource group are listed for protection in the next step.
    - **Virtual machine deployment model**: Select Azure deployment model of the source machines.
diff --git a/articles/site-recovery/site-recovery-deployment-planner.md b/articles/site-recovery/site-recovery-deployment-planner.md
@@ -5,10 +5,9 @@ author: ankitaduttaMSFT
 ms.service: azure-site-recovery
 ms.topic: concept-article
 ms.author: ankitadutta
-ms.date: 08/30/2024
+ms.date: 12/23/2024
 ---
 
-
 # About the Azure Site Recovery Deployment Planner for VMware to Azure
 
 This article is the Azure Site Recovery Deployment Planner user guide for VMware to Azure production deployments.
@@ -82,19 +81,19 @@ The tool has two main phases: profiling and report generation. There is also a t
 
 ## Download and extract the deployment planner tool
 
-1. Download the latest version of [Site Recovery Deployment Planner](https://download.microsoft.com/download/6/5/d/65d39a90-c4e2-49a7-9149-af58deb8ef7d/ASRDeploymentPlanner-v3.0.zip).
-The tool is packaged in a .zip folder. The current version of the tool supports only the VMware to Azure scenario.
+1. Download the latest version of [Site Recovery Deployment Planner](https://download.microsoft.com/download/7d07e00c-87c2-4413-b062-50c7095589ec/ASRDeploymentPlanner-v3.1.zip).
+The tool is packaged in a `.zip` folder. The current version of the tool supports only the VMware to Azure scenario.
 
-2. Copy the .zip folder to the Windows server from which you want to run the tool.
+2. Copy the `.zip` folder to the Windows server from which you want to run the tool.
 You can run the tool from Windows Server 2012 R2 if the server has network access to connect to the vCenter Server/vSphere ESXi host that holds the VMs to be profiled. However, we recommend that you run the tool on a server whose hardware configuration meets the [configuration server sizing guidelines](site-recovery-plan-capacity-vmware.md#size-recommendations-for-the-configuration-server-and-inbuilt-process-server). If you already deployed Site Recovery components on-premises, run the tool from the configuration server.
 
     We recommend that you have the same hardware configuration as the configuration server (which has an in-built process server) on the server where you run the tool. Such a configuration ensures that the achieved throughput that the tool reports matches the actual throughput that Site Recovery can achieve during replication. The throughput calculation depends on available network bandwidth on the server and hardware configuration (such as CPU and storage) of the server. If you run the tool from any other server, the throughput is calculated from that server to Azure. Also, because the hardware configuration of the server might differ from that of the configuration server, the achieved throughput that the tool reports might be inaccurate.
 
-3. Extract the .zip folder.
+3. Extract the `.zip` folder.
 The folder contains multiple files and subfolders. The executable file is ASRDeploymentPlanner.exe in the parent folder.
 
     Example:
-    Copy the .zip file to E:\ drive and extract it.
+    Copy the .`zip` file to E:\ drive and extract it.
     E:\ASR Deployment Planner_v2.3.zip
 
     E:\ASR Deployment Planner_v2.3\ASRDeploymentPlanner.exe
@@ -121,4 +120,4 @@ See the [Site Recovery Deployment Planner version history](./site-recovery-deplo
 
 ## Next steps
 
-[Run Site Recovery Deployment Planner](site-recovery-vmware-deployment-planner-run.md)
+[Run Site Recovery Deployment Planner](site-recovery-vmware-deployment-planner-run.md).
diff --git a/articles/site-recovery/site-recovery-retain-ip-azure-vm-failover.md b/articles/site-recovery/site-recovery-retain-ip-azure-vm-failover.md
@@ -2,7 +2,7 @@
 title: Keep IP addresses after Azure VM failover with Azure Site Recovery
 description: Describes how to retain IP addresses when failing over Azure VMs for disaster recovery to a secondary region with Azure Site Recovery
 ms.service: azure-site-recovery
-ms.date: 07/25/2021
+ms.date: 12/23/2024
 author: ankitaduttaMSFT
 ms.topic: concept-article
 ms.author: ankitadutta
@@ -99,7 +99,6 @@ Before failover, the architecture is as follows:
     - **Source VNet 1** and **Source VNet 2** are connected with VPN site-to-site
 - **Recovery VNet 1** and **Recovery VNet 2** aren't connected to any other VNets.
 - **Company A** configures VPN gateways on **Recovery VNet 1** and **Recovery VNet 2**, to reduce RTO.  
-- **Recovery VNet1** and **Recovery VNet2** are not connected with any other virtual network.
 - To reduce recovery time objective (RTO), VPN gateways are configured on **Recovery VNet1** and **Recovery VNet2** prior to failover.
 
     ![Resources in Azure before app failover](./media/site-recovery-retain-ip-azure-vm-failover/azure-to-azure-connectivity-isolated-application-before-failover2.png)
diff --git a/articles/site-recovery/upgrade-mobility-service-modernized.md b/articles/site-recovery/upgrade-mobility-service-modernized.md
@@ -3,7 +3,7 @@ title: Upgrade Mobility Service and appliance components - Modernized
 description: This article describes about automatic updates for mobility agent and the procedure involved with manual updates - Modernized.
 ms.service: azure-site-recovery
 ms.topic: how-to
-ms.date: 08/21/2024
+ms.date: 12/23/2024
 ms.author: ankitadutta
 author: ankitaduttaMSFT
 ---
@@ -266,7 +266,7 @@ To update the Recovery Service agent, download the latest version [here](./site-
 
 3.	To update the Recovery Service agent, run the following command: 
     
-    `MARSAgentInstaller.exe /q /nu - for mars agent`
+    `MARSAgentInstaller.exe /q /nu for mars agent`
 
 #### Update remaining components of appliance
 
