The server runs fine. That is not the same as supported.
Most people arrive at this page needing a date for a risk register, a security review, or a renewal conversation. The dates are below, first, verified against Microsoft’s lifecycle pages. What to do about them comes after.
One word matters on this page. Azure DevOps Server is the on-premises product, the successor to TFS. Azure DevOps Services is Microsoft's cloud. Check which one you are on before picking a path.
The dates
| Product | Mainstream support ended | All support ends | Where that leaves you |
|---|---|---|---|
| TFS 2015 and older | 13 Oct 2020 | Ended 14 Oct 2025 | Out of support entirely. No patches at any price. |
| TFS 2017 | 11 Jan 2022 | 11 Jan 2027 | Months away. If a move needs budget, this is the year to ask. |
| TFS 2018 | 10 Jan 2023 | 11 Jan 2028 | A real window, but a finite one. |
| Azure DevOps Server 2019 | 9 Apr 2024 | 10 Apr 2029 | Security fixes only. |
| Azure DevOps Server 2020 | 14 Oct 2025 | 8 Oct 2030 | Security fixes only. |
| Azure DevOps Server 2022 | 11 Jan 2028 | 11 Jan 2033 | Fully supported. This is the current upgrade target. |
Dates are Microsoft’s published lifecycle dates ( lifecycle pages , Pacific time). Check your exact version and update level there.
Three things “out of support” means in practice, without any theatre: no more security patches for the server, or for the aging SQL Server and Windows underneath it. A finding that reappears in every audit until the server is gone. And a shrinking pool of people who still know how to operate it.
The five paths off the list
Most of these do not involve paying us. That is not generosity, it is the honest shape of the problem.
1. Upgrade in place. If your estate must stay on your own infrastructure, the answer is not a migration at all: it is Azure DevOps Server 2022. Supported until 2033, problem solved. Start with Microsoft’s upgrade documentation . If you want experienced hands alongside the upgrade, ask .
2. Move everything to the cloud, byte for byte. Microsoft’s Data Migration Tool lifts one collection into one new Azure DevOps Services organisation, with full fidelity and no modifications. It is the first option we test on every cloud move. One catch that surprises almost everyone: it only accepts servers on one of the two most recent releases . A TFS 2015 or 2017 box cannot leave directly. It has an upgrade chain to climb first, which turns “we’ll just import it” into a multi-step project with its own timeline. Full requirements and surprises: the data import, honestly .
3. Move what matters, leave the rest. Fifteen years of dead projects, abandoned experiments, and test suites nobody remembers do not have to come with you. End of support is the one moment the organisation will grant permission to leave them behind. A selective move takes the projects that are alive, with their history, and closes the door on the rest. That is replay-based tooling, not byte-perfect, with the differences named up front. It is also where we do most of our work: start with a migration assessment .
4. Retire it. Some of these servers hold nothing but the archive of a finished product. If nobody writes to it, the honest path may be to export what compliance requires, take a final backup, and decommission. No migration at all. If you are unsure whether that is safe for your estate, that is a conversation , not an engagement.
5. Accept the risk, explicitly. Running unsupported is a choice organisations do make. Made deliberately, documented, with the finding owned by someone senior, it is at least an honest position. Made by default, because nobody asked, it is how this page ends up being read during an incident.
If a move off one of these servers was already attempted and is now stalled or half-done, that is a different starting point: a migration rescue .
This is not for you if you have a single project, matching process templates, and no test plans. Take path 2 or the open-source tools and their docs , and come back if it gets complicated.
Taking this upstairs
If you need to turn this page into a decision, the sentence that works is: “The server is out of support on [date]. Here are the five options and what each costs.” An assessment turns that sentence into a plan with a fixed quote: your versions, your estate, measured, with the path chosen on evidence.
Need the plan behind the date?
Tell me your version, collection count, and rough size. I'll tell you which of the five paths fits and what it would take. If the answer is an upgrade or Microsoft's import, that's what you'll hear.
Get in touch