Microsoft has announced that it is retiring Azure Database for MariaDB on September 19, 2025. Beginning on March 19, 2024, Microsoft disabled the option to create new MariaDB instances. Any that were created before this date will continue to run until the retirement date. Any that remain will be permanently deleted, and all data that is not backed up or migrated will be lost.
What is MariaDB?
MariaDB is a relational database that was created by the developers of MySQL as a “drop-in replacement” for MySQL 5.5. Starting with version 10, MariaDB introduced new features not included in MySQL but still compatible.
What is Changing?
On September 19, 2025, Azure Database for MariaDB will be retired permanently. Any existing MariaDB instances will be deleted.
What are the Options?
Microsoft recommends migrating all instances to Azure Database for MySQL – Flexible Server. Azure Database for MySQL – Flexible Server is a fully managed PaaS offering from Microsoft with enhanced features such as increased availability, built-in scaling & added security. Microsoft offers MySQL version 5.7, which is compatible with MariaDB versions 10.2 & 10.3, and MySQL version 8.0, which is compatible with MariaDB version 10.5. A complete list of MariaDB to MySQL compatibility can be found here. Below are the basic steps to implement a migration to Azure Database for MySQL – Flexible Server.
- Create an Azure Database for MySQL – Flexible Server instance with the appropriate version of MySQL.
- Backup the existing Azure Database for MariaDB.
- Restore the MariaDB backup to MySQL.
- Configure replication from MariaDB to MySQL.
- Cutover to MySQL database once replication lag reaches zero.
- Upgrade MySQL (Optional)
An alternative option is to self-host MariaDB on virtual machines. This option is not recommended for production environments as it is much harder to manage. If you require a version of MySQL that Azure Database for MySQL – Flexible Server does not offer, this would be the way to achieve that. Microsoft currently supports MySQL version 5.7 & 8.0 and public preview versions 8.4 & 9.1. The public preview versions may not be fully developed and may be unstable, making them not a good choice for production workloads. The steps for self-hosted migration are similar to those above.
- Create one or more Virtual Machines (VMs).
- Install MariaDB on each VM.
- Backup the existing Azure Database for MariaDB.
- Restore the MariaDB backup to MariaDB on each VM.
- Configure replication from MariaDB to MySQL.
- Cutover to MySQL database once replication lag reaches 0.
- Configure replication between MariaDB VMs if required.
A third option is to migrate your MariaDB to Amazon Web Services (AWS). AWS offers Relational Database Service (RDS), a fully managed PaaS service. They offer stable versions of MariaDB up to 11.4.5. RDS supports MySQL & PostgresSQL, Microsoft SQL, IBM Db2, and Oracle DB.
No matter the migration path you decide to take, the experts at XTIVIA are here to help. The important thing is to act now to ensure plenty of time to make the appropriate changes and test, test, test.
For any questions, please contact us.