Azure Database For Postgresql End of Life Dates
other
Developers rely on Azure Database For Postgresql to manage their PostgreSQL databases in the cloud, and this service has been available since its introduction. The maintenance of this service is handled by Microsoft, ensuring that it stays up-to-date and secure for its users. By utilizing Azure Database For Postgresql, developers can take advantage of a managed database service that allows them to focus on application development, knowing that their database is being handled by a reliable service. This service has been a crucial tool for many developers, providing a scalable and secure way to manage their PostgreSQL databases.
The end-of-life landscape for Azure Database For Postgresql currently consists of 8 existing versions, with none of them having reached their end-of-life date yet. However, the first version to reach its end-of-life date will be version 11, which is scheduled to expire on 2026-07-31. This information is crucial for developers who need to plan their upgrades and ensure that their applications remain compatible with the latest versions of Azure Database For Postgresql. By tracking the end-of-life dates of each version, developers can avoid potential security risks and performance issues associated with using outdated software.
The security picture for Azure Database For Postgresql is currently very positive, with a total of 0 CVEs tracked and 0 critical CVEs reported. As a result, there is no most affected version, and the service is not currently listed on the Known Exploited Vulnerabilities catalog. With no known security vulnerabilities, developers can have confidence in the security of their Azure Database For Postgresql instances. Nevertheless, it is essential for developers to stay informed about the latest security updates and plan their upgrades accordingly to ensure the continued security and integrity of their databases. By doing so, they can minimize potential risks and ensure that their applications remain secure and reliable.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 18 | Sep 25, 2025 | — | Nov 14, 2030 | in 1574d | — | — | Active | |
| 17 | Sep 30, 2024 | — | Nov 8, 2029 | in 1203d | — | — | Active | |
| 16 | Oct 15, 2023 | — | Nov 9, 2028 | in 839d | — | — | Active | |
| 15 | May 15, 2023 | — | Nov 11, 2027 | in 475d | — | — | Active | |
| 14 | Jun 29, 2022 | — | Nov 12, 2026 | in 111d | — | — | Active | |
| 13 | May 25, 2021 | — | Jul 31, 2026 | in 7d | — | — | EOL soon | |
| 12 | Sep 22, 2020 | — | Jul 31, 2026 | in 7d | — | — | EOL soon | |
| 11 | Jul 24, 2019 | — | Jul 31, 2026 | in 7d | — | — | EOL soon |
Data sourced from endoflife.date · CVE data from NVD
