Merge pull request #251206 from aditivgupta/selfserve

Selfserve

Author: prmerger-automator[bot]

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

@@ -24,6 +24,9 @@ The in-place migration provides a highly resilient and self-healing offline migr
 > [!NOTE]
 > In-place migration is only for Single Server database workloads with Basic or GP SKU, data storage used < 10 GiB and no complex features (CMK, AAD, Read Replica, Private Link) enabled. All other Single Server workloads are recommended to use user-initiated migration tooling offered by Azure - Azure DMS, Azure MySQL Import to migrate.
 
+## What's new?
+* If you own a Single Server workload with Basic or GP SKU, data storage used < 10 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). (Sept 2023)
+
 ## Configure migration alerts and review migration schedule
 
 Servers eligible for in-place automigration are sent an advance notification by the service.
@@ -39,7 +42,7 @@ Following described are the ways to review your migration schedule once you have
 > [!NOTE]
 > The migration schedule will be locked 7 days prior to the scheduled migration window after which you’ll be unable to reschedule.
 
-* The S**ingle Server overview page** for your instance displays a portal banner with information about your migration schedule.
+* The **Single Server overview page** for your instance displays a portal banner with information about your migration schedule.
 * For Single Servers scheduled for automigration, a new **Migration blade** is lighted on the portal. 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 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.