Merge pull request #312707 from swapnilbel/main

Update managed identity support status in recovery matrix

Author: v-dirichards

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

@@ -72,7 +72,7 @@ Subscription | Can be different from source VMs | Cache storage account must be
 Azure Storage firewalls for virtual networks | Supported | If you use a firewall-enabled cache storage account or a target storage account, ensure that you [allow trusted Microsoft services](../storage/common/storage-network-security.md#exceptions).<br></br>Ensure that you allow access to at least one subnet of the source virtual network.<br></br>If you use user-assigned managed identity (UAMI) created on an Azure Recovery Services vault, don't restrict virtual network access to your storage accounts that are used for Site Recovery. Allow access from all networks if you use vault UAMI.
 Soft delete | Not supported | Soft delete isn't supported because after soft delete is enabled on a cache storage account, it increases cost. Site Recovery performs frequent creates/deletes of log files. Replicating causes costs to increase.
 Encryption at rest | Supported | You can configure storage account encryption with customer-managed keys (CMKs).
-Managed identity | Not supported | The cached storage account must allow shared key access and shared access signatures signed by the shared key. Recent changes in Azure Policy disable key authentication because of security concerns. For Site Recovery, you need to enable it again.
+Managed identity | Supported | Follow [Turn off key based access on cache account](/azure/site-recovery/asr-turn-off-key-authentication-cache).
 
 The following table lists the limits in terms of number of disks that can replicate to a single storage account.