Add

Author: aditiiitb

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

@@ -16,7 +16,7 @@ ms.custom:
 > [!IMPORTANT]
 > Azure Database for MySQL - Single Server retired on **September 16, 2024**.
 
-After years of evolving the Azure Database for MySQL - Single Server service, it can no longer handle all the new features, functions, and security needs. We recommend upgrading to Azure Database for MySQL - Flexible Server before Sept 16, 2024 to avoid involuntary forced-migration and server unavailability.
+Azure Database for MySQL - Single Server service has been retired on September 16, 2024. We recommend migrating to Azure Database for MySQL - Flexible Server before Mar 10, 2025 to avoid server deletion.
 
 Azure Database for MySQL - Flexible Server is a fully managed production-ready database service designed for more granular control and flexibility over database management functions and configuration settings. For more information about Flexible Server, visit **[Azure Database for MySQL - Flexible Server](../flexible-server/overview.md)**.
 
@@ -51,9 +51,9 @@ For more information on migrating from Single Server to Flexible Server using ot
 
 We have sent recurring notifications over the past two years to complete the migration to Azure Database for MySQL Flexible Server, both via public channels such as Azure Update and blogs as well as direct outreach through customer emails, product pages, and Azure portal banners. As part of our ongoing communication and assistance to migrate customers safely to their new environment, this section provides more information on the customer experience for any workloads that remain in production beginning September 16, 2024.
 
-Starting September 17, 2024, nonresponsive servers which haven't yet migrated will be **periodically stopped**. You're required to come to the Azure portal, acknowledge the migration actions and start your server. Once you have started the server, proceed with 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. On the other hand if you wish to proceed with automigration, raise an Azure Support ticket to get the automigration scheduled. Ensure to start the server and migrate to Flexible Server to avoid involuntary forced-migration later which will lead to server unavailability as only limited features can be migrated.
+On Mar 10, 2025 nonresponsive servers which haven't yet migrated themselves or have been unable to be forced-migrated will be **deleted**. Please migrate your instances before Mar 10, 2025 to avoid any data loss.
 
-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 as a last resort to an appropriate Flexible Server instance in a phased manner.
+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, all eligible Single Server instances, along with its data files, will be force-migrated as a last resort to an appropriate Flexible Server instance in a phased manner.
 
 > [!NOTE]  
 > No SLAs, bug fixes, security fixes, or live support will be honored for your Single Server instance post the sunset date.
@@ -85,7 +85,7 @@ After the forced migration, you must reconfigure the features listed above on th
 - Read Replicas - The read replicas are migrated as separate standalone servers. Configure read replicas for your primary server by referring to the migrated secondary standalone server, which can be deleted post configuration. Read more about how to configure [here](../flexible-server/how-to-read-replicas-portal.md)
 
 > [!NOTE]  
-> If your server is in a region where Azure Database for MySQL - Flexible Server isn't supported, then post the sunset date, your Single Server instance will be available with limited operations to access data and to be able to migrate to Flexible Server until November 15 2024th, 2024. Your instance will not be force-migrated to Flexible Server until November 15 2024th, 2024. Your servers will be stopped in the first week of December, 2024. You can restart your server via Azure Portal or CLI and migrate within 7 days. If your server is not migrated in the above mentioned grace period, it will be force migrated in the second week of December, 2024. Post 31st December, servers will be deleted in order to retire the platform. We strongly recommend that you use one of the following options to migrate before November 22nd, 2024 to avoid any disruptions in business continuity:
+> If your server is in a region where Azure Database for MySQL - Flexible Server isn't supported, then post the sunset date, your Single Server instance will be available with limited operations to access data and to be able to migrate to Flexible Server. Your servers will be set to stopped on Feb 10, 2025. You can restart your server by opening an Azure Support ticket, where teh support team will help restart your server. To avoid the above disruption, we recommend migrating to the Flexible Server at the earliest. Post Mar 10, 2025 any remaining servers will be deleted in order to retire the platform. We strongly recommend that you use one of the following options to migrate before Feb 10, 2025 to avoid any disruptions in business continuity:
 
 > - Use Azure DMS to perform a cross-region migration to Flexible Server in a suitable Azure region.
 > - Migrate to MySQL Server hosted on a VM in the region, if you're unable to change regions due to compliance issues.