Merge pull request #280023 from aditivgupta/autoup

Update

Author: prmerger-automator[bot]

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

@@ -78,6 +78,7 @@ The compute tier and SKU for the target flexible server is provisioned based on
 | --- | --- | :---: | :---: |
 | Basic | 1 | Burstable | Standard_B1s |
 | Basic | 2 | Burstable | Standard_B2s |
+| General Purpose | 2 | GeneralPurpose | Standard_D2ds_v4 |
 | General Purpose | 4 | GeneralPurpose | Standard_D4ds_v4 |
 | General Purpose | 8 | GeneralPurpose | Standard_D8ds_v4 |
 | General Purpose | 16 | GeneralPurpose | Standard_D16ds_v4 |
@@ -102,7 +103,7 @@ Here's the info you need to know post in-place migration:
 > Post-migration do no restart the stopped Single Server instance as it might hamper your client's and application connectivity.
 
 - Copy the following properties from the source Single Server to target Flexible Server post in-place migration operation is completed successfully:
-  - Monitoring page settings (Alerts, Metrics, and Diagnostic settings)
+  - Monitoring page settings (Alerts, Metrics, and Diagnostic settings) and Locks 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 automigration for properties you can configure in Single Server, consider the details in the following table: