Merge pull request #273679 from ankitaduttaMSFT/5257

pbi5257

Author: prmerger-automator[bot]

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

@@ -5,13 +5,13 @@ author: ankitaduttaMSFT
 ms.service: site-recovery
 ms.author: ankitadutta
 ms.topic: how-to 
-ms.date: 04/01/2024
+ms.date: 04/29/2024
 ---
 
 # Migrate from a Run As account to Managed Identities 
 
 > [!IMPORTANT]
-> - Azure Automation Run As Account will retire on September 30, 2023 and will be replaced with Managed Identities. Before that date, you'll need to start migrating your runbooks to use managed identities. For more information, see [migrating from an existing Run As accounts to managed identity](../automation/automation-managed-identity-faq.md).
+> - Azure Automation Run As Account was retired on September 30, 2023 and is replaced by Managed Identities. We recommend to start migrating your runbooks to use managed identities. For more information, see [migrating from an existing Run As accounts to managed identity](../automation/automation-managed-identity-faq.md).
 > - Delaying the feature has a direct impact on our support burden, as it would cause upgrades of mobility agent to fail.
 
 This article shows you how to migrate your runbooks to use a Managed Identities for Azure Site Recovery. Azure Automation Accounts are used by Azure Site Recovery customers to auto-update the agents of their protected virtual machines. Site Recovery creates Azure Automation Run As Accounts when you enable replication via the IaaS VM Blade and Recovery Services Vault. 
@@ -22,6 +22,9 @@ On Azure, managed identities eliminate the need for developers having to manage
 
 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.
 
+> [!NOTE]
+> You can use the same automation account across multiple recovery services vaults, however, both the automation account and recovery services vault should be in the same region.
+
 ## Benefits of managed identities
 
 Here are some of the benefits of using managed identities: