EEE 2312 tasks

Author: Ankita Dutta

articles/site-recovery/azure-to-azure-common-questions.md

@@ -3,7 +3,7 @@ title: Common questions about Azure virtual machine disaster recovery with Azure
 description: This article answers common questions about Azure virtual machine disaster recovery when you use Azure Site Recovery.
 ms.author: ankitadutta
 author: ankitaduttaMSFT
-ms.date: 11/25/2024
+ms.date: 12/23/2024
 ms.topic: faq
 ms.service: azure-site-recovery
 
@@ -295,6 +295,12 @@ You can start failover. Site Recovery doesn't need connectivity from the primary
 
 Site Recovery has an RTO SLA of [one hours](https://azure.microsoft.com/support/legal/sla/site-recovery/v1_2/). Most of the time, Site Recovery fails over virtual machines within minutes. To calculate the RTO, review the failover job, which shows the time it took to bring up a virtual machine.
 
+### Are the extensions replicated to failover VM in target region? 
+
+Extensions aren't replicated to the failover VM in the target region, so we need to install them manually after failover.
+
+**For SQL VM zonal replication:** In the case of a SQL VM, it'll not be shown if we don't have the corresponding IaaS SQL Extension installed. After installing the `SqlIaasExtension`, the `SQL virtual machine` is created automatically. [Learn more](https://learn.microsoft.com/azure/azure-sql/virtual-machines/windows/sql-agent-extension-manually-register-single-vm?view=azuresql&tabs=azure-powershell#register-with-extension).
+
 ## Recovery plans
 
 ### What's a recovery plan?
@@ -352,6 +358,12 @@ While Site Recovery makes a best effort to ensure that capacity is available in
 
 Yes, you can purchase [reserved Azure virtual machines](https://azure.microsoft.com/pricing/reserved-vm-instances/) in the disaster recovery region, and Site Recovery failover operations use them. No additional configuration is needed.
 
+### Where do we see the VM mapping to the reservation group when we enable capacity reservation for our VMs in ASR on the target region?
+
+When we enable capacity reservation for our VMs in Azure Site Recovery on the target region, the VM maps to the reservation group during replication. Since the target VM is not created until a test failover or actual failover is performed, we see the mapping under *Recovery Services Vault* > **Compute** > **Capacity Reservation** settings.
+
+The VM associated option under the capacity reservation group populates only when the target VMs are created during a test failover or actual failover. [Learn more](https://learn.microsoft.com/azure/virtual-machines/capacity-reservation-overview#capacity-reservation-lifecycle).
+
 ## Security
 
 ### Is replication data sent to the Site Recovery service?

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

@@ -5,15 +5,12 @@ author: ankitaduttaMSFT
 ms.author: ankitadutta
 ms.service: azure-site-recovery
 ms.topic: how-to
-ms.date: 09/03/2024
+ms.date: 12/23/2024
 ms.custom: references_regions, subject-rbac-steps, engagement-fy23
 ---
 # Replicate machines with private endpoints
 
-Azure Site Recovery allows you to use
-[Azure Private Link](../private-link/private-endpoint-overview.md) private endpoints for replicating
-your machines from inside an isolated virtual network. Private endpoint access to
-a recovery vault is supported in all Azure Commercial & Government regions.
+Azure Site Recovery allows you to use [Azure Private Link](../private-link/private-endpoint-overview.md) private endpoints for replicating your machines from inside an isolated virtual network. Private endpoint access to a recovery vault is supported in all Azure Commercial & Government regions.
 
 This article provides instructions for you to perform the following steps:
 
@@ -27,7 +24,7 @@ This article provides instructions for you to perform the following steps:
   access for storage as needed. Creation of a private endpoint for accessing storage isn't mandatory
   for Azure Site Recovery.
 
-Below is a reference architecture on how the replication workflow changes with private endpoints.
+Following is a reference architecture on how the replication workflow changes with private endpoints.
 
 :::image type="content" source="./media/azure-to-azure-how-to-enable-replication-private-endpoints/architecture.png" alt-text="Reference architecture for Site Recovery with private endpoints.":::
 
@@ -44,7 +41,7 @@ Below is a reference architecture on how the replication workflow changes with p
   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 seven IP addresses are required** in the subnets of both your source machines and your
+- **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.

articles/site-recovery/azure-to-azure-how-to-enable-zone-to-zone-disaster-recovery.md

@@ -43,7 +43,7 @@ Learn more about [Azure regions with availability zones](../reliability/availabi
 > [!NOTE]
 > Zone-to-zone disaster recovery isn't supported for VMs that have managed disks via zone-redundant storage (ZRS).
 >
->Regions that don't support Azure availability zones also don't support Azure Site Recovery zone-to-zone replication. For Azure Site Recovery zone-to-zone replication to work, the region must support availability zones.
+> Regions that don't support Azure availability zones also don't support Azure Site Recovery zone-to-zone replication. For Azure Site Recovery zone-to-zone replication to work, the region must support availability zones.
 
 ## Using availability zones for disaster recovery
 

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

@@ -104,11 +104,7 @@ Let's take the example from the following screenshot, where Enable Replication f
 
    :::image type="content" source="./media/site-recovery-how-to-reprotect-azure-to-azure/estimated-reprotection.png" alt-text="Screenshot displays example duration of reprotection of a virtual machine on the Azure portal." lightbox="./media/site-recovery-how-to-reprotect-azure-to-azure/estimated-reprotection.png":::
 
-The above is a simple illustration of how to estimate the reprotection time. 
-
-When the virtual machine is re-protected from disaster recovery region to primary region (that is, after failing over from the primary region to disaster recovery region), the target virtual machine (original source virtual machine), and associated NIC(s) are deleted.
-
-However, when the virtual machine is re-protected again from the primary region to disaster recovery region after failback, we do not delete the virtual machine and associated NIC(s) in the disaster recovery region that were created during the earlier failover.
+The above is a simple illustration of how to estimate the reprotection time. When customer failover to target region and reprotect, the source virtual machine and associated resources are **not deleted**. When customer *failback* to primary region and reprotect, the VM (in the target / disaster recovery region) and associated resources are then deleted. 
 
 ## Next steps