Azure DevOps
Also known as: ADO, VSTS, TFS, Azure Boards, Azure Pipelines, Azure Repos
Azure DevOps (formerly Visual Studio Team Services) is Microsoft's all-in-one DevOps platform.
It combines Boards (Agile work tracking), Repos (Git hosting), Pipelines (CI/CD), Artifacts (package registry), and Test Plans in a single product -- tightly integrated with Microsoft's ecosystem.
Azure DevOps, explained at three levels
At home
Azure DevOps is a collection of tools for software teams. Think of it as a combination of Jira (for tracking tasks), GitHub (for code), and Jenkins (for automated builds) -- integrated into one Microsoft product that works with Azure cloud services.
At work
Enterprises using Microsoft tools often use Azure DevOps to manage their software delivery. Developers track their work in Boards, store code in Repos, run automated tests and deployments with Pipelines, and share packages via Artifacts -- all in one platform with integrated reporting.
At home
Azure Boards supports Scrum, Kanban, and SAFe (Scaled Agile Framework) work item types. Repos provides full Git hosting with branch policies (require PR reviews, status checks before merging). Pipelines uses YAML-based pipeline definitions, supporting multi-stage deployments to Azure or any cloud. Artifacts hosts npm, NuGet, Maven, and Python packages privately.
At work
Azure DevOps integrates with: GitHub (repositories can live in GitHub while Azure DevOps handles Boards and Pipelines), Azure cloud services (App Service, AKS, VM deployments), Microsoft Teams (work item notifications), and hundreds of marketplace extensions. Pipeline service connections allow deploying to AWS, GCP, and on-premises targets, not just Azure.
At home
Azure Pipelines' YAML schema supports stages (group of jobs), jobs (group of steps running on a single agent), and steps (individual tasks). Template references enable shared pipeline logic across projects. Environments track deployment history and provide manual approval gates before production deployments. Checks enforce policies (branch protection, required approvals) at pipeline gate points.
At work
Azure DevOps Server is the self-hosted version for organizations with compliance requirements preventing cloud use. YAML pipelines support Deployment Jobs (with rollback and deployment tracking), Kubernetes jobs (with service account authentication), and Container Jobs (running pipeline steps inside Docker containers). Azure DevOps REST API and CLI enable programmatic pipeline triggering, work item management, and integration with enterprise toolchains.
Real-world examples
At home
Aisha's team switched from Jira + Jenkins to Azure DevOps. She now tracks her sprint tasks in Azure Boards, reviews code in Azure Repos pull requests, and watches CI/CD runs in Azure Pipelines -- all in one browser tab.
At work
Jerome's enterprise uses Azure DevOps for all 50 development teams. Centralized Artifacts hosts shared libraries; a pipeline template library (stored in a separate repo) ensures all teams run security scans. Azure Boards' portfolio features provide management visibility into epics and features across all teams.
Common confusions
- Azure DevOps is only for .NET and Windows development — Azure DevOps supports every language and platform. Python, Node.js, Java, Go, Docker containers, Linux agents, macOS agents, and deployments to AWS and GCP are all natively supported. The .NET heritage is in the history, not the current product.
- Azure DevOps and GitHub are competing products — Microsoft owns both and positions them as complementary. GitHub is the open-source developer platform; Azure DevOps is the enterprise ALM suite. GitHub Actions now competes with Azure Pipelines, but many organizations use GitHub Repos + Azure Pipelines, or Azure Repos + GitHub Actions.
For analysts
Azure DevOps Boards and its reporting features (velocity charts, burndown, cumulative flow) give business analysts visibility into software delivery metrics. BAs in organizations using Azure DevOps can pull sprint data, feature throughput, and release cadence directly from the platform.
History & origin
Azure DevOps evolved from Team Foundation Server (TFS), Microsoft's on-premises ALM (Application Lifecycle Management) tool launched in 2005. The cloud version launched as Visual Studio Online in 2013, renamed Visual Studio Team Services (VSTS), and rebranded as Azure DevOps Services in 2018 when Microsoft separated the product into five modular services. The rebranding reflected Microsoft's pivot toward open-source (Azure DevOps supports GitHub repos and non-Microsoft languages natively).