Cross-Cutting Tools Deep Dive · 5 of 6

Azure DevOps — Microsoft's Full ALM Suite

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.

MicrosoftPipelinesBoardsTFVCEnterprise
← Back to Cross-Cutting Tools
The Five Services

What's Inside

ServicePurpose
ReposGit hosting (and legacy TFVC centralized VCS).
PipelinesYAML-based CI/CD. Microsoft-hosted or self-hosted agents. Cross-platform.
BoardsWork items, backlogs, sprints, kanban — Agile, Scrum, or CMMI templates.
ArtifactsPackage feeds for NuGet, npm, Maven, Python, universal packages.
Test PlansManual 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.

Where It Shines

Why Pick It

  • Native .NET / Windows story. First-class MSBuild, NuGet feeds, Windows agents, Visual Studio integration.
  • Mature on-prem option. Azure DevOps Server is the self-hosted edition for regulated and air-gapped environments.
  • Enterprise governance. Granular permissions, audit logs, AD/Entra integration that maps cleanly to corporate IT.
  • Pipelines are very capable. YAML pipelines, environments with approvals, deployment groups, variable groups linked to Key Vault.
The Direction

Azure DevOps vs GitHub

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.

Continue

Other Cross-Cutting Tools