Merge pull request #304825 from mmkiran21-git/16441660

v-ccolin · web-flow · commit 7f41c9ce3c5f · 2025-08-28T20:58:15.000+01:00
16441660 changes made
diff --git a/articles/migrate/how-to-create-group-machine-dependencies-agentless.md b/articles/migrate/how-to-create-group-machine-dependencies-agentless.md
@@ -319,7 +319,7 @@ Follow the steps to disable the servers where dependency analysis is autoenabled
 
 1. You can filter servers to disable dependency analysis on those that were autoenabled (servers with the status as *Enabled*). Servers that aren't eligible for disablement—such as those with the status *Validation failed*, *Not initiated*, *Disabled*, or *Credentials* not available'—can't be selected.
 
-    :::image type="content" source="./media/how-to-create-group-machine-dependencies-agentless/disable-dependencies-view.png" alt-text="The screenshot shows disable dependencies view." lightbox="./media/how-to-create-group-machine-dependencies-agentless/disable-dependencies-view.png":::
+:::image type="content" source="./media/how-to-create-group-machine-dependencies-agentless/disable-dependencies-view.png" alt-text="The screenshot shows disable dependencies view." lightbox="./media/how-to-create-group-machine-dependencies-agentless/disable-dependencies-view.png":::
 
 1. You can select the servers and select **Disable** to proceed.
 
@@ -336,8 +336,7 @@ Follow the steps to disable the servers where dependency analysis has been autoe
 
 1. You can filter servers to disable dependency analysis on those that were autoenabled (servers with the status as *Enabled*). Servers that aren't eligible for disablement—such as those with the status *Validation failed*, *Not initiated*, *Disabled*, or *Credentials* not available'—can't be selected.
 
-    :::image type="content" source="./media/how-to-create-group-machine-dependencies-agentless/enable-dependencies-view.png" alt-text="The screenshot shows the enable dependenies view." lightbox="./media/how-to-create-group-machine-dependencies-agentless/enable-dependencies-view.png":::
-
+:::image type="content" source="./media/how-to-create-group-machine-dependencies-agentless/enable-dependencies-view.png" alt-text="The screenshot shows the enable dependencies view." lightbox="./media/how-to-create-group-machine-dependencies-agentless/enable-dependencies-view.png":::
 
 1. You can select the servers and select **Enable** to proceed.
 
diff --git a/articles/site-recovery/azure-to-azure-common-questions.md b/articles/site-recovery/azure-to-azure-common-questions.md
@@ -138,6 +138,10 @@ The Azure portal displays *logical Zones*. In the datacenter, actual physical zo
 
 In case the source and target zones are the same, you can't view zone for target configuration while enabling zonal replication.
 
+#### Can I select a different automation name than the existing automation name for my recovery services vault? 
+
+When you replicate a new virtual machine (VM) and assign a new automation account, this account is automatically set at the vault level and will appear under Recovery Services Vault > Site Recovery Infrastructure > Extension Update Settings in the Azure portal. From that point onward, Azure Site Recovery will use this new Automation Account to manage the Site Recovery extension for all replicated VMs.
+
 #### Can I choose a different name for my recovery services vault automation instead of using the existing one?
 
 When you replicate a new VM and specify a new Automation Account name, the vault updates to use this new Automation Account at the vault level. This updated name appears in the vault under **Recovery Services Vault** > **Site Recovery Infrastructure** > **Extension Update Settings**.
@@ -160,7 +164,7 @@ Azure Site Recovery supports live resync. Once resize is completed, resync of Re
  
 #### Are there any changes in performance of Azure Site Recovery between Premium SSD v1 and SSD v2 disks?
 
-The RPO and RTO SLAs of Azure Site Recovery remain the same for both disk types. However, Premium SSD v2 disks takes more time to complete the enable protection process. Also, as Azure Site Recovery uses Premium SSD v1 disks as replica disks, during failover, the new Premium SSD v2 disks created in target using the replica disk, would need some time for data hydration. However, this would not impact the environment availability.
+The RPO and RTO SLAs of Azure Site Recovery remain the same for both disk types. However, Premium SSD v2 disks take more time to complete the enable protection process. Also, as Azure Site Recovery uses Premium SSD v1 disks as replica disks, during failover, the new Premium SSD v2 disks created in target using the replica disk, would need some time for data hydration. However, this would not impact the environment availability.
  
 #### What snapshots are used when protecting VMs with Premium SSD v2 using Azure Site Recovery?
 
diff --git a/articles/site-recovery/azure-to-azure-how-to-enable-replication-ade-vms.md b/articles/site-recovery/azure-to-azure-how-to-enable-replication-ade-vms.md
@@ -4,7 +4,7 @@ description: This article describes how to configure replication for Azure Disk
 author: jyothisuri
 ms.service: azure-site-recovery
 ms.topic: how-to
-ms.date: 10/29/2024
+ms.date: 08/28/2024
 ms.author: jsuri
 
 # Customer intent: As a cloud administrator, I want to configure replication for encrypted Azure VMs to another region, so that I can ensure disaster recovery and maintain data security across regions.
diff --git a/articles/site-recovery/azure-to-azure-support-matrix.md b/articles/site-recovery/azure-to-azure-support-matrix.md
@@ -434,7 +434,7 @@ General purpose V2 storage accounts (Both Hot and Cool tier) | Supported | Trans
 Generation 2 (UEFI boot) | Supported
 NVMe disks | Not supported
 Managed Shared Disk| Supported 
-Managed Premium SSD v2 Disk| Supported | Public Preview  in all public regions.<br/><br/>Note: Since Block Blob storage accounts are not supported in China North and China East regions, Azure Site Recovery for Premium SSD v2 disks cannot be supported. 
+Managed Premium SSD v2 Disk| Supported | Public Preview with PowerShell support in all public regions.<br/><br/>Note: Since Block Blob storage accounts are not supported in China North and China East regions, Azure Site Recovery for Premium SSD v2 disks cannot be supported. 
 Ultra Disks | Supported | Public Preview  in all public regions.<br/><br/>Note: Since Block Blob storage accounts are not supported in China North and China East regions, Azure Site Recovery for Premium SSD v2 disks cannot be supported.
 Secure transfer option | Supported
 Write accelerator enabled disks | Not supported
diff --git a/articles/site-recovery/site-recovery-role-based-linked-access-control.md b/articles/site-recovery/site-recovery-role-based-linked-access-control.md
@@ -2,7 +2,7 @@
 title: Manage Azure role-based access control in Azure Site Recovery
 description: This article describes how to apply Azure role-based access control (Azure RBAC) to manage Azure Site Recovery access.
 ms.service: azure-site-recovery
-ms.date: 12/28/2024
+ms.date: 07/21/2025
 author: jyothisuri
 ms.topic: overview
 ms.author: jsuri
