Clarification on In-Place Migration Eligibility for Azure Database for MySQL Server

Hello @Sina Salam ,

I still have significant concerns regarding the upcoming in-place migration of our Azure Database for MySQL server to a Flexible Server, specifically related to the handling of our private endpoints.

Based on the documentation, our server should be ineligible for this migration due to the configuration of private endpoints, which rely on the Private Link service.

Please find below the output of the first command you provided:

This indicates that the Private Link service connection is enabled and in an active state.

Given these criteria, our server, which has private endpoints configured, should not qualify for in-place migration. This discrepancy (documentation vs actions) raises several concerns:

Documentation Clarity: The current documentation clearly states that servers with private links enabled are not eligible for in-place migration. If there have been recent updates or exceptions to this eligibility, please provide detailed information and update the documentation accordingly.

Migration Handling of Private Endpoints: Even if our server is being considered for migration, there is a lack of clarity on how the migration process will handle the existing private endpoints. Given the critical nature of these configurations, I need assurance and detailed steps on how the migration will maintain or reconfigure these endpoints to ensure uninterrupted service.

Additionally, I have attached a screenshot from our Private Link Center, showing the current private endpoints.

Could you please confirm that these endpoints and all related configurations will be securely migrated, ensuring no loss of functionality or connectivity?

Furthermore, I have already raised a support ticket regarding this issue but did not receive a clear resolution. Although I provided positive feedback for the support engineer to avoid any negative repercussions for them, my concerns remain unaddressed. The suggestion to raise another support ticket feels like a repeat of an already unhelpful process.

I urge you to provide a detailed and concrete response addressing these points to ensure we can proceed with confidence or understand the necessary steps to mitigate any potential issues.

Thank you for your assistance.

Regards,
Cosmina

Hi,

Thank you for your feedback.

Good to know about your endpoint, and based on the latest information I found, it appears that there have been updates regarding the migration of servers with private links enabled.

Microsoft Azure now provides a way to migrate servers over a private network by using Azure Private Link. You can use the Migration and modernization tool to connect privately and securely to Azure Migrate over an Azure ExpressRoute private peering or a site-to-site (S2S) VPN connection by using Private Link.

# Ensure you create backup
# Example Azure CLI command to create a backup
az mysql flexible-server backup create --resource-group YourResourceGroup --name YourDatabaseServer --backup-name YourBackupName
# Example PowerShell command to list private endpoints
Get-AzPrivateEndpoint -ResourceGroupName "YourResourceGroup"
Check Database Connectivity:
# Example MySQL command to test connectivity
mysql -h your-database.private.endpoint -u your-username -p

There should not be any loss of functionality or connectivity if above are put into consideration.

Check out the reference below for more details and documentation as requested.

• Migrate servers to Azure by using Private Link: https://video2.skills-academy.com/en-us/azure/migrate/migrate-servers-to-azure-using-private-link
• Use Azure Migrate with private endpoints - Azure Migrate: https://video2.skills-academy.com/en-us/azure/migrate/how-to-use-azure-migrate-with-private-endpoints
• Azure Migrate private endpoint support available in public preview: https://azure.microsoft.com/en-us/updates/azure-migrate-private-endpoint-support-available-in-public-preview/

Best,

Sina

Hello @Sina Salam ,

Thank you for your response and the information provided.

However, I still have 2 questions regarding the in-place automigration of our Azure Database for MySQL Single Server, specifically in relation to our Private Endpoints.

1. Will the in-place automigration automatically handle our private endpoints without any loss of functionality or connectivity, or do we need to manually take any actions before the scheduled migration by following steps from the links provided by you?
2. Also, if we conclude that we want to cancel the auto-migration, can we raise a ticket for this and someone from your end will cancel it from backend? This is just a question for now, not sure if we'll need to cancel or not at this moment.

Clear guidance on this is essential to ensure a smooth transition, especially when we go in production with this.

Thank you for your assistance.

Best regards,

Cosmina

Hi Cosmina,

Thank you for acknowledgement and more questions.

Question 1:

Will the in-place automigration automatically handle our private endpoints without any loss of functionality or connectivity, or do we need to manually take any actions before the scheduled migration by following steps from the links provided by you?

The in-place auto-migration should automatically handle private endpoints without any loss of functionality or connectivity. It is advisable to verify and document current configurations, monitor the migration process, and validate post-migration to ensure a smooth transition.

Question 2:

Also, if we conclude that we want to cancel the auto-migration, can we raise a ticket for this and someone from your end will cancel it from backend? This is just a question for now, not sure if we'll need to cancel or not at this moment.

Yes! You can raise a support ticket to cancel the auto-migration if needed. Provide detailed information in the ticket and follow up with Azure support to ensure the request is processed.

Best,

Sina