Merge pull request #298610 from ankitaduttaMSFT/2204

edits

Author: v-dirichards

articles/resource-mover/support-matrix-move-region-azure-vm.md

@@ -4,7 +4,7 @@ description: Review support for moving Azure VMs between regions with Azure Reso
 author: ankitaduttaMSFT
 ms.service: azure-resource-mover
 ms.topic: how-to
-ms.date: 12/27/2024
+ms.date: 04/22/2025
 ms.author: ankitadutta
 ms.custom: engagement-fy23, UpdateFrequency.5, linux-related-content
 ---
@@ -17,6 +17,9 @@ This article summarizes support and prerequisites when you move virtual machines
 
 Resource Mover supports Azure VMs running these Windows operating systems.
 
+> [!NOTE]
+> Windows Trusted Launch VMs are supported by Resource Mover. 
+
 **Operating system** | **Details**
 --- | ---
 Windows Server 2019 | Supported for Server Core, Server with Desktop Experience.
@@ -27,16 +30,19 @@ Windows Server 2008 R2 with SP1/SP2 | Supported.<br/><br/> For machines running
 Windows 10 (x64) | Supported.
 Windows 8.1 (x64) | Supported.
 Windows 8 (x64) | Supported.
-Windows 7 (x64) with SP1 onwards | Install a Windows [servicing stack update (SSU)](https://support.microsoft.com/help/4490628) and [SHA-2 update](https://support.microsoft.com/help/4474419) on machines running Windows 7 with SP1.  SHA-1 isn't supported from September 2019, and if SHA-2 code signing isn't enabled the 'prepare' step will not succeed. Learn more about [SHA-2 upgrade and requirements](https://aka.ms/SHA-2KB).
+Windows 7 (x64) with SP1 onwards | Install a Windows [servicing stack update (SSU)](https://support.microsoft.com/help/4490628) and [SHA-2 update](https://support.microsoft.com/help/4474419) on machines running Windows 7 with SP1.  SHA-1 isn't supported from September 2019, and if SHA-2 code signing isn't enabled the 'prepare' step won't succeed. Learn more about [SHA-2 upgrade and requirements](https://aka.ms/SHA-2KB).
 
 
 ## Linux VM support
 
-Resource Move supports Azure VMs running these Linux operating systems.
+Resource Mover supports Azure VMs running these Linux operating systems.
+
+> [!NOTE]
+> Linux Trusted Launch VMs aren't supported by Resource Mover.
 
 **Operating system** | **Details**
 --- | ---
-Red Hat Enterprise Linux | 6.7, 6.8, 6.9, 6.10, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6,[7.7](https://support.microsoft.com/help/4528026/update-rollup-41-for-azure-site-recovery), [8.0](https://support.microsoft.com/help/4531426/update-rollup-42-for-azure-site-recovery), 8.1
+Red Hat Enterprise Linux | 6.7, 6.8, 6.9, 6.10, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6,[7.7](https://support.microsoft.com/help/4528026/update-rollup-41-for-azure-site-recovery), [8.0](https://support.microsoft.com/help/4531426/update-rollup-42-for-azure-site-recovery), 8.1, 9.4
 Ubuntu 14.04 LTS Server | [Supported kernel versions](#supported-ubuntu-kernel-versions)
 Ubuntu 16.04 LTS Server | [Supported kernel version](#supported-ubuntu-kernel-versions)<br/><br/> Ubuntu servers using password-based authentication and sign-in, and the cloud-init package to configure cloud VMs, might have password-based sign-in disabled on failover (depending on the cloud-init configuration). Password-based sign-in can be reenabled on the virtual machine by resetting the password from the Support > Troubleshooting > Settings menu (of the failed over VM in the Azure portal.
 Ubuntu 18.04 LTS Server | [Supported kernel version](#supported-ubuntu-kernel-versions).
@@ -106,7 +112,7 @@ Extensions | Not supported | Extensions aren't copied over to the  VM in target
 This table summarized support for the Azure VM OS disk, data disk, and temporary disk. It's important to observe the VM disk limits and targets for [managed disks](/azure/virtual-machines/disks-scalability-targets) to avoid any performance issues.
 
 > [!NOTE]
-> The target VM size should be equal to or larger than the source VM. The parameters used for validation are: Data Disks Count, NICs count, Available CPUs, Memory in GB. If it sn't a error is issued.
+> The target VM size should be equal to or larger than the source VM. The parameters used for validation are: Data Disks Count, NICs count, Available CPUs, Memory in GB. If it isn't, an error is issued.
 
 
 **Component** | **Support** | **Details**
@@ -152,7 +158,7 @@ Network security group | Supported | Specify an existing resource in the target
 Reserved (static) IP address | Supported | You can't currently configure this. The value defaults to the source value. <br/><br/> If the NIC on the source VM has a static IP address, and the target subnet has the same IP address available, it's assigned to the target VM.<br/><br/> If the target subnet doesn't have the same IP address available, the initiate move for the VM will fail.
 Dynamic IP address | Supported | You can't currently configure this. The value defaults to the source value.<br/><br/> If the NIC on the source has dynamic IP addressing, the NIC on the target VM is also dynamic by default.
 IP configurations | Supported | You can't currently configure this. The value defaults to the source value.
-VNET Peering | Not Retained | The VNET which is moved to the target region will not retain its VNET peering configuration present in the source region. To retain the peering, it needs to do be done again manually in the target region.
+VNET Peering | Not Retained | The VNET which is moved to the target region won't retain its VNET peering configuration present in the source region. To retain the peering, it needs to do be done again manually in the target region.
 
 ## Outbound access requirements
 

articles/site-recovery/shared-disks-common-questions.md

@@ -4,7 +4,7 @@ description: This article answers common questions about Azure to Azure Shared d
 ms.author: ankitadutta
 author: ankitaduttaMSFT
 ms.topic: faq
-ms.date: 04/02/2025
+ms.date: 04/22/2025
 ms.service: azure-site-recovery
 
 ---
@@ -18,7 +18,7 @@ This article answers common questions about using shared disks (Azure to Azure)
 No, Azure Site Recovery does not support Linux VMs with shared disks. Only VMs with WSFC-based shared disks are supported.
 
 #### Is PowerShell supported for Azure Site Recovery with shared disks?
-No, PowerShell support for shared disks is currently unavailable.
+Yes, it is supported.
 
 #### Can we enable replication for only some of the VMs attached to a shared disk?
 No, enable replication can only be enabled successfully when all the VMs attached to a shared disk are selected.
@@ -32,14 +32,12 @@ Yes, you can restart the job without reselecting clusters, just like other A2A s
 #### Can new shared disks be added to a protected cluster?
 No, if new shared disks need to be added, disable the replication for the already protected cluster. Enable a new cluster protection with a new cluster name for the modified infrastructure.
 
-#### Can we select both crash-consistent and app-consistent recovery points?
-Yes, both types of recovery points are generated. App-consistent recovery points and Latest recovery point will be available as part of General Availability.
+#### Are both crash-consistent and app-consistent recovery points supported?
+No, Azure Site Recovery for Shared Disks supports only Crash consistent recovery points.
 
 #### Can we use recovery plans to failover Azure Site Recovery enabled VMs with shared disks?
 No, recovery plans are not supported for shared disks in Azure Site Recovery.
 
-#### Why is there no health status for VMs with shared disks in the monitoring plane, whether test failover is completed or not?
-The health status warning due to test failover will be available as part of General Availability.
 
 ## Next steps
 

articles/site-recovery/site-recovery-cost.md

@@ -3,7 +3,7 @@ title: Understanding Azure Site Recovery for Managed Disks Charges
 description: This article summarizes the costs disaster recovery and migration deployment scenarios.
 ms.topic: overview
 ms.service: azure-site-recovery
-ms.date: 01/21/2025
+ms.date: 04/22/2025
 ms.author: ankitadutta
 author: ankitaduttaMSFT
 ---
@@ -46,7 +46,7 @@ Network egress costs, also known as outbound data transfer charges, occur when r
 This cost includes:
 
 - **Source**:
-  - For Pv1 disks, incremental snapshots are charged.
+  - For Standard and Pv1 disks, incremental snapshots are charged.
   - For Pv2 disks, one full snapshot followed by incremental snapshots is charged. 
 - **Target**:
   - Snapshot costs are associated with the recovery points created by Azure Site Recovery. These snapshots capture the replica storage at a point in time and are charged based on the consumed capacity. Pricing details align with Page Blob Snapshots. [Learn more](https://azure.microsoft.com/pricing/details/storage/page-blobs/#:~:text=Note%3A%20Snapshots%20are%20charged,at%20%240.12%20%2FGB%20per%20month.?msockid=3816c7206e2268e7035dd3316f7069f4).