added note in Azure resource manager article

Author: SnehaSudhirG

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

@@ -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
 
@@ -103,22 +102,20 @@ You can now move your Automation account and its runbooks.
 
 ## 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 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 |