address reviewr changes

Author: markingmyname

articles/mysql/flexible-server/how-to-manage-server-portal.md

@@ -4,7 +4,7 @@ description: Learn how to manage Azure Database for MySQL - Flexible Server from
 author: mksuni
 ms.author: sumuth
 ms.reviewer: maghan
-ms.date: 05/17/2024
+ms.date: 05/21/2024
 ms.service: mysql
 ms.subservice: flexible-server
 ms.topic: how-to
@@ -16,9 +16,10 @@ ms.topic: how-to
 
 This article shows you how to manage your Azure Database for MySQL flexible server instances. Management tasks include compute and storage scaling, resetting the server administrator password, and deleting your server.
 
-## Sign in
+## Prerequisites
 
-Sign in to the [Azure portal](https://portal.azure.com). Go to your Azure Database for MySQL flexible server resource in the Azure portal.
+- Sign in to the [Azure portal](https://portal.azure.com).
+- Go to your Azure Database for MySQL flexible server resource in the Azure portal.
 
 ## Scale compute and storage
 
@@ -29,11 +30,11 @@ After server creation you can scale between the various [pricing tiers](https://
 1. You can change the **Compute Tier**, **vCore**, **Storage** to scale up the server using higher compute tier or scale up within the same tier by increasing storage or vCores to a value you want.
 
    > [!div class="mx-imgBorder"]
-   > :::image type="content" source="media/howto-manage-server-portal/scale-server.png" alt-text="Scaling storage for Azure Database for MySQL flexible server." lightbox="media/howto-manage-server-portal/scale-server.png":::
+   > :::image type="content" source="media/howto-manage-server-portal/scale-server.png" alt-text="Screenshot of scaling storage for Azure Database for MySQL flexible server." lightbox="media/howto-manage-server-portal/scale-server.png":::
 
-> [!IMPORTANT]  
-   > - Storage cannot be scaled down.
-   > - Scaling vCores causes a server restart.
+   > [!IMPORTANT]  
+      > - Storage cannot be scaled down.
+      > - Scaling vCores causes a server restart.
 
 1. Select **OK** to save changes.
 
@@ -43,25 +44,25 @@ You can change the administrator role's password using the Azure portal.
 
 1. Select your Azure Database for MySQL flexible server instance in the Azure portal. In the **Overview** window, select **Reset password**.
 
-1. Enter a new password and confirm the password. The textbox will prompt you about password complexity requirements.
+1. Enter a new password and confirm the password. The textbox prompts you about password complexity requirements.
 
    > [!div class="mx-imgBorder"]
-   > :::image type="content" source="media/howto-manage-server-portal/reset-password.png" alt-text="Reset your password for Azure Database for MySQL flexible server." lightbox="media/howto-manage-server-portal/reset-password.png":::
+   > :::image type="content" source="media/howto-manage-server-portal/reset-password.png" alt-text="Screenshot of resetting your password for Azure Database for MySQL flexible server." lightbox="media/howto-manage-server-portal/reset-password.png":::
 
 1. Select **Save** to save the new password.
 
 ## Delete a server
 
 You can delete your server if you no longer need it.
 
-1. Select your Azure Database for MySQL flexible server instance in the Azure portal. In the **Overview** window select **Delete**.
+1. Select your Azure Database for MySQL flexible server instance in the Azure portal. In the Overview window, select **Delete**.
 
 1. Type the name of the server into the input box to confirm that you want to delete the server.
 
    > [!div class="mx-imgBorder"]
-   > :::image type="content" source="media/howto-manage-server-portal/delete-server.png" alt-text="Delete the Azure Database for MySQL flexible server instance." lightbox="media/howto-manage-server-portal/delete-server.png":::
+   > :::image type="content" source="media/howto-manage-server-portal/delete-server.png" alt-text="Screenshot of deleting the Azure Database for MySQL flexible server instance." lightbox="media/howto-manage-server-portal/delete-server.png":::
 
-   > [!NOTE]  
+   > [!IMPORTANT]  
    > Deleting a server is irreversible.
 
 1. Select **Delete**.

articles/mysql/migrate/migrate-single-flexible-in-place-auto-migration.md

@@ -1,5 +1,5 @@
 ---
-title: "In-place automigration from Azure Database for MySQL – Single Server to Flexible Server"
+title: In-place automigration
 description: This tutorial describes how to configure notifications, review migration details and FAQs for an Azure Database for MySQL Single Server instance schedule for in-place automigration to Flexible Server.
 author: adig
 ms.author: adig
@@ -17,7 +17,7 @@ ms.custom:
 
 [!INCLUDE [applies-to-mysql-single-server](../includes/applies-to-mysql-single-server.md)]
 
-**In-place automigration** from Azure Database for MySQL – Single Server to Flexible Server is a service-initiated in-place migration during planned maintenance window for Single Server database workloads with **Basic, General Purpose or Memory Optimized SKU**, data storage used **<= 20 GiB** and **no complex features (CMK, AAD, Read Replica, Private Link) enabled**. The eligible servers are identified by the service and are sent an advance notification detailing steps to review migration details.
+**In-place automigration** from Azure Database for MySQL – Single Server to Flexible Server is a service-initiated in-place migration during planned maintenance window for Single Server database workloads with **Basic, General Purpose or Memory Optimized SKU**, data storage used **<= 20 GiB** and **no complex features (CMK, Microsoft Entra ID, Read Replica, Private Link) enabled**. The eligible servers are identified by the service and are sent an advance notification detailing steps to review migration details.
 
 The in-place migration provides a highly resilient and self-healing offline migration experience during a planned maintenance window, with less than **5 mins** of downtime. It uses backup and restore technology for faster migration time. This migration removes the overhead to manually migrate your server and ensure you can take advantage of the benefits of Flexible Server, including better price & performance, granular control over database configuration, and custom maintenance windows. Following described are the key phases of the migration:
 
@@ -30,7 +30,7 @@ The in-place migration provides a highly resilient and self-healing offline migr
 
 ## Eligibility
 
-If you own a Single Server workload with Basic, General Purpose or Memory Optimized SKU, data storage used <= 20 GiB and no complex features (CMK, AAD, Read Replica, Private Link) enabled, you can now nominate yourself (if not already scheduled by the service) for auto-migration by submitting your server details through this [form](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR4lhLelkCklCuumNujnaQ-ZUQzRKSVBBV0VXTFRMSDFKSUtLUDlaNTA5Wi4u).
+If you own a Single Server workload with Basic, General Purpose or Memory Optimized SKU, data storage used <= 20 GiB and no complex features (CMK, Microsoft Entra ID, Read Replica, Private Link) enabled, you can now nominate yourself (if not already scheduled by the service) for automigration by submitting your server details through this [form](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR4lhLelkCklCuumNujnaQ-ZUQzRKSVBBV0VXTFRMSDFKSUtLUDlaNTA5Wi4u).
 
 ## Configure migration alerts and review migration schedule
 
@@ -52,18 +52,18 @@ Following described are the ways to review your migration schedule once you rece
 - If you wish to defer the migration, you can defer by a month at a time by navigating to the Migration blade of your single server instance on the Azure portal and rescheduling the migration by selecting another migration window within a month.
 - If your Single Server has **General Purpose SKU**, you have the other option to enable **High Availability** when reviewing the migration schedule. As High Availability can only be enabled during create time for a MySQL Flexible Server, it's highly recommended that you enable this feature when reviewing the migration schedule.
 
-## Prerequisite checks for in-place auto-migration
+## Prerequisite checks for in-place automigration
 
 Review the following prerequisites to ensure a successful in-place automigration:
 
 - The Single Server instance should be in **ready state** and shouldn't be in stopped state during the planned maintenance window for automigration to take place.
-- For Single Server instance with **SSL enabled**, ensure you have all three certificates (**[BaltimoreCyberTrustRoot](https://cacerts.digicert.com/BaltimoreCyberTrustRoot.crt.pem), [DigiCertGlobalRootG2 Root CA](https://cacerts.digicert.com/DigiCertGlobalRootG2.crt.pem) and [DigiCertGlobalRootCA Root CA](https://dl.cacerts.digicert.com/DigiCertGlobalRootCA.crt.pem)**) available in the trusted root store. Additionally, if you have the certificate pinned to the connection string create a combined CA certificate with all three certificates before scheduled auto-migration to ensure business continuity post-migration.
+- For Single Server instance with **SSL enabled**, ensure you have all three certificates (**[BaltimoreCyberTrustRoot](https://cacerts.digicert.com/BaltimoreCyberTrustRoot.crt.pem), [DigiCertGlobalRootG2 Root CA](https://cacerts.digicert.com/DigiCertGlobalRootG2.crt.pem) and [DigiCertGlobalRootCA Root CA](https://dl.cacerts.digicert.com/DigiCertGlobalRootCA.crt.pem)**) available in the trusted root store. Additionally, if you have the certificate pinned to the connection string create a combined CA certificate with all three certificates before scheduled automigration to ensure business continuity post-migration.
 - The MySQL engine doesn't guarantee any sort order if there's no 'SORT' clause present in queries. Post in-place automigration, you might observe a change in the sort order. If preserving sort order is crucial, ensure your queries are updated to include 'SORT' clause before the scheduled in-place automigration.
 - If your source Azure Database for MySQL Single Server has engine version v8.x, ensure to upgrade your source server's .NET client driver version to 8.0.32 to avoid any encoding incompatibilities post migration to Flexible Server.
 - If your source Azure Database for MySQL Single Server has firewall rule names exceeding 80 characters, rename them to ensure length of name is fewer than 80 characters. (The firewall rule name length supported on Flexible Server is 80 characters whereas on Single Server the allowed length is 12 8 characters.)
-- If your source Azure Database for MySQL Single Server utilizes non-default ports such as 3308,3309 and 3310, change your connectivity port to 3306 as the above mentioned non-default ports are not supported on Flexible Server.
+- If your source Azure Database for MySQL Single Server utilizes nondefault ports such as 3308,3309 and 3310, change your connectivity port to 3306 as the above mentioned nondefault ports aren't supported on Flexible Server.
 
-## How is the target MySQL Flexible Server auto-provisioned?
+## How is the target MySQL Flexible Server autoprovisioned?
 
 The compute tier and SKU for the target flexible server is provisioned based on the source single server's pricing tier and VCores based on the detail in the following table.
 
@@ -81,15 +81,15 @@ The compute tier and SKU for the target flexible server is provisioned based on
 | Memory Optimized | 16 | MemoryOptimized | Standard_E16ds_v4 |
 | Memory Optimized | 32 | MemoryOptimized | Standard_E32ds_v4 |
 
-- The MySQL version, region, *storage size, subscription and resource group for the target Flexible Server is same as that of the source Single Server.
-- For Single Servers with less than 20 GiB storage, the storage size is set to 20 GiB as that is the minimum storage limit on Azure Database for MySQL - Flexible Server.
+- The MySQL version, region, *storage size, subscription, and resource group for the target Flexible Server is same as that of the source Single Server.
+- For Single Servers with less than 20-GiB storage, the storage size is set to 20 GiB as that is the minimum storage limit on Azure Database for MySQL - Flexible Server.
 - Both username formats – username@server_name (Single Server) and username (Flexible Server) are supported on the migrated Flexible Server.
 - Both connection string formats – Single Server and Flexible Server are supported on the migrated Flexible Server.
 - For Single Server instance with Query store enabled, the server parameter 'slow_query_log' on target instance is set to ON to ensure feature parity when migrating to Flexible Server. For certain workloads this could affect performance and if you observe any performance degradation, set this server parameter to 'OFF' on the Flexible Server instance.
 
 ## Post-migration steps
 
-Here is the info you need to know post in-place migration:
+Here's the info you need to know post in-place migration:
 
 > [!NOTE]
 > Post-migration do no restart the stopped Single Server instance as it might hamper your client's and application connectivity.
@@ -98,7 +98,7 @@ Here is the info you need to know post in-place migration:
   - Monitoring page settings (Alerts, Metrics, and Diagnostic settings)
   - Any Terraform/CLI scripts you host to manage your Single Server instance should be updated with Flexible Server references.
 - For Single Server instance with Query store enabled, the server parameter 'slow_query_log' on target instance is set to ON to ensure feature parity when migrating to Flexible Server. Note, for certain workloads this could affect performance and if you observe any performance degradation, set this server parameter to 'OFF' on the Flexible Server instance.
-- For Single Server instance with Microsoft Defender for Cloud enabled, the enablement state is migrated. To achieve parity in Flexible Server post auto-migration for properties you can configure in Single Server, consider the details in the following table:
+- For Single Server instance with Microsoft Defender for Cloud enabled, the enablement state is migrated. To achieve parity in Flexible Server post automigration for properties you can configure in Single Server, consider the details in the following table:
 
 | Property | Configuration |
 | --- | --- |
@@ -125,7 +125,7 @@ Here is the info you need to know post in-place migration:
 
 **Q. How can I defer the scheduled migration?​**
 
-**A.** You can review the migration schedule by navigating to the Migration blade of your Single Server instance. If you wish to defer the migration, you can defer by a month at the most by navigating to the Migration blade of your single server instance on the Azure portal and re-scheduling the migration by selecting another migration window within a month. The migration details will be locked 7 days prior to the scheduled migration window after which you're unable to reschedule. This in-place migration can be deferred monthly until 16 September 2024.
+**A.** You can review the migration schedule by navigating to the Migration blade of your Single Server instance. If you wish to defer the migration, you can defer by a month at the most by navigating to the Migration blade of your single server instance on the Azure portal and rescheduling the migration by selecting another migration window within a month. The migration details will be locked seven days prior to the scheduled migration window after which you're unable to reschedule. This in-place migration can be deferred monthly until 16 September 2024.
 
 **Q. What username and connection string would be supported for the migrated Flexible Server? ​​**
 
@@ -137,8 +137,8 @@ Here is the info you need to know post in-place migration:
 
 **Q. I see a pricing difference on my potential move from MySQL Basic Single Server to MySQL Flexible Server??​**
 
-**A.** Few servers might see a small price increase after migration (estimated costs can be seen by selecting the automigration schedule edit option on the portal), as the minimum storage limit on both offerings is different (5 GiB on Single Server; 20 GiB on Flexible Server) and storage cost (0.1$ on Single Server; 0.115$ on Flexible Server) for Flexible Server is slightly higher than Single Server. For affected servers, this price increase in Flexible Server provides better throughput and performance compared to Single Server
+**A.** Few servers might see a small price increase after migration (estimated costs can be seen by selecting the automigration schedule edit option on the portal), as the minimum storage limit on both offerings is different (5 GiB on Single Server; 20 GiB on Flexible Server) and storage cost (0.1$ on Single Server; 0.115$ on Flexible Server) for Flexible Server is slightly higher than Single Server. For affected servers, this price increase in Flexible Server provides better throughput and performance compared to Single Server.
 
 ## Related content
 
-[Manage an Azure Database for MySQL - Flexible Server using the Azure portal](../flexible-server/how-to-manage-server-portal.md)
+[Manage an Azure Database for MySQL - Flexible Server using the Azure portal.](../flexible-server/how-to-manage-server-portal.md)