Merge pull request #297583 from ankitaduttaMSFT/0104

PBI 30406202, 28626643

Author: prmerger-automator[bot]

articles/site-recovery/azure-stack-site-recovery.md

@@ -2,7 +2,7 @@
 title: Replicate Azure Stack Hub to Azure using Azure Site Recovery
 description: Learn how to set up disaster recovery to Azure for Azure Stack Hub with the Azure Site Recovery service.
 ms.topic: how-to
-ms.date: 02/05/2025
+ms.date: 04/03/2025
 ms.author: ankitadutta
 ms.custom: engagement-fy23
 ms.service: azure-site-recovery
@@ -26,7 +26,7 @@ In this article, you learn how to:
 > * **Step 2: Set up a Recovery Services vault**. Set up a vault for Site Recovery, and specify what you want to replicate. Site Recovery components and actions are configured and managed in the vault.
 > * **Step 3: Set up the source replication environment**. Set up a Site Recovery configuration server. The configuration server is a single Azure Stack VM that runs all the components needed by Site Recovery. After you've set up the configuration server, you register it in the vault.
 > * **Step 4: Set up the target replication environment**. Select your Azure account, and the Azure storage account and network that you want to use. During replication, VM data is copied to Azure storage. After failover, Azure VMs are joined to the specified network.
-> * **Step 5: Enable replication**. Configure replication settings, and enable replication for VMs. The Mobility service will be installed on a VM when replication is enabled. Site Recovery performs an initial replication of the VM, and then ongoing replication begins.
+> * **Step 5: Enable replication**. Configure replication settings, and enable replication for VMs. The Mobility service will be installed on a VM when replication is enabled. Site Recovery performs an initial replication of the VM, and then ongoing replication begins. Learn how to [install the Mobility service using command prompt (Modernized)](vmware-physical-mobility-service-overview.md#install-the-mobility-service-using-command-prompt-modernized).   
 > * **Step 6: Run a disaster recovery drill**: After replication is up and running, you verify that failover will work as expected by running a drill. To initiate the drill, you run a test failover in Site Recovery. The test failover doesn't impact your production environment.
 
 With these steps complete, you can then run a full failover to Azure as and when you need to.

articles/site-recovery/azure-to-azure-how-to-enable-replication-private-endpoints.md

@@ -30,31 +30,20 @@ Following is a reference architecture on how the replication workflow changes wi
 
 ## Prerequisites and caveats
 
-- Private endpoints can be created only for new Recovery Services vaults that don't have any items
-  registered to the vault. As such, private endpoints **must be created before any items are added
-  to the vault**. Review the pricing structure for
-  [private endpoints](https://azure.microsoft.com/pricing/details/private-link/).
-- When a private endpoint is created for a vault, the vault is locked down and **isn't accessible
-  from networks other than those networks that have private endpoints**.
-- Microsoft Entra ID currently doesn't support private endpoints. As such, IPs and fully
-  qualified domain names required for Microsoft Entra ID to work in a region need to be allowed
-  outbound access from the secured network. You can also use network security group tag "Azure
-  Active Directory" and Azure Firewall tags for allowing access to Microsoft Entra ID, as
-  applicable.
-- **At least nine IP addresses are required** in the subnets of both your source machines and your
-  recovery machines. When you create a private endpoint for the vault, Site Recovery creates five
-  private links for access to its microservices. Further, when you enable the replication, it adds
-  two additional private links for the source and target region pairing.
-- **One additional IP address is required** in both the source and recovery subnets. This IP address
-  is needed only when you need to use private endpoints connecting to cache storage accounts.
-  Private endpoints for storage can only be created on General Purpose v2 type. Review the pricing
-  structure for
-  [data transfer on GPv2](https://azure.microsoft.com/pricing/details/storage/page-blobs/).
-
- ## Creating and using private endpoints for Site Recovery
-
- This section talks about the steps involved in creating and using private endpoints for Azure Site
- Recovery inside your virtual networks.
+- **Private endpoints**:
+    - Private endpoints can be created only for new Recovery Services vaults that don't have any items registered to the vault. As such, private endpoints **must be created before any items are added to the vault**. Review the pricing structure for [private endpoints](https://azure.microsoft.com/pricing/details/private-link/).
+    - Private endpoint for Recovery Services only supports dynamic IP addresses. Static IP addresses are not supported. 
+    - When a private endpoint is created for a vault, the vault is locked down and **isn't accessible from networks other than those networks that have private endpoints**.
+    - Private endpoints for storage can only be created on General Purpose v2 type. Review the pricing structure for [data transfer on GPv2](https://azure.microsoft.com/pricing/details/storage/page-blobs/).
+- **Microsoft Entra ID** currently doesn't support private endpoints. As such, IPs and fully qualified domain names required for Microsoft Entra ID to work in a region need to be allowed outbound access from the secured network. You can also use network security group tag `Azure Active Directory` and Azure Firewall tags for allowing access to Microsoft Entra ID, as applicable.
+- **IP addresses**:
+    - **At least nine IP addresses are required** in the subnets of both your source machines and your recovery machines. When you create a private endpoint for the vault, Site Recovery creates five private links for access to its microservices. Further, when you enable the replication, it adds two additional private links for the source and target region pairing.
+    - **One additional IP address is required** in both the source and recovery subnets. This IP address is needed only when you need to use private endpoints connecting to cache storage accounts.
+
+
+## Creating and using private endpoints for Site Recovery
+
+This section talks about the steps involved in creating and using private endpoints for Azure Site Recovery inside your virtual networks.
 
 > [!NOTE]
 > It's highly recommended that you follow these steps in the same sequence as provided. Failure to
@@ -92,6 +81,9 @@ for the reprotection of failed over machines in the recovery network.
 Ensure that you create a recovery virtual network in your target region as well during this setup
 process.
 
+> [!NOTE]
+> Currently, you can't configure an automation account to use private endpoints for auto agent upgrade. This configuration requires to set up a private endpoint for the vault, however, Automation account cloud jobs can't access Azure resources secured with private endpoints.
+
 Create the first private endpoint for your vault inside your source virtual network using the
 Private Link Center in the portal or through
 [Azure PowerShell](../private-link/create-private-endpoint-powershell.md). Create the second private

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: azure-site-recovery
 ms.topic: tutorial
-ms.date: 11/06/2024
+ms.date: 04/03/2025
 ms.custom: MVC
 ms.author: ankitadutta
 author: ankitaduttaMSFT
@@ -130,6 +130,9 @@ Follow these steps to enable replication:
 
 5. After you select the list of VMs, select **Next** to proceed to source settings. Here, select the [replication appliance](#appliance-selection) and VM credentials. These credentials will be used to push mobility agent on the machine by Azure Site Recovery replication appliance to complete enabling Azure Site Recovery. Ensure accurate credentials are chosen.
 
+   >[!TIP]
+   > In addition to automatic installation, Mobility Services agent can be installed manually or through an automated deployment method, such as Configuration Manager. [Learn more](vmware-physical-mobility-service-overview.md). 
+
    >[!NOTE]
    >For Linux OS, ensure to provide the root credentials. For Windows OS, a user account with admin privileges should be added. These credentials will be used to push Mobility Service on to the source machine during enable replication operation.
 

articles/site-recovery/vmware-physical-mobility-service-overview.md

@@ -6,7 +6,7 @@ manager: gaggupta
 ms.service: azure-site-recovery
 ms.topic: how-to
 ms.author: ankitadutta
-ms.date: 03/21/2025
+ms.date: 04/03/2025
 ms.custom: engagement-fy23, linux-related-content
 ---
 
@@ -78,9 +78,10 @@ During a push installation of the Mobility service, the following steps are perf
 ### Prerequisites
 
 Locate the installer files for the server’s operating system using the following steps:
-- Ensure that all server configurations meet the criteria in the [support matrix](vmware-physical-azure-support-matrix.md#replicated-machines) for disaster recovery of VMware VMs and physical servers to Azure.
+- Ensure that all server configurations meet the [requirements for server's operating system](vmware-physical-azure-support-matrix.md#replicated-machines).
+- [Locate the installer](vmware-physical-mobility-service-overview.md#locate-installer-files) for server's operating system.
 - On the appliance, go to the folder `E:\Software\Agents`.
-- Copy the installer corresponding to the source machine’s operating system and place it on your source machine in a local folder, such as `C:\Program Files (x86)\Microsoft Azure Site Recovery`.
+- Copy the installer corresponding to the source machine’s operating system and place it on your source machine in a local folder, for example `C:\Program Files (x86)\Microsoft Azure Site Recovery`.
 
 
 **Use the following steps to install the mobility service:**
@@ -114,6 +115,17 @@ Locate the installer files for the server’s operating system using the followi
 >[!NOTE]
 > This section is applicable to Azure Site Recovery - Modernized. [Here are the installation instructions for Classic](#install-the-mobility-service-using-command-prompt-classic).
 
+### Prerequisites
+
+### Prerequisites
+
+Locate the installer files for the server’s operating system using the following steps:
+- Ensure that all server configurations meet the [requirements for server's operating system](vmware-physical-azure-support-matrix.md#replicated-machines).
+- [Locate the installer](vmware-physical-mobility-service-overview.md#locate-installer-files) for server's operating system.
+- On the appliance, go to the folder `E:\Software\Agents`.
+- Copy the installer corresponding to the source machine’s operating system and place it on your source machine in a local folder, for example `C:\Program Files (x86)\Microsoft Azure Site Recovery`.
+
+
 ### Windows machine
 
 1. Open command prompt and navigate to the folder where the installer file has been placed.