Azure DevOps started life as Team Foundation Server in 2005 and morphed through Visual Studio Online into its current form. It bundles five products under one roof — Repos, Pipelines, Boards, Artifacts, Test Plans — and is the deeply-rooted default in many .NET shops. Microsoft has been clear that long-term investment is shifting to GitHub, but Azure DevOps remains supported and widely used.
← Back to Cross-Cutting Tools| Service | Purpose |
|---|---|
| Repos | Git hosting (and legacy TFVC centralized VCS). |
| Pipelines | YAML-based CI/CD. Microsoft-hosted or self-hosted agents. Cross-platform. |
| Boards | Work items, backlogs, sprints, kanban — Agile, Scrum, or CMMI templates. |
| Artifacts | Package feeds for NuGet, npm, Maven, Python, universal packages. |
| Test Plans | Manual test case management — uncommon outside enterprise QA. |
You can use any subset. Many teams use Repos + Pipelines and track work in Jira, or use Boards + Pipelines pointed at a GitHub repo.
Microsoft owns both. The public guidance is that greenfield projects should default to GitHub (with GitHub Advanced Security and Actions) and that Azure DevOps remains a supported home for existing investments. New feature work happens on GitHub first.
In practice: if you're starting today and don't have a strong reason to pick ADO, pick GitHub. If you already run ADO, there's no urgent reason to migrate — but expect any "what's new" announcement to land on the GitHub side first.