Merge pull request #311725 from Jeronika-MS/freshnessasr

Updated docs for freshness - ASR

Author: Carolyn135

articles/site-recovery/asr-arm-templates.md

@@ -5,7 +5,7 @@ services: site-recovery
 author: Jeronika-MS
 ms.service: azure-site-recovery
 ms.topic: sample
-ms.date: 02/11/2026
+ms.date: 02/12/2026
 ms.author: v-gajeronika
 ms.reviewer: v-gajeronika
 ms.custom: engagement-fy23, devx-track-arm-template

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

@@ -4,7 +4,7 @@ description: Learn how to run a disaster recovery drill from an Azure VMware Sol
 author: Jeronika-MS
 ms.service: azure-site-recovery
 ms.topic: tutorial
-ms.date: 02/11/2026
+ms.date: 02/12/2026
 ms.author: v-gajeronika
 ms.reviewer: v-gajeronika
 ms.custom: MVC

articles/site-recovery/avs-tutorial-failover.md

@@ -4,7 +4,7 @@ description: Learn how to fail over Azure VMware Solution VMs to Azure in Azure
 author: Jeronika-MS
 ms.service: azure-site-recovery
 ms.topic: tutorial
-ms.date: 02/11/2026
+ms.date: 02/12/2026
 ms.author: v-gajeronika
 ms.reviewer: v-gajeronika
 ms.custom: MVC, engagement-fy23

articles/site-recovery/avs-tutorial-prepare-avs.md

@@ -45,7 +45,7 @@ Create the account as follows:
 1. Assign the role the permissions summarized in the following table.
 1. Create a user on the vCenter server. Assign the role to the user.
 
-Task | Role/Permissions | Details
+| Task | Role/Permissions | Details |
 --- | --- | ---
 VM discovery | At least a read-only user<br/><br/> Data Center object > Propagate to Child Object, role=Read-only | User is assigned at the datacenter level and has access to all the objects in the datacenter.<br/><br/> To restrict access, assign the **No access** role with the **Propagate to child** object to the child objects (vSphere hosts, datastores, VMs, and networks).
 Full replication, failover, failback |  Create a role (Azure_Site_Recovery) with the required permissions, and then assign the role to a VMware user or group<br/><br/> Data Center object > Propagate to Child Object, role=Azure_Site_Recovery<br/><br/> Datastore > Allocate space, browse datastore, low-level file operations, remove file, update virtual machine files<br/><br/> Network > Network assign<br/><br/> Resource > Assign VM to resource pool, migrate powered off VM, migrate powered on VM<br/><br/> Scheduled Tasks > Create task, update task<br/><br/> Virtual machine > Configuration<br/><br/> Virtual machine > Interact > answer question, device connection, configure CD media, configure floppy media, power off, power on, VMware tools install<br/><br/> Virtual machine > Inventory > Create, register, unregister<br/><br/> Virtual machine > Provisioning > Allow virtual machine download, allow virtual machine files upload<br/><br/> Virtual machine > Snapshots > Remove snapshots | User is assigned at the datacenter level and has access to all the objects in the datacenter.<br/><br/> To restrict access, assign the **No access** role with the **Propagate to child** object to the child objects (vSphere hosts, datastores, VMs, and networks).
@@ -75,7 +75,6 @@ Make sure that the VMware vCenter server and VMs comply with requirements:
 * Verify that the Azure VMware Solution VMs that you replicate to Azure comply with [Azure VM requirements](vmware-physical-azure-support-matrix.md#azure-vm-requirements).
 * For Linux VMs, ensure that no two devices or mount points have the same names. These names must be unique and aren't case-sensitive. For example, you can't name two devices for the same VM as *device1* and *Device1*.
 
-
 ## Prepare to connect to Azure VMs after failover
 
 After failover, you might want to connect to the Azure VMs from your Azure VMware Solution network.

articles/site-recovery/avs-tutorial-prepare-azure.md

@@ -5,7 +5,7 @@ services: site-recovery
 author: Jeronika-MS
 ms.service: azure-site-recovery
 ms.topic: tutorial
-ms.date: 02/11/2026
+ms.date: 02/12/2026
 ms.author: v-gajeronika
 ms.reviewer: v-gajeronika
 ms.custom:
@@ -60,7 +60,7 @@ To complete these tasks, your account should be assigned the Virtual Machine Con
 1. Select **Backup and Site Recovery** from the search results. Then, select **Create**.
 1. On **Create Recovery Services vault**, on the **Basics** tab, do the following:
 
-    1. For **Subscription**, select the subscription in which you want to create the Recovery Services vault.
+    1. For **Subscription**, select the subscription where you want to create the Recovery Services vault.
     1. For **Resource group**, select an existing resource group or create a new one. For example, create one named **contosoRG**.
     1. For **Vault name**, enter a friendly name to identify the vault. For example, enter **ContosoVMVault**.
     1. For **Region**, select the region where the vault should be located. For example, select **West Europe**.
@@ -81,7 +81,7 @@ Azure VMware Solution VMs replicate to Azure managed disks. When failover occurs
 
 1. In the [Azure portal](https://portal.azure.com), select **Create a resource**.
 1. Under **Categories**, select **Networking** > **Virtual network**.
-1. On the **Create virtual network** page, on the **Basics** tab, do the following:
+1. On the **Create virtual network** page, on the **Basics** tab, complete the following steps:
     1. For **Subscription**, select the subscription in which to create the network.
     1. For **Resource group**, select the resource group in which to create the network. For this tutorial, use the existing resource group **contosoRG**.
     1. For **Virtual network name**, enter a network name. The name must be unique within the Azure resource group. For example, enter **ContosoASRnet**.

articles/site-recovery/avs-tutorial-reprotect.md

@@ -4,7 +4,7 @@ description: Learn how to reprotect Azure VMware Solution VMs after failover to
 author: Jeronika-MS
 ms.service: azure-site-recovery
 ms.topic: tutorial
-ms.date: 09/30/2020
+ms.date: 02/12/2026
 ms.author: v-gajeronika
 ms.custom: MVC
 # Customer intent: As an IT administrator managing virtual machines, I want to reprotect Azure VMware Solution VMs after failover, so that I can ensure data consistency and maintain disaster recovery capabilities in my cloud environment.
@@ -20,7 +20,7 @@ After [failover](avs-tutorial-failover.md) of Azure VMware Solution VMs to Azure
 2. Make sure that the Azure VMware Solution private cloud configuration server is running and connected to Azure. During failback, the VM must exist in the configuration server database. Otherwise, failback is unsuccessful.
 3. Delete any snapshots on the Azure VMware Solution private cloud master target server. Reprotection won't work if there are snapshots.  The snapshots on the VM are automatically merged during a reprotect job.
 4. If you're reprotecting VMs gathered into a replication group for multi-VM consistency, make sure they all have the same operating system (Windows or Linux) and make sure that the master target server you deploy has the same type of operating system. All VMs in a replication group must use the same master target server.
-5. Open [the required ports](vmware-azure-prepare-failback.md#ports-for-reprotectionfailback) for failback.
+5. Open [the required ports](vmware-azure-prepare-failback.md#ports-for-reprotection-and-failback) for failback.
 6. Ensure that the vCenter Server is connected before failback. Otherwise, disconnecting disks and attaching them back to the virtual machine fails.
 7. If a vCenter Server manages the VMs to which you'll fail back, make sure that you have the required permissions. If you perform a read-only user vCenter Server discovery and protect virtual machines, protection succeeds, and failover works. However, during reprotection, failover is unsuccessful because the datastores can't be discovered, and aren't listed during reprotection. To resolve this problem, you can update the vCenter Server credentials with an [appropriate account/permissions](avs-tutorial-prepare-avs.md#prepare-an-account-for-automatic-discovery), and then retry the job. 
 8. If you used a template to create your virtual machines, ensure that each VM has its own UUID for the disks. If the Azure VMware Solution VM UUID clashes with the UUID of the master target server because both were created from the same template, reprotection fails. Deploy from a different template.

articles/site-recovery/azure-to-azure-how-to-enable-policy.md

@@ -5,7 +5,7 @@ author: Jeronika-MS
 ms.author: v-gajeronika
 ms.reviewer: v-gajeronika
 ms.topic: how-to
-ms.date: 02/11/2026
+ms.date: 02/12/2026
 ms.service: azure-site-recovery
 ms.custom: template-how-to
 

articles/site-recovery/azure-to-azure-how-to-enable-replication-s2d-vms.md

@@ -5,7 +5,7 @@ ms.author: v-gajeronika
 ms.reviewer: v-gajeronika
 author: Jeronika-MS
 ms.topic: how-to
-ms.date: 02/11/2026
+ms.date: 02/12/2026
 ms.service: azure-site-recovery
 
 # Customer intent: As a cloud administrator managing critical applications, I want to set up disaster recovery for Azure virtual machines using replication, so that I can ensure high availability and quick recovery in case of regional failures.

articles/site-recovery/azure-to-azure-move-overview.md

@@ -4,7 +4,7 @@ description: Using Azure Site Recovery to move Azure VMs from one Azure region t
 author: Jeronika-MS
 ms.service: azure-site-recovery
 ms.topic: tutorial
-ms.date: 02/11/2026
+ms.date: 02/12/2026
 ms.author: v-gajeronika
 ms.reviewer: v-gajeronika
 ms.custom: MVC, engagement-fy23

articles/site-recovery/azure-to-azure-network-mapping.md

@@ -4,7 +4,7 @@ description: Learn about mapping virtual networks between two Azure regions for
 author: Jeronika-MS
 ms.service: azure-site-recovery
 ms.topic: how-to
-ms.date: 02/11/2026
+ms.date: 02/12/2026
 ms.author: v-gajeronika
 ms.reviewer: v-gajeronika
 ms.custom:
@@ -85,8 +85,6 @@ The same configuration applies to the Secondary IP Configurations.
 Same address space | Use the IP address of the source virtual machine NIC as the target virtual machine NIC IP address.<br/><br/> If the address isn't available, use the next available IP address.
 Different address space | Use the next available IP address in the target subnet as the target virtual machine NIC address.
 
-
-
 ## IP address assignment during test failover
 
 **Target network** | **Details**