Azure DevOps Server TFS 2018 · Version Status
Azure DevOps Server TFS 2018 End of Life Date
Azure DevOps Server TFS 2018 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
✓
Azure DevOps Server TFS 2018 is actively supported. EOL date: January 11, 2028.
📅 Get reminded before Azure DevOps Server TFS 2018 reaches EOL on January 11, 2028 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Jan 11, 2028
475 days remaining
Latest Release
2018.3.2patch20
Standard release
Release Date
Nov 15, 2017
Azure DevOps Server TFS 2018 series
Lifecycle detail
Azure DevOps Server 2018 was released on November 15, 2017 and support is scheduled to end on January 11, 2028 — a planned supported lifespan of 10 years and 2 months, in line with the 10 years and 1 month median for Azure DevOps Server releases. Its most recent patch is 2018.3.2patch20, published April 8, 2025.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
All Azure DevOps Server Versions
| Version | Latest | EOL Date | Status |
|---|
| TFS 2005 |
2005.SP2 |
Jul 12, 2016 |
EOL |
| TFS 2010 |
2010.SP1 |
Jul 14, 2020 |
EOL |
| TFS 2012 |
2012.4 |
Jan 10, 2023 |
EOL |
| TFS 2013 |
2013.5 |
Apr 9, 2024 |
EOL |
| TFS 2015 |
2015.4.2patch8 |
Oct 14, 2025 |
EOL |
| TFS 2017 |
2017.3.1patch15 |
Jan 11, 2027 |
Warning |
| → TFS 2018 |
2018.3.2patch20 |
Jan 11, 2028 |
Active |
| 2019 |
2019.0.1patch16 |
Apr 10, 2029 |
Active |
What does Azure DevOps Server TFS 2018 end of life mean?
When Azure DevOps Server TFS 2018 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Azure DevOps Server TFS 2018 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Azure DevOps Server Azure DevOps Server or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Azure DevOps Server TFS 2018 reach end of life?
Azure DevOps Server TFS 2018 reached end of life on January 11, 2028. That is 475 days remaining.
Is Azure DevOps Server TFS 2018 still supported?
Yes, Azure DevOps Server TFS 2018 is currently supported. The EOL date is January 11, 2028.
What should I upgrade to from Azure DevOps Server TFS 2018?
The recommended upgrade from Azure DevOps Server TFS 2018 is
Azure DevOps Server Azure DevOps Server — the latest actively supported version. Check the
Azure DevOps Server full timeline for all supported versions.
What are the security risks of running Azure DevOps Server TFS 2018 past EOL?
When Azure DevOps Server TFS 2018 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Azure DevOps Server should migrate immediately or implement compensating controls.