Merge pull request #289383 from ankitaduttaMSFT/asrdoc1

asr doc updates

Author: PMEds28

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

@@ -86,6 +86,10 @@ This isn't supported.
 
 Support for this is limited to a few regions. [Learn more](azure-to-azure-how-to-enable-zone-to-zone-disaster-recovery.md).
 
+### Can we replicate from one Zone to non-zone with Azure Site Recovery?
+
+Yes, this is supported.
+
 ### Can I exclude disks from replication?
 
 Yes, you can exclude disks when you set up replication, using PowerShell. [Learn more](azure-to-azure-exclude-disks.md) about excluding disks.

articles/site-recovery/azure-to-azure-how-to-enable-replication-ade-vms.md

@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
 manager: gaggupta
 ms.service: azure-site-recovery
 ms.topic: how-to
-ms.date: 05/06/2024
+ms.date: 10/29/2024
 ms.author: ankitadutta
 
 ---
@@ -70,6 +70,9 @@ To troubleshoot permissions, refer to [key vault permission issues](#trusted-roo
 
    By default, Site Recovery creates a new key vault in the target region. The vault's name has an "asr" suffix that's based on the source VM disk encryption keys. If a key vault already exists that was created by Site Recovery, it's reused. Select a different key vault from the list if necessary.
 
+> [!NOTE]
+> Alternatively, you can download the key, import it in the secondary key vault region. You can then modify your replicas disks to use the keys.
+
 ## Enable replication
 
 Use the following procedure to replicate Azure Disk Encryption-enabled VMs to another Azure region. As an example, primary Azure region is East Asia, and the secondary is Southeast Asia.

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

@@ -82,6 +82,8 @@ As average churn on the disks increases, the number of disks that a storage acco
 > The cache limits are specific to Azure-to-Azure and Zone-to-Zone DR scenarios.
 >
 > When you enable replication via the virtual machine workflow for cross subscription, the portal only lists the cache storage account from the source subscription, but doesn't list any storage account created in the target subscription. To set up this scenario, use [PowerShell](azure-to-azure-powershell.md).
+>
+> Azure Site Recovery isn't supported for VMs with Premium SSD v2 disks.
 
 
 

articles/site-recovery/report-site-recovery.md

@@ -33,7 +33,7 @@ To start using Azure Site Recovery reports, follow these steps:
 
 ### Create a Log Analytics workspace or use an existing workspace
 
-Set up one or more Log Analytics workspaces to store your Backup reporting data. The location and subscription of this Log Analytics workspace, can be different from where your vaults are located or subscribed. 
+Set up one or more Log Analytics workspaces to store your Backup reporting data. The location and subscription of this Log Analytics workspace can be different from where your vaults are located or subscribed. 
 
 To set up a Log Analytics workspace, [follow these steps](/azure/azure-monitor/logs/quick-create-workspace). The data in a Log Analytics workspace is kept for 30 days by default. If you want to see data for a longer time span, change the retention period of the Log Analytics workspace. To change the retention period, see [Configure data retention and archive policies in Azure Monitor Logs](/azure/azure-monitor/logs/data-retention-configure). 
 
@@ -48,7 +48,7 @@ You can also configure diagnostics settings for your vaults using the following
 
 1. Navigate to the chosen the Recovery Services vault, then select **Monitoring** > **Diagnostic settings**.
 1. Specify the target for the Recovery Services Vault's diagnostic data. Learn more about [using diagnostic events](../backup/backup-azure-diagnostic-events.md) for Recovery Services vaults.
-1. Select **Azure Site Recovery Jobs** and **Azure Site Recovery Replicated Item Details** options to populate the reports. 
+1. Select **Azure Site Recovery Jobs** and **Azure Site Recovery Replicated Item Details**, and on the **Destination** table **Resource Specific** options to populate the reports. 
     :::image type="content" source="./media/report-site-recovery/logs.png" alt-text="Screenshot of logs options.":::
 
     > [!NOTE]
@@ -120,4 +120,4 @@ Additionally, the V1 schema for sending diagnostics data to a storage account or
 
 ## Next steps
 
-- [Diagnostics in Backup and Site Recovery](../backup/backup-azure-diagnostic-events.md)
+- [Diagnostics in Backup and Site Recovery](../backup/backup-azure-diagnostic-events.md)

articles/site-recovery/site-recovery-faq.yml

@@ -161,7 +161,7 @@ sections:
               >The modernized experience uses TLS 1.2 for all the communication and enforces it by default. 
 
       - question: |
-         How can I enforce TLS 1.2 on HyperV-to-Azure Site Recovery scenarios?
+         How can I enforce TLS 1.2 on Hyper-V-to-Azure Site Recovery scenarios?
         answer: |
              All communication between the microservices of Azure Site Recovery happens on TLS 1.2 protocol. Site Recovery uses security providers configured in the system (OS) and uses the latest available TLS protocol. One needs to explicitly enable the TLS 1.2 in the Registry and then Site Recovery will start using TLS 1.2 for communication with services.
 
@@ -180,6 +180,10 @@ sections:
                 - [Classic Storage Account Contributor](../role-based-access-control/built-in-roles.md#classic-storage-account-contributor)
                 - [Classic Storage Account Key Operator Service Role](../role-based-access-control/built-in-roles.md#classic-storage-account-key-operator-service-role)
 
+               Cache storage account is not supported for managed identity.
+
+
+
       - question: |
          Can Azure Site Recovery track source virtual machine changes outside the Source OS?
         answer: |