Add

Author: aditiiitb

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

@@ -36,7 +36,7 @@ The in-place migration provides a highly resilient and self-healing offline migr
 
 ## Eligibility
 
-If you own a Single Server workload with no complex features (Read Replica, Virtual Network, Double Infra encryption, Service endpoint/VNet Rules) 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).
+If you own a Single Server workload with no complex features (Read Replica, Virtual Network, Double Infra encryption, Service endpoint/VNet Rules) enabled, you can now nominate yourself (if not already scheduled by the service) for automigration by submitting your server details through an Azure Support ticket.
 
 In order to make your ineligible server eligible for auto-migration perform the following steps :
 
@@ -73,7 +73,7 @@ Following described are the ways to review your migration schedule once you rece
   - Navigate to the **Migration blade** of your Single Server instance and select **edit** scheduled migration.
   - In the **Auto-migration details section** click on **Authenticate** button to authenticate and save ARM API connection to migrate your server.
   - If your server has **Microsoft Entra Admin** configured, you can provide inputs under the Microsoft Entra Admin section in the auto-migration wizard :
-    - Migrating Microsoft Entra admin for target server requires an **Identity** to be added to Azure Database for MySQL – Flexible Server. The Identity requires the following privileges – **User.Read.All, GroupMember.Read.All and Application.Read.All** to be granted. Please select an appropriate **user assigned managed identity**.  
+    - Migrating Microsoft Entra admin for target server requires an **Identity** to be added to Azure Database for MySQL – Flexible Server. The Identity requires the following privileges – **User.Read.All, GroupMember.Read.All and Application.Read.All** to be granted. Please select an appropriate **user assigned managed identity** and grant the right permissions by following steps [here](../flexible-server/how-to-azure-ad#grant-permissions-to-user-assigned-managed-identity).  
   - If your server has **Customer Managed Key** configured, you can provide inputs under the Data Encryption section in the auto-migration wizard :
     - Migrating customer managed key encryption requires an **Identity** to be added to Azure Database for MySQL – Flexible Server. Please select an appropriate **user assigned managed identity**. The listed **key identifier/key** would be migrated from the source to target server and should be granted the following privileges – **Get, Wrap Key, Unwrap Key** in order to access the key vault.
   - If your Single Server has **private endpoints**, perform the following **mandatory** steps when reviewing the migration schedule at least 2 days before the scheduled migration:

articles/mysql/migrate/whats-happening-to-mysql-single-server.md

@@ -41,7 +41,7 @@ Learn how to migrate from Azure Database for MySQL - Single Server to Azure Data
 For more information on migrating from Single Server to Flexible Server using other migration tools, visit [Select the right tools for migration to Azure Database for MySQL](../migrate/how-to-decide-on-right-migration-tools.md).
 
 > [!NOTE]  
-> In-place auto-migration from Azure Database for MySQL – Single Server to Flexible Server is a service-initiated in-place migration during planned maintenance window for select Single Server database workloads. The eligible servers are identified by the service and are sent an advance notification detailing steps to review migration details. If you own a Single Server workload with no complex features (Read Replica, Virtual Network, Double Infra encryption, Service endpoint/VNet Rules) 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). All other Single Server workloads are recommended to use user-initiated migration tooling offered by Azure - Azure DMS, Azure Database for MySQL Import to migrate. Learn more about in-place auto-migration [here](../migrate/migrate-single-flexible-in-place-auto-migration.md).
+> In-place auto-migration from Azure Database for MySQL – Single Server to Flexible Server is a service-initiated in-place migration during planned maintenance window for select Single Server database workloads. The eligible servers are identified by the service and are sent an advance notification detailing steps to review migration details. If you own a Single Server workload with no complex features (Read Replica, Virtual Network, Double Infra encryption, Service endpoint/VNet Rules) enabled, you can now nominate yourself (if not already scheduled by the service) for auto-migration by raising an Azure Support ticket. All other Single Server workloads are recommended to use user-initiated migration tooling offered by Azure - Azure DMS, Azure Database for MySQL Import to migrate. Learn more about in-place auto-migration [here](../migrate/migrate-single-flexible-in-place-auto-migration.md).
 
 ## Prerequisite checks when migrating from Single to Flexible Server
 
@@ -56,7 +56,7 @@ We have sent recurring notifications over the past two years to complete the mig
 
 Running the Single Server instance post sunset date would be a security risk, as there will be no security and bug fixes maintenance on the deprecated Single Server platform. To ensure our commitment towards running the managed instances on a trusted and secure platform post the sunset date, your Single Server instance, along with its data files, will be force-migrated to an appropriate Flexible Server instance in a phased manner.
 
-Starting 17th September, non-responsive servers which have an auto-migration scheduled and have not provided mandatory inputs will be stopped. Additionally servers with low TLS version, low client driver version and service endpoints will also be stopped. You'll be required to come to the Azure portal, acknowledge the migration actions and restart your server. Ensure to complete the action required in order to proceed with auto-migration, to avoid involuntary forced-migration later which could lead to server unavailability as only limited features can be migrated.
+Starting 17th September, non-responsive servers which have an auto-migration scheduled and have not provided mandatory inputs will be stopped. Additionally servers with low TLS version, low client driver version, service endpoints and other auto-migration ineligibilities who have not taken any action to migrate will also be stopped. You'll be required to come to the Azure portal, acknowledge the migration actions and restart your server. Ensure to complete the action required in order to proceed with auto-migration, to avoid involuntary forced-migration later which could lead to server unavailability as only limited features can be migrated.
 
 We strongly recommend using the [Azure Database for MySQL Import CLI](../migrate/migrate-single-flexible-mysql-import-cli.md) or [Azure Data Migration](../../dms/tutorial-mysql-Azure-single-to-flex-online-portal.md) Service to migrate to Azure Database for MySQL - Flexible Server before 16 September 2024 (read the [FAQ](./whats-happening-to-mysql-single-server.md#frequently-asked-questions-faqs) to learn more) to avoid any disruptions caused by forced migration and to ensure business continuity.