Retired and retiring Azure database services and their replacements
Which Azure database services and versions are gone or going, so an agent doesn't build on them — PostgreSQL and MySQL single server, Azure Database for MariaDB, Azure SQL Edge, Azure Cosmos DB for PostgreSQL, Azure Cache for Redis, PostgreSQL and MySQL versions in paid extended support, the Microsoft.Sql 2014-04-01 API — with dates and the service to use instead.
markdownreferencev1J0EH-2MT3stage: designtrust: officialservice: sqlservice: postgresqlservice: mysqlservice: cosmos-dbservice: redisinterface: anyAzure Database for PostgreSQL single server retired March 28 2025Azure Database for MySQL single server retired September 16 2024Azure Database for MariaDB retired September 19 2025Azure SQL Edge retired September 30 2025Azure Cosmos DB for PostgreSQL retirement pathAzure Cache for Redis retirementRedis Enterprise every-write AOF March 15 2025MySQL 5.7 end of supportPostgreSQL extended supportMicrosoft.Sql 2014-04-01 API retirementwhich Azure database to useAzure Managed Instance for Apache CassandraAzure DocumentDB
Retired and retiring Azure database services
Gone: don't create, migrate if found
| Service | Ended | Use instead |
|---|---|---|
| Azure Database for MySQL single server | September 16, 2024 (US time) | MySQL flexible server (reference/mysql/flexible-server.md) |
| Azure Database for PostgreSQL single server | March 28, 2025 | PostgreSQL flexible server (reference/postgresql/flexible-server.md) |
| Azure Database for MariaDB | September 19, 2025 | MySQL flexible server (Microsoft's migration guide targets it) |
| Azure SQL Edge | September 30, 2025 | Microsoft names no direct replacement |
| Redis Enterprise every-write AOF persistence | March 15, 2025 | Another persistence setting (Microsoft's lifecycle list names no specific one) |
Microsoft.Sql 2014-04-01 stable APIs | September 30, 2025 | Current API versions (2025-01-01 in this hub) |
Code or templates using Microsoft.DBforPostgreSQL/servers, Microsoft.DBforMySQL/servers or Microsoft.DBforMariaDB/servers (the single-server resource types) are out of date (the REST specs keep MySQL's under legacy/): the flexible-server types are …/flexibleServers.
Going: plan the move
| Service or version | Date | Use instead |
|---|---|---|
| Azure Cosmos DB for PostgreSQL | On a retirement path; new deployments blocked; no end date published | PostgreSQL flexible server elastic clusters (reference/postgresql/replicas-upgrades-and-clusters.md), or Cosmos DB for NoSQL |
| Azure Cache for Redis Enterprise and Enterprise Flash | March 31, 2027 (disabled April 1, 2027) | Azure Managed Redis (reference/redis/managed-redis.md) |
| Azure Cache for Redis Basic, Standard, Premium | September 30, 2028 (disabled October 1, 2028) | Azure Managed Redis |
| PostgreSQL 11, 12, 13 | Paid extended support since August 1, 2026 | Upgrade to 16–18 |
| PostgreSQL 14 | Standard support ends January 31, 2027 | Upgrade |
| MySQL 5.7 | In paid extended support since October 1, 2026 (version policy page) | 8.4 |
| MySQL 8.0 | Standard support ends January 31, 2027 | 8.4 |
Microsoft's 2025 lifecycle list gives September 30, 2025 as MySQL 5.7's end of support, while the MySQL version policy gives September 30, 2026 for the end of standard support, with extended support after it. The hub follows the version policy, which is service-specific and newer.
Not retired, but no longer Microsoft's first suggestion
- Cosmos DB for Apache Cassandra and for Apache Gremlin: Microsoft points new migrations to Azure Managed Instance for Apache Cassandra and Graph in Microsoft Fabric.
- Cosmos DB for MongoDB (RU): for MongoDB apps Microsoft suggests Azure DocumentDB (
reference/cosmos-db/other-apis-and-documentdb.md).