Azure Database for MariaDB is scheduled for retirement by September 19, 2025
In alignment with the Azure Database for MariaDB retirement announcement, we stopped support for creating MariaDB instances via the Azure portal or CLI as of March 19, 2024. If you still need to create MariaDB instances to address business continuity requirements, please raise an Azure support ticket.
Note: You can create read replicas and perform restores (PITR and geo-restore) for your existing MariaDB instances until the sunset date, September 19, 2025.
Migrating to Azure Database for MySQL - Flexible Server
To migrate your Azure Database for MariaDB workloads to Azure Database for MySQL – Flexible Server, set up replication between your MariaDB instance and a MySQL - Flexible Server instance so that you can perform a near-zero downtime online migration. To minimize the effort required for application refactoring, it is highly recommended to migrate your Azure MariaDB v10.3 workloads to Azure MySQL v5.7, which is closely compatible, and then subsequently plan for a major version upgrade to Azure MySQL v8.0.
For more information about how you can migrate your Azure Database for MariaDB server to Azure Database for MySQL - Flexible Server, see the blog post Migrating from Azure Database for MariaDB to Azure Database for MySQL.
SKU recommendations based on your MariaDB server compute SKU
The table below lists MySQL - Flexible Server SKU recommendations based on your existing MariaDB server compute SKU.
| MariaDB SKU (Source) |
MySQL - Flexible Server SKU (Target) |
| Basic 1-2 vCores |
Burstable 1-2 vCores |
| General Purpose 2-64 vCores |
General Purpose 2-96 vCores |
| Memory Optimized 2-32 vCores |
Business Critical 2-96 vCores |
Azure Database for MySQL - Flexible Server features recommended for performance and resiliency
To enhance the performance and resiliency of your Azure Database for MySQL – Flexible Server instance, it is recommended to take advantage of the following features:
-
Storage auto growth - prevents your server from running out of storage and becoming read-only.
-
High availability - This feature gives your more flexibility, where standby can be in the same zone or different paired zone to get 99.99% service level agreement.
-
Auto scale IOPS - Offers the flexibility to scale IOPS on demand, eliminating the need to pre-provision a specific amount of IO per second.
Conclusion
For more questions on Azure Database for MariaDB retirement, see our Frequently Asked Questions. If you have any feedback or questions about the information provided above, please leave a comment below or email us at AskAzureDBforMariaDB@service.microsoft.com.
Thank you!
