Azure Devops Server End of Life Dates
other
Developers rely on Azure Devops Server to streamline their development processes, and for good reason - this powerful tool has been a cornerstone of agile development since its inception. Created to help teams collaborate and deliver high-quality software, Azure Devops Server has been maintained by Microsoft, a trusted name in the industry, to ensure it continues to meet the evolving needs of its users. With a history of providing robust features and support, Azure Devops Server has become an essential component of many development workflows, allowing teams to track progress, manage projects, and stay organized.
The end-of-life landscape for Azure Devops Server is characterized by a total of 15 versions, with 5 of these versions having already reached their end-of-life milestone. Currently, 10 versions remain active, with the latest stable version being 2017.3.1patch15. Looking ahead, the next version slated to reach its end-of-life date is version 2017, which will occur on 2027-01-11. This information is crucial for developers who need to plan their upgrades and migrations to ensure uninterrupted support and security. By staying informed about the lifecycle of each Azure Devops Server release, teams can proactively manage their development environments and minimize potential disruptions.
From a security standpoint, Azure Devops Server has a clean slate, with a total of 0 CVEs tracked and 0 critical CVEs reported. As a result, there is no most affected version to report. With no known vulnerabilities, developers can have confidence in the security of their Azure Devops Server installations. However, it is still essential for teams to stay vigilant and keep their systems up to date to ensure they remain secure. By tracking end-of-life dates and staying informed about potential security issues, developers can take proactive steps to protect their development environments and maintain the integrity of their projects.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| continuous | Dec 9, 2025 | — | No | — | Patch 5 | — | Active | |
| 2022.2 | Jul 9, 2024 | Jan 11, 2028 | Jan 11, 2033 | in 2363d | 2022.2patch10 | — | Active | |
| 2022.1 | Nov 28, 2023 | Jan 11, 2028 | Jan 11, 2033 | in 2363d | 2022.1patch4 | — | Active | |
| 2022.0 | Dec 6, 2022 | Jan 11, 2028 | Jan 11, 2033 | in 2363d | 2022.0.1patch5 | — | Active | |
| 2020.1 | May 25, 2021 | Oct 14, 2025 | Oct 8, 2030 | in 1537d | 2020.1.2patch19 | — | Active | |
| 2020.0 | Aug 25, 2020 | Oct 14, 2025 | Oct 8, 2030 | in 1537d | 2020.0.2patch6 | — | Active | |
| 2019.1 | Aug 20, 2019 | Apr 9, 2024 | Apr 10, 2029 | in 991d | 2019.1.2patch13 | — | Active | |
| 2019.0 | Mar 5, 2019 | Apr 9, 2024 | Apr 10, 2029 | in 991d | 2019.0.1patch16 | — | Active | |
| 2018 | Nov 15, 2017 | Jan 10, 2023 | Jan 11, 2028 | in 536d | 2018.3.2patch20 | — | Active | |
| 2017 | Nov 16, 2016 | Jan 11, 2022 | Jan 11, 2027 | in 171d | 2017.3.1patch15 | — | Active | |
| 2015 | Jul 30, 2015 | Oct 13, 2020 | Oct 14, 2025 | 283d ago | 2015.4.2patch8 | — | EOL | |
| 2013 | Jan 15, 2014 | Apr 9, 2019 | Apr 9, 2024 | 836d ago | 2013.5 | — | EOL | |
| 2012 | Oct 31, 2012 | Jan 9, 2019 | Jan 10, 2023 | 1291d ago | 2012.4 | — | EOL | |
| 2010 | Jun 29, 2010 | Jul 14, 2015 | Jul 14, 2020 | 2201d ago | 2010.SP1 | — | EOL | |
| 2005 | Jun 17, 2006 | Jul 12, 2011 | Jul 12, 2016 | 3664d ago | 2005.SP2 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
