Merge pull request #11 from markingmyname/2460571

[MySQL] Remove erroneous images

Author: VandhanaMehta

articles/mysql/flexible-server/how-to-move-regions.md

@@ -1,23 +1,23 @@
 ---
 title: Move Azure regions - Azure portal - Azure Database for MySQL - Flexible Server
 description: Move an Azure Database for MySQL - Flexible Server from one Azure region to another using the Azure portal.
+author: VandhanaMehta
+ms.author: vamehta
+ms.reviewer: maghan
+ms.date: 08/23/2023
 ms.service: mysql
 ms.subservice: flexible-server
 ms.topic: how-to
-author: VandhanaMehta
-ms.author: vamehta
 ms.custom: subject-moving-resources
-ms.date: 04/08/2022
-#Customer intent: As an Azure service administrator, I want to move my service resources to another Azure region.
 ---
 
 # Move an Azure Database for MySQL - Flexible Server to another region by using the Azure portal
 
 There are various scenarios for moving an existing Azure Database for MySQL - Flexible Server from one region to another. For example, you might want to move a production server to another region as part of your disaster recovery planning.
 
-You can use Azure Database for MySQL - Flexible Server's [geo-restore](concepts-backup-restore.md#geo-restore) feature to complete the move to another region. To do so, first ensure geo-redundancy is enabled for your flexible server. Next, trigger geo-restore for your geo-redundant server and move your server to the geo-paired region.
+You can use Azure Database for MySQL - Flexible Server's [geo restore](concepts-backup-restore.md#geo-restore) feature to complete the move to another region. To do so, first ensure geo-redundancy is enabled for your flexible server. Next, trigger geo-restore for your geo-redundant server and move your server to the geo-paired region.
 
-> [!NOTE]
+> [!NOTE]  
 > This article focuses on moving your server to a different region. If you want to move your server to a different resource group or subscription, refer to the [move](../../azure-resource-manager/management/move-resource-group-and-subscription.md) article.
 
 ## Prerequisites
@@ -32,31 +32,31 @@ To move the Azure Database for MySQL - Flexible Server to the geo-paired region
 
 1. In the [Azure portal](https://portal.azure.com/), choose your flexible server that you want to restore the backup from.
 
-2. Click **Overview** from the left panel.
+1. Select **Overview** from the left panel.
 
-3. From the overview page, click **Restore**.
+1. From the overview page, select **Restore**.
 
-4. Restore page will be shown with an option to choose **Geo-redundant restore**. If you have configured your server for geographically redundant backups, the server can be restored to the corresponding Azure paired region and the geo-redundant restore option can be enabled. Geo-redundant restore option restores the server to Latest UTC Now timestamp and hence after selection of Geo-redundant restore, the point-in-time restore options cannot be selected simultaneously.
+1. Restore page is shown with an option to choose **Geo-redundant restore**. If you have configured your server for geographically redundant backups, the server can be restored to the corresponding Azure paired region and the geo-redundant restore option can be enabled. Geo-redundant restore option restores the server to Latest UTC Now timestamp and hence after selection of Geo-redundant restore, the point-in-time restore options can't be selected simultaneously.
 
-   :::image type="content" source="./media/how-to-move-regions/geo-restore-flex.png" alt-text="Geo-restore option":::
+   :::image type="content" source="./media/how-to-move-regions/geo-restore-flex.png" alt-text="Screenshot of Geo-restore option" lightbox="./media/how-to-move-regions/geo-restore-flex.png":::
 
-   :::image type="content" source="./media/how-to-move-regions/geo-restore-enabled-flex.png" alt-text="Enabling Geo-Restore":::
+   :::image type="content" source="./media/how-to-move-regions/geo-restore-enabled-flex.png" alt-text="Screenshot of Enabling Geo-Restore" lightbox="./media/how-to-move-regions/geo-restore-enabled-flex.png":::
 
-5. Provide a new server name in the **Name** field in the Server details section.
+1. Provide a new server name in the **Name** field in the Server details section.
 
-6. When primary region is down, one cannot create geo-redundant servers in the respective geo-paired region as storage cannot be provisioned in the primary region. One must wait for the primary region to be up to provision geo-redundant servers in the geo-paired region. With the primary region down one can still geo-restore the source server to the geo-paired region by disabling the geo-redundancy option in the Compute + Storage Configure Server settings in the restore portal experience and restore as a locally redundant server to ensure business continuity.
+1. When primary region is down, one can't create geo-redundant servers in the respective geo-paired region as storage can't be provisioned in the primary region. One must wait for the primary region to be up to provision geo-redundant servers in the geo-paired region. With the primary region down one can still geo-restore the source server to the geo-paired region by disabling the geo-redundancy option in the Compute + Storage Configure Server settings in the restore portal experience and restore as a locally redundant server to ensure business continuity.
 
-   :::image type="content" source="./media/how-to-move-regions/geo-restore-region-down-1.png" alt-text="Compute + Storage window":::
+   :::image type="content" source="./media/how-to-move-regions/geo-restore-region-down-1.png" alt-text="Screenshot of Compute + Storage window" lightbox="./media/how-to-move-regions/geo-restore-region-down-1.png":::
 
-   :::image type="content" source="./media/how-to-move-regions/geo-restore-region-down-2.png" alt-text="Disabling Geo-Redundancy":::
+   :::image type="content" source="./media/how-to-move-regions/geo-restore-region-down-2.png" alt-text="Screenshot of Disabling Geo-Redundancy" lightbox="./media/how-to-move-regions/geo-restore-region-down-2.png":::
 
-   :::image type="content" source="./media/how-to-move-regions/geo-restore-region-down-3.png" alt-text="Restoring as Locally redundant server":::
+   :::image type="content" source="./media/how-to-move-regions/geo-restore-region-down-3.png" alt-text="Screenshot of Restoring as Locally redundant server" lightbox="./media/how-to-move-regions/geo-restore-region-down-3.png":::
 
-7. Select **Review + Create** to review your selections.
+1. Select **Review + Create** to review your selections.
 
-8. A notification will be shown that the restore operation has been initiated. This operation may take a few minutes.
+1. A notification is shown that the restore operation has been initiated. This operation may take a few minutes.
 
-The new server created by geo-restore has the same server admin login name and password that was valid for the existing server at the time the restore was initiated. The password can be changed from the new server's Overview page. Additionally during a geo-restore, **Networking** settings such as virtual network settings and firewall rules can be configured as described in the below section.
+The new server created by geo-restore has the same server admin sign-in name and password that was valid for the existing server at the time the restore was initiated. The password can be changed from the new server's Overview page. Additionally during a geo-restore, **Networking** settings such as virtual network settings and firewall rules can be configured as described in the below section.
 
 ## Clean up source server
 
@@ -73,4 +73,4 @@ In this tutorial, you moved an Azure Database for MySQL - Flexible Server from o
 
 - Learn more about [geo-restore](concepts-backup-restore.md#geo-restore)
 - Learn more about [Azure paired regions](overview.md#azure-regions) supported for Azure Database for MySQL - Flexible Server
-- Learn more about [business continuity](concepts-business-continuity.md) options
+- Learn more about [business continuity](concepts-business-continuity.md) options