About Azure Database for MySQL 5.7 EOL

Question

It says , "Creation of new servers using the Azure portal.　To Be Decided" "Creation of new servers using the Command Line Interface (CLI). To Be Decided" Have you decided? https://learn.microsoft.com/en-us/azure/mysql/concepts-version-policy

Answer 1

Hi
naotoshi suzuki •,

Thanks for your patience.

We have got the below reply from the internal team:

As of now we have not made any decisions that when will we stop the creation of 5.7 servers, actually we may even keep this door open as long as we are providing Azure MySQL offering. Our product team is listening to community’s feedback and if there is a strong need that many customers would like to stay in 5.7, in that case we will always respect our customers’ choice and give customers the option to create new 5.7 servers.

Even if one day we stop the creation of 5.7 due to no strong feedback from community, we won’t stop customers’ existing 5.7 servers unless there is very critical security issue with 5.7 servers and that issue might lead to data loss.

While we are pending on making the decision of when to stop the 5.7 server creation, could you please let us know why you are choosing new servers default to 5.7 instead of 8.0, given the situation that 5.7 has already been announced deprecated by Oracle last year.

Your response is awaited.

Thanks

Answer 2

Hi
naotoshi suzuki •,

Welcome to Microsoft Q&A forum.

As I understand, you want to know the timeline of Azure Database for MySQL 5.7 EOL.

We initially planned to stop the creation of new Azure Database for MySQL version 5.7 instances via CLI and Portal after April 2024. However, after further review and customer feedback, we have decided to delay this action. The specific date for discontinuing the creation of new MySQL 5.7 instances is currently under review and remains 'To Be Decided'. This change reflects our commitment to accommodating customer needs and providing flexibility during the transition. We value your feedback and encourage ongoing communication as we navigate these changes.

I am checking internally about tentative timeline. Thanks