Azure DevOps Server end of life dates

End-of-life and end-of-support dates for every Azure DevOps Server version ReleaseBytes tracks, updated nightly. The latest release is 2022.2patch10.

Want a warning before a version expires? Set up a free EOL alert — email or Slack, at 90, 30 and 7 days out.

Version Released End of life Status Extended support
2022.2 9 Jul 2024 11 Jan 2033 2371 days left
2022.1 28 Nov 2023 11 Jan 2033 2371 days left
2022.0 6 Dec 2022 11 Jan 2033 2371 days left
2020.1 25 May 2021 8 Oct 2030 1545 days left
2020.0 25 Aug 2020 8 Oct 2030 1545 days left
2019.1 20 Aug 2019 10 Apr 2029 999 days left
2019.0 5 Mar 2019 10 Apr 2029 999 days left
2018 15 Nov 2017 11 Jan 2028 544 days left
2017 16 Nov 2016 11 Jan 2027 179 days left
2015 30 Jul 2015 14 Oct 2025 end of life
2013 15 Jan 2014 9 Apr 2024 end of life
continuous 9 Dec 2025 no date

Frequently asked questions

When does Azure DevOps Server 2022.2 reach end of life?

Azure DevOps Server 2022.2 reaches end of life on 11 January 2033.

When does Azure DevOps Server 2022.1 reach end of life?

Azure DevOps Server 2022.1 reaches end of life on 11 January 2033.

When does Azure DevOps Server 2022.0 reach end of life?

Azure DevOps Server 2022.0 reaches end of life on 11 January 2033.

When does Azure DevOps Server 2020.1 reach end of life?

Azure DevOps Server 2020.1 reaches end of life on 8 October 2030.

When does Azure DevOps Server 2020.0 reach end of life?

Azure DevOps Server 2020.0 reaches end of life on 8 October 2030.

When does Azure DevOps Server 2019.1 reach end of life?

Azure DevOps Server 2019.1 reaches end of life on 10 April 2029.

Which Azure DevOps Server versions are still supported?

Currently supported Azure DevOps Server versions: 2022.2, 2022.1, 2022.0, 2020.1, 2020.0, 2019.1, 2019.0, 2018, 2017, continuous. The latest release is 2022.2patch10.

How can I get Azure DevOps Server end-of-life alerts?

ReleaseBytes sends free email or Slack alerts 90, 30 and 7 days before a tracked version reaches end of life, and its GitHub App can open an issue in your repository when something you depend on is close to EOL.