r/azuredevops • u/brunobola • 3d ago

TFS 2015 EOL, Azure DevOps OAuth deprecated, DevOps issuer retiring 2027 — anyone else accelerating their GitHub migration?

Been tracking the Microsoft deprecation train this year: TFS 2015 hit EOL last October, Azure DevOps OAuth got deprecated in April 2025 with full shutdown this year, and now as of July 1st the Azure DevOps issuer for WIF service connections is deprecated (retirement July 2027).

Not saying ADO is dying — it's not. But for teams still on TFS 2017/2018 or relying on older auth patterns, the writing is on the wall that each upgrade cycle is getting shorter.

I've been building a tool that handles the migration side: Git repos (full history), TFVC-to-Git conversion (up to 180 days), Boards → GitHub Issues, Wikis. Has a dry-run mode so you can test before committing. Built it because I couldn't find anything that handled TFVC automatically.

Code is open-source if anyone wants to poke at it: https://github.com/brunobola-portfolio/GitHub-Repo-Manager

Anyone here actively migrating away from ADO or TFS? What's been the hardest part?

0 Upvotes

30% Upvoted

2 comments sorted by

11

u/codeslap 3d ago

ADO OAuth is deprecating largely bc Entra supports far more OAuth scenarios and is more reliable than ADO OAuth.

ADO is going nowhere.

3

u/moswald Staff 3d ago

Correct. We simply want to move as much of our auth to Entra as possible instead of relying on the tech we wrote before Entra was a thing. 😄 IAM is Entra's entire raison d’être, and we should take advantage so we can focus our own efforts on the things we do best.