Merge pull request #222152 from ankitaduttaMSFT/RM-correction

corrections

Author: prmerger-automator[bot]

articles/resource-mover/tutorial-move-region-encrypted-virtual-machines.md

@@ -289,8 +289,7 @@ To prepare to move the source resource group, do the following:
 
 > [!NOTE]
 > After you've committed the move, the source resource group status changes to *Delete source pending*.
-
-:::image type="content" source="./media/tutorial-move-region-encrypted-virtual-machines/resource-group-delete-move-pending.png" alt-text="Screenshot of the source resource group showing the status changed to 'Delete source pending'." lightbox="./media/tutorial-move-region-encrypted-virtual-machines/resource-group-delete-move-pending.png":::
+> :::image type="content" source="./media/tutorial-move-region-encrypted-virtual-machines/resource-group-delete-move-pending.png" alt-text="Screenshot of the source resource group showing the status changed to 'Delete source pending'." lightbox="./media/tutorial-move-region-encrypted-virtual-machines/resource-group-delete-move-pending.png":::
 
 ## Prepare resources to move
 
@@ -308,8 +307,7 @@ Now that the encryption resources and the source resource group are moved, you c
 
 > [!NOTE]
 > After you've prepared the resources, their status changes to *Initiate move pending*.
-
-:::image type="content" source="./media/tutorial-move-region-encrypted-virtual-machines/resources-initiate-move-pending.png" alt-text="Screenshot of the 'Prepare resources' pane, showing the resources in 'Initiate move pending' status." lightbox="./media/tutorial-move-region-encrypted-virtual-machines/resources-initiate-move-pending.png":::
+> :::image type="content" source="./media/tutorial-move-region-encrypted-virtual-machines/resources-initiate-move-pending.png" alt-text="Screenshot of the 'Prepare resources' pane, showing the resources in 'Initiate move pending' status." lightbox="./media/tutorial-move-region-encrypted-virtual-machines/resources-initiate-move-pending.png":::
 
 
 ## Initiate the move
@@ -324,10 +322,10 @@ Now that you've prepared the resources prepared, you can initiate the move.
     - Resource Mover re-creates other resources by using the prepared ARM templates. There's usually no downtime.
     - After you've moved the resources, their status changes to *Commit move pending*.
 
-:::image type="content" source="./media/tutorial-move-region-encrypted-virtual-machines/resources-commit-move-pending.png" alt-text="Screenshot of a list of resources with a 'Commit move pending' status." lightbox="./media/tutorial-move-region-encrypted-virtual-machines/resources-commit-move-pending.png" :::
+    :::image type="content" source="./media/tutorial-move-region-encrypted-virtual-machines/resources-commit-move-pending.png" alt-text="Screenshot of a list of resources with a 'Commit move pending' status." lightbox="./media/tutorial-move-region-encrypted-virtual-machines/resources-commit-move-pending.png" :::
 
 
-## Manage the move
+## Discard or commit the move
 
 After the initial move, you can decide whether to commit the move or discard it. 
 
@@ -363,8 +361,6 @@ To complete the move process, you commit the move by doing the following:
 > - The commit process doesn't affect the source networking resources.
 > - After you've committed the move, the resource statuses change to *Delete source pending*.
 
-
-
 ## Configure settings after the move
 
 You can configure the following settings after the move process:

articles/resource-mover/tutorial-move-region-powershell.md

@@ -17,21 +17,15 @@ This article explains how to move Azure resources to a different Azure region, u
 In this tutorial, you learn how to:
 
 > [!div class="checklist"]
-> * Check prerequisites and requirements.
-> * Set up the move collection.
-> * Add resources to the move collection, and resolve dependencies.
-> * Prepare and move the source resource group.
-> * Prepare and move the other resources.
-> * Decide whether you want to discard or commit the move.
-> * Optionally remove resources in the source region after the move.
+> * Move Azure resources to a different Azure region
 
 > [!NOTE]
 > Tutorials show the quickest path for trying out a scenario and use default options.
 
-If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/pricing/free-trial/) before you begin. Then sign in to the [Azure portal](https://portal.azure.com).
-
 ## Prerequisites
 
+Verify the following requirements:
+
 | Requirement | Description |
 | --- | --- |
 | **Subscription permissions** | Check you have *Owner* access on the subscription containing the resources that you want to move<br/><br/> **Why do I need Owner access?** The first time you add a resource for a  specific source and destination pair in an Azure subscription, Resource Mover creates a [system-assigned managed identity](../active-directory/managed-identities-azure-resources/overview.md#managed-identity-types) (formerly known as Managed Service Identify (MSI)) that's trusted by the subscription. To create the identity, and to assign it the required role (Contributor or User Access administrator in the source subscription), the account you use to add resources needs *Owner* permissions on the subscription. [Learn more](../role-based-access-control/rbac-and-directory-admin-roles.md#azure-roles) about Azure roles. |
@@ -71,6 +65,8 @@ We're using these values in our script examples:
 
 ## Sign in to Azure
 
+If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/pricing/free-trial/) before you begin. Then sign in to the [Azure portal](https://portal.azure.com).
+
 Sign in to your Azure subscription with the Connect-AzAccount cmdlet:
 
 ```azurepowershell-interactive
@@ -425,13 +421,4 @@ After committing the move, and verifying that resources work as expected in the
 
 ## Next steps
 
-In this tutorial, you:
-
-> [!div class="checklist"]
-> * Moved Azure VMs to another Azure region using PowerShell.
-> * Moved resources associated with VMs to another region.
-
-Now, try moving Azure VMs using the portal:
-
-> [!div class="nextstepaction"]
-> [Move Azure VMs in the portal](./tutorial-move-region-virtual-machines.md)
+[Learn more](./tutorial-move-region-virtual-machines.md) about move Azure VMs in the portal.

articles/resource-mover/tutorial-move-region-sql.md

@@ -5,26 +5,20 @@ author: ankitaduttaMSFT
 manager: evansma
 ms.service: resource-mover
 ms.topic: tutorial
-ms.date: 12/16/2022
+ms.date: 12/21/2022
 ms.author: ankitadutta
 ms.custom: mvc, engagement-fy23
 #Customer intent: As an Azure admin, I want to move SQL Server databases to a different Azure region.
 ---
 
-# Tutorial: Move Azure SQL Database resources to another region
+# Move Azure SQL Database resources to another region
 
 In this tutorial, you learn how to move Azure SQL databases and elastic pools to a different Azure region, using [Azure Resource Mover](overview.md).
 
 In this tutorial, you learn how to:
 
 > [!div class="checklist"]
-> * Check prerequisites and requirements.
-> * Select the resources you want to move.
-> * Resolve resource dependencies.
-> * Prepare and move the SQL Server to the target region.
-> * Prepare and move databases and elastic pools.
-> * Decide whether you want to discard or commit the move. 
-> * Optionally remove resources in the source region after the move. 
+> * Move Azure SQL databases and elastic pools to a different Azure region 
 
 > [!NOTE]
 > Tutorials show the quickest path for trying out a scenario, and use default options. 
@@ -279,10 +273,4 @@ After the move, you can optionally delete resources in the source region.
 
 ## Next steps
 
-In this tutorial, you:
-
-> [!div class="checklist"]
-> * Moved Azure SQL databases to another Azure region.
-> * Moved Azure SQL elastic pools to another region.
-
-Now, try [moving Azure VMs to another region](./tutorial-move-region-virtual-machines.md).
+[Learn more](./tutorial-move-region-virtual-machines.md) about moving Azure VMs to another region.

articles/resource-mover/tutorial-move-region-virtual-machines.md

@@ -200,7 +200,7 @@ With resources prepared, you can now initiate the move. To start the move, follo
 > :::image type="content" source="./media/tutorial-move-region-virtual-machines/delete-source-pending.png" alt-text="Screenshot displays page showing resources in *Delete source pending* state." lightbox="./media/tutorial-move-region-virtual-machines/delete-source-pending.png":::
 
 
-## Manage the move
+## Commit or discard the move
 
 After the initial move, you can decide if you want to commit the move or discard it. 
 
@@ -235,8 +235,7 @@ If you want to complete the move process, commit the move. To commit the move, f
 > - After committing the move, VMs stop replicating. The source VM isn't impacted by the commit.
 > - Commit doesn't impact source networking resources.
 > - After committing the move, resources are in a *Delete source pending* state.
-
- :::image type="content" source="./media/tutorial-move-region-virtual-machines/delete-source-pending.png" alt-text="Screenshot displays page showing resources in *Delete source pending* state." lightbox="./media/tutorial-move-region-virtual-machines/delete-source-pending.png":::
+> :::image type="content" source="./media/tutorial-move-region-virtual-machines/delete-source-pending.png" alt-text="Screenshot displays page showing resources in *Delete source pending* state." lightbox="./media/tutorial-move-region-virtual-machines/delete-source-pending.png":::
 
 
 ## Configure settings after the move