Merge pull request #297297 from ankitaduttaMSFT/1803a

PBI 24846254, 24834774, 16426451

Author: prmerger-automator[bot]

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

@@ -96,13 +96,14 @@ Yes, you can exclude disks when you set up replication, using PowerShell. [Learn
 
 ### Can I replicate new disks added to replicated virtual machines?
 
-For replicated virtual machines with managed disks, you can add new disks, and enable replication for them. When you add a new disk, the replicated virtual machine shows a warning message that one or more disks on the virtual machine are available for protection.
+For replicated virtual machines with managed disks, you can add new disks, and enable replication for them. When you add a new disk, the replicated virtual machine shows a warning message that one or more disks on the virtual machine are available for protection. 
 
-- If you enable replication for the added disks, the warning disappears after the initial replication.
+- If you enable replication for the added disks, the warning disappears after the initial replication. 
 - If you don't want to enable replication for the disk, you can dismiss the warning.
-- If you fail over a virtual machine with added disks, replication points show the disks available for recovery. For example, if you add a second disk to a virtual machine with one disk, a replication point created before you added shows as "1 of 2 disks."
+- If you fail over a virtual machine with added disks, replication points show the disks available for recovery. For example, if you add a second disk to a virtual machine with one disk, a replication point created before you added shows as *1 of 2 disks*.
+- If you perform an OS Disk swap, you're required to perform disable and enable replication, since Site Recovery doesn't support swapping the OS disk.
 
-Site Recovery doesn't support "hot remove" of disks from a replicated virtual machine. If you remove a virtual machine disk, you need to disable and then reenable replication for the virtual machine.
+Site Recovery doesn't support *hot remove* of disks from a replicated virtual machine. If you remove a virtual machine disk, you need to disable and then reenable replication for the virtual machine. 
 
 ### How often can I replicate to Azure?
 

articles/site-recovery/azure-to-azure-troubleshoot-errors.md

@@ -4,7 +4,7 @@ description: Troubleshoot errors when replicating Azure virtual machines for dis
 author: ankitaduttaMSFT
 ms.service: azure-site-recovery
 ms.topic: troubleshooting
-ms.date: 03/07/2024
+ms.date: 03/31/2025
 ms.author: ankitadutta
 ms.custom: engagement-fy23
 ---
@@ -66,6 +66,9 @@ For more information, see [Configure trusted roots and disallowed certificates](
 
 Follow the guidance provided by the distributor of your Linux operating system version to get the latest trusted root certificates and the latest certificate revocation list on the VM.
 
+> [!IMPORTANT]
+> For RedHat Linux machines, add the Ca -Trust certificates to the `/etc/pki/ca-trust/` to avoid certificate errors.
+
 Because SUSE Linux uses symbolic links, or symlinks, to maintain a certificate list, follow these steps:
 
 1. Sign in as a **root** user. The hash symbol (`#`) is the default command prompt.

articles/site-recovery/site-recovery-deployment-planner.md

@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
 ms.service: azure-site-recovery
 ms.topic: concept-article
 ms.author: ankitadutta
-ms.date: 02/05/2025
+ms.date: 03/31/2025
 ---
 
 # About the Azure Site Recovery Deployment Planner for VMware to Azure
@@ -72,7 +72,7 @@ The tool has two main phases: profiling and report generation. There is also a t
 | Server requirement | Description|
 |---|---|
 |Profiling and throughput measurement| <ul><li>Operating system: Windows Server 2016 or Windows Server 2012 R2<br>(ideally matching at least the [size recommendations for the configuration server](/en-in/azure/site-recovery/site-recovery-plan-capacity-vmware#size-recommendations-for-the-configuration-server))</li><li>Machine configuration: 8 vCPUs, 16 GB RAM, 300 GB HDD</li><li>[.NET Framework 4.5](https://aka.ms/dotnet-framework-45)</li><li>[Visual C++ Redistributable for Visual Studio 2012](https://aka.ms/vcplusplus-redistributable)</li><li>Internet access to Azure (`*.blob.core.windows.net`) from this server, port 443<br>[This is optional. You can choose to provide the available bandwidth during Report Generation manually.]</li><li>Azure storage account</li><li>Administrator access on the server</li><li>Minimum 100 GB of free disk space (assuming 1,000 VMs with an average of three disks each, profiled for 30 days)</li><li>VMware vCenter statistics level settings can be 1 or higher level</li><li>Allow vCenter port (default 443): Site Recovery Deployment Planner uses this port to connect to the vCenter server/ESXi host</ul></ul>|
-| Report generation | A Windows PC or Windows Server with Excel 2013 or later.<li>[.NET Framework 4.5](https://aka.ms/dotnet-framework-45)</li><li>[Visual C++ Redistributable for Visual Studio 2012](https://aka.ms/vcplusplus-redistributable)</li> is required only when you pass -User option in the report generation command to fetch the latest VM configuration information of the VMs. The Deployment Planner connects to vCenter server. Allow  vCenter port (default 443) port to connect to vCenter server.</li>|
+| Report generation | A Windows PC or Windows Server with Excel 2013 or later.<li>[.NET Framework 4.5](https://aka.ms/dotnet-framework-45)</li><li>[Visual C++ Redistributable for Visual Studio 2012](https://aka.ms/vcplusplus-redistributable)</li> is required only when you pass -User option in the report generation command to fetch the latest VM configuration information of the VMs. The Deployment Planner connects to vCenter server. Allow  vCenter port (default 443) port to connect to vCenter server.</li> <br> TLS version is supported for Deployment Planner. |
 | User permissions | Read-only permission for the user account that's used to access the VMware vCenter server/VMware vSphere ESXi host during profiling |
 
 > [!NOTE]