Merge pull request #264788 from ankitaduttaMSFT/cahanges

owner

Author: prmerger-automator[bot]

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

@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
 manager: gaggupta
 ms.service: site-recovery
 ms.topic: how-to
-ms.date: 01/23/2024
+ms.date: 01/31/2024
 ms.author: ankitadutta
 
 ---

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: 07/14/2023
+ms.date: 01/31/2024
 ms.author: ankitadutta
 ---
 

articles/site-recovery/how-to-migrate-run-as-accounts-managed-identity.md

@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
 ms.service: site-recovery
 ms.author: ankitadutta
 ms.topic: how-to 
-ms.date: 09/14/2023
+ms.date: 01/31/2024
 ---
 
 # Migrate from a Run As account to Managed Identities 
@@ -20,7 +20,7 @@ On Azure, managed identities eliminate the need for developers having to manage
 
 ## Prerequisites
 
-Before you migrate from a Run As account to a managed identity, ensure that you have the appropriate roles to create a system-assigned identity for your automation account and to assign it the Contributor role in the corresponding recovery services vault.
+Before you migrate from a Run As account to a managed identity, ensure that you have the appropriate roles to create a system-assigned identity for your automation account and to assign it the *Owner* role in the corresponding recovery services vault.
 
 ## Benefits of managed identities