edits

Author: Ankita Dutta

articles/site-recovery/azure-to-azure-architecture.md

@@ -3,7 +3,7 @@ title: Azure to Azure disaster recovery architecture in Azure Site Recovery
 description: Overview of the architecture used when you set up disaster recovery between Azure regions for Azure VMs, using the Azure Site Recovery service.
 ms.service: azure-site-recovery
 ms.topic: concept-article
-ms.date: 12/28/2024
+ms.date: 03/17/2025
 ms.author: ankitadutta
 author: ankitaduttaMSFT
 ---
@@ -37,7 +37,7 @@ When you enable replication for a VM, Site Recovery gives you the option of crea
 **Target resource group** | The resource group to which VMs belong after failover.<br/><br/> It can be in any Azure region except the source region.<br/><br/> Site Recovery creates a new resource group in the target region, with an "asr" suffix.
 **Target VNet** | The virtual network (VNet) in which replicated VMs are located after failover. A network mapping is created between source and target virtual networks, and vice versa.<br/><br/> Site Recovery creates a new VNet and subnet, with the "asr" suffix.
 **Target storage account** |  If the VM doesn't use a managed disk, this is the storage account to which data is replicated.<br/><br/> Site Recovery creates a new storage account in the target region, to mirror the source storage account.
-**Replica managed disks** | If the VM uses a managed disk, this is the managed disks to which data is replicated.<br/><br/> Site Recovery creates replica managed disks in the storage region to mirror the source.
+**Replica managed disks** | If the VM uses a managed disk, a copy of the original disk is created with an `-ASRReplica` suffix. The copies created are used for replication. <br> This `-ASRReplica` disk's **Disk state** should be *ActiveSAS* which automatically creates a tag with `ASR-ReplicaDisk` prefix. 
 **Target availability sets** |  Availability set in which replicating VMs are located after failover.<br/><br/> Site Recovery creates an availability set in the target region with the suffix "asr", for VMs that are located in an availability set in the source location. If an availability set exists, it's used and a new one isn't created.
 **Target availability zones** | If the target region supports availability zones, Site Recovery assigns the same zone number as that used in the source region.
 

articles/site-recovery/azure-to-azure-how-to-reprotect.md

@@ -5,7 +5,7 @@ services: site-recovery
 author: ankitaduttaMSFT
 ms.service: azure-site-recovery
 ms.topic: tutorial
-ms.date: 05/23/2024
+ms.date: 03/17/2025
 ms.author: ankitadutta
 ---
 
@@ -58,6 +58,12 @@ By default, the following occurs:
 1. Temporary replicas of the source disks (disks attached to the virtual machines in secondary region) are created with the name `ms-asr-<GUID>`, that are used to transfer / read data. The temp disks let us utilize the complete bandwidth of the disk instead of only 16% bandwidth of the original disks (that are connected to the virtual machine). The temp disks are deleted once the reprotection completes.
 1. If the target availability set doesn't exist, a new one is created as part of the reprotect job if necessary. If you've customized the reprotection settings, then the selected set is used.
 
+> [!NOTE]
+> After re-protecting virtual machines in the secondary region, Azure Site Recovery locks the source machine as Read-only. It applies the lock to prevent deletion during reprotection and replication from the failed-over VM back to the source machine. 
+>
+> The lock remains until the failback to the source region completes. This Read-only lock name follows this naming convention: ```SiteRecovery-<Recovery Services vault's resource ID>-<Vault's name>-<Vault's location>```.
+
+
 **When you trigger a reprotect job, and the target virtual machine exists, the following occurs:**
 
 1. The target side virtual machine is turned off if it's running.

articles/site-recovery/site-recovery-runbook-automation.md

@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
 ms.service: azure-site-recovery
 ms.topic: concept-article
 ms.author: ankitadutta
-ms.date: 03/07/2024
+ms.date: 03/17/2025
 ---
 
 # Add Azure Automation runbooks to recovery plans
@@ -223,7 +223,7 @@ We do this by specifying multiple values, using Azure PowerShell.
 4. Use this variable in your runbook. If the indicated VM GUID is found in the recovery plan context, apply the NSG on the VM:
 
     ```powershell
-    $VMDetailsObj = (Get-AutomationVariable -Name $RecoveryPlanContext.RecoveryPlanName).ToObject([hashtable])
+    $VMDetailsObj = (Get-AzAutomationVariable -Name $RecoveryPlanContext.RecoveryPlanName).ToObject([hashtable])
     ```
 
 4. In your runbook, loop through the VMs of the recovery plan context. Check whether the VM exists in **$VMDetailsObj**. If it exists, access the properties of the variable to apply the NSG: