Merge pull request #239403 from SnehaSudhirG/26May-RemoveRenewRunAs

Removed a section and added note

Author: prmerger-automator[bot]

articles/automation/how-to/move-account.md

@@ -3,7 +3,7 @@ title: Move your Azure Automation account to another subscription
 description: This article tells how to move your Automation account to another subscription.
 services: automation
 ms.subservice: process-automation
-ms.date: 01/07/2021
+ms.date: 05/26/2023
 ms.topic: conceptual 
 ---
 
@@ -16,8 +16,7 @@ The Automation account is one of the resources that you can move. In this articl
 1. Disable your features.
 2. Unlink your workspace.
 3. Move the Automation account.
-4. Delete and re-create the Run As accounts.
-5. Re-enable your features.
+4. Re-enable your features.
 
 ## Remove features
 
@@ -97,43 +96,25 @@ You can now move your Automation account and its runbooks.
 
 2. Select the resources in your resource group that you want to move. Ensure that you include your Automation account, runbooks, and Log Analytics workspace resources.
 
-## Re-create Run As accounts
-
-[Run As accounts](../automation-security-overview.md#run-as-accounts) create a service principal in Azure Active Directory to authenticate with Azure resources. When you change subscriptions, the Automation account no longer uses the existing Run As account. To re-create the Run As accounts:
-
-1. Go to your Automation account in the new subscription, and select **Run as accounts** under **Account Settings**. You'll see that the Run As accounts show as incomplete now.
-
-    ![Screenshot of Run As accounts, showing incomplete](../media/move-account/run-as-accounts.png)
-
-2. Delete the Run As accounts, one at a time, by selecting **Delete** on the **Properties** page. 
-
-    > [!NOTE]
-    > If you don't have permissions to create or view the Run As accounts, you see the following message: `You do not have permissions to create an Azure Run As account (service principal) and grant the Contributor role to the service principal.` For more information, see [Permissions required to configure Run As accounts](../automation-security-overview.md#permissions).
-
-3. After you've deleted the Run As accounts, select **Create** under **Azure Run As account**. 
-
-4. On the Add Azure Run As account page, select **Create** to create the Run As account and service principal. 
-
-5. Repeat the steps above with the Azure Classic Run As account.
+> [!NOTE]
+> The movement of System assigned managed identity, and User-assigned managed identity takes place automatically with the Automation account.
 
 ## Enable features
 
-After you re-create the Run As accounts, you must re-enable the features that you removed before the move:
+You must re-enable the features that you removed before the move:
 
 1. To turn on Change Tracking and Inventory, select **Change Tracking and Inventory** in your Automation account. Choose the Log Analytics workspace that you moved over, and select **Enable**.
 
 2. Repeat step 1 for Update Management.
 
     ![Screenshot of Re-enabling features in your moved Automation account](../media/move-account/reenable-solutions.png)
 
-3. Machines that are enabled with your features are visible when you've connected the existing Log Analytics workspace. To turn on the Start/Stop VMs during off-hours feature, you must re-enable it. Under **Related Resources**, select **Start/Stop VMs** > **Learn more about and enable the solution** > **Create** to start the deployment.
+3. Machines that are enabled with your features are visible when you've connected the existing Log Analytics workspace.
 
 4. On the Add Solution page, choose your Log Analytics workspace and Automation account.
 
     ![Screenshot of Add Solution menu](../media/move-account/add-solution-vm.png)
 
-5. Configure the feature as described in [Start/Stop VMs during off-hours overview](../automation-solution-vm-management.md).
-
 ## Verify the move
 
 When the move is complete, verify that the capabilities listed below are enabled. 

articles/azure-resource-manager/management/move-support-resources.md

@@ -161,9 +161,8 @@ Before starting your move operation, review the [checklist](./move-resource-grou
 ## Microsoft.Automation
 
 > [!IMPORTANT]
-> Runbooks must exist in the same resource group as the Automation Account.
->
-> For information, see [Move your Azure Automation account to another subscription](../../automation/how-to/move-account.md?toc=/azure/azure-resource-manager/toc.json).
+> Runbooks must exist in the same resource group as the Automation Account. 
+> The movement of System assigned managed identity, and User-assigned managed identity takes place automatically with the Automation account. For information, see [Move your Azure Automation account to another subscription](../../automation/how-to/move-account.md?toc=/azure/azure-resource-manager/toc.json).
 
 > [!div class="mx-tableFixed"]
 > | Resource type | Resource group | Subscription | Region move |