Skip to content

Commit c86c641

Browse files
authored
Merge pull request #278735 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents a6b80f5 + d95a21a commit c86c641

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/mariadb/whats-happening-to-mariadb.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -52,6 +52,8 @@ A. Your existing Azure Database for MariaDB workloads will continue to function
5252

5353
A. Unfortunately, we don't plan to support Azure Database for MariaDB beyond the sunset date of September 19, 2025. Hence, we advise that you start planning your migration as soon as possible.
5454

55+
On 19 September 2025, workloads that run Azure Database for MariaDB will be deleted, and associated application data will be lost. For more information, see [Azure Database for MariaDB will be retired on 19 September 2025 – Migrate to Azure Database for MySQL Flexible Server](https://azure.microsoft.com/updates/azure-database-for-mariadb-will-be-retired-on-19-september-2025-migrate-to-azure-database-for-mysql-flexible-server/)
56+
5557
**Q. How do I manage my reserved instances for MariaDB?**
5658

5759
A. Since MariaDB service is on the deprecation path you will not be able to purchase new MariaDB reserved instances. For any existing reserved instances, you will continue to use the benefits of your reserved instances until the September, 19 2025 when MariaDB service will no longer be available. [You can exchange your existing MariaDB reservations to MySQL reservations](/azure/cost-management-billing/reservations/exchange-and-refund-azure-reservations).

0 commit comments

Comments
 (0)