Merge pull request #267303 from ankitaduttaMSFT/ad-hoc

Ad hoc

Author: prmerger-automator[bot]

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

@@ -4,7 +4,7 @@ description: This article answers common questions about Azure VM disaster recov
 ms.author: ankitadutta
 author: ankitaduttaMSFT
 manager: rochakm
-ms.date: 10/06/2023
+ms.date: 02/27/2024
 ms.topic: conceptual
 ms.service: site-recovery
 
@@ -76,7 +76,7 @@ Yes, you can replicate VMs in availability zones to another Azure region.
 
 ### Can I replicate non-zone VMs to a zone within the same region?
 
-This isn't supported in the portal. You can use the REST API/PowerShell to do this.
+This isn't supported.
 
 ### Can I replicate zoned VMs to a different zone in the same region?
 

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

@@ -5,7 +5,7 @@ services: site-recovery
 author: ankitaduttaMSFT
 ms.service: site-recovery
 ms.topic: tutorial
-ms.date: 01/31/2024
+ms.date: 02/27/2024
 ms.author: ankitadutta
 ---
 
@@ -81,7 +81,7 @@ By default, the following occurs:
 
 In most cases, Azure Site Recovery doesn't replicate the complete data to the source region. The amount of data replicated depends on the following conditions:
 
-1. If the source VM data is deleted, corrupted, or inaccessible for some reason, such as a resource group change or delete, a complete initial replication will happen during reprotection because there's no data available on the source region to use. In this case, the reprotection time taken will be at least as long as the initial replication time taken from the primary to the disaster recovery location.
+1. Azure Site Recovery doesn't support reprotection if the source virtual machine's data is deleted, corrupted, or inaccessible for some reason. For example, a resource group change or deletion. Alternatively, you can disable the previous disaster recovery protection and enable a new protection from the current region.
 2.	If the source VM data is accessible, then differentials are computed by comparing both the disks and only the differences are transferred. 
    In this case, the **reprotection  time** is greater than or equal to the `checksum calculation time + checksum differentials transfer time + time taken to process the recovery points from Azure Site Recovery agent + auto scale time`.
 

articles/site-recovery/azure-to-azure-support-matrix.md

@@ -356,7 +356,7 @@ SAS key rotation | Not Supported | If the SAS key for storage accounts is rotate
 Host Caching | Supported
 Hot add    | Supported | Enabling replication for a data disk that you add to a replicated Azure VM is supported for VMs that use managed disks. <br/><br/> Only one disk can be hot added to an Azure VM at a time. Parallel addition of multiple disks isn't supported. |
 Hot remove disk    | Not supported | If you  remove data disk on the VM, you need to disable replication and enable replication again for the VM.
-Exclude disk | Support. You must use [PowerShell](azure-to-azure-exclude-disks.md) to configure. |    Temporary disks are excluded by default.
+Exclude disk | Supported. You can use [PowerShell](azure-to-azure-exclude-disks.md) or navigate to **Advanced Setting** > **Storage Settings** > **Disk to Replicate** option from the portal. | Temporary disks are excluded by default.
 Storage Spaces Direct  | Supported for crash consistent recovery points. Application consistent recovery points aren't supported. |
 Scale-out File Server  | Supported for crash consistent recovery points. Application consistent recovery points aren't supported. |
 DRBD | Disks that are part of a DRBD setup aren't supported. |