Complete end-of-life dates, support windows, and security status for all Azure Devops Server versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2005 | 2005.SP2 | Jun 17, 2006 | Jul 12, 2016 | 3588 days past EOL | EOL |
| 2010 | 2010.SP1 | Jun 29, 2010 | Jul 14, 2020 | 2125 days past EOL | EOL |
| 2012 | 2012.4 | Oct 31, 2012 | Jan 10, 2023 | 1215 days past EOL | EOL |
| 2013 | 2013.5 | Jan 15, 2014 | Apr 9, 2024 | 760 days past EOL | EOL |
| 2015 | 2015.4.2patch8 | Jul 30, 2015 | Oct 14, 2025 | 207 days past EOL | EOL |
| 2017 | 2017.3.1patch15 | Nov 16, 2016 | Jan 11, 2027 | 247 days remaining | Active |
| 2018 | 2018.3.2patch20 | Nov 15, 2017 | Jan 11, 2028 | 612 days remaining | Active |
| 2019.0 | 2019.0.1patch16 | Mar 5, 2019 | Apr 10, 2029 | 1067 days remaining | Active |
| 2019.1 | 2019.1.2patch12 | Aug 20, 2019 | Apr 10, 2029 | 1067 days remaining | Active |
| 2020.0 | 2020.0.2patch6 | Aug 25, 2020 | Oct 8, 2030 | 1613 days remaining | Active |
| 2020.1 | 2020.1.2patch18 | May 25, 2021 | Oct 8, 2030 | 1613 days remaining | Active |
| 2022.0 | 2022.0.1patch5 | Dec 6, 2022 | Jan 11, 2033 | 2439 days remaining | Active |
| 2022.1 | 2022.1patch4 | Nov 28, 2023 | Jan 11, 2033 | 2439 days remaining | Active |
| 2022.2 | 2022.2patch8 | Jul 9, 2024 | Jan 11, 2033 | 2439 days remaining | Active |
| continuous | Patch 3 | Dec 9, 2025 | Already EOL | Supported | Active |
When a Azure Devops Server version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Azure Devops Server should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →