What are the five main services in Azure DevOps and when do you use each?

Think of Azure DevOps like a modern automobile factory with five specialized departments working in coordination. Azure Boards is the planning office where managers track which cars are in design, assembly, testing, or ready for delivery. Azure Repos is the engineering vault holding all blueprints and design revisions. Azure Pipelines is the assembly line that takes designs from the vault, builds the cars, tests them, and delivers them to dealerships. Azure Test Plans is the quality assurance department running safety inspections. Azure Artifacts is the parts warehouse storing reusable components that multiple car models share. Each department functions independently but their real power emerges when they operate as an integrated system.

Azure Boards provides work item tracking using Agile, Scrum, or CMMI process templates. Teams create Epics, Features, User Stories, and Tasks organized in backlogs and sprint boards. Boards connect directly to code through branch policies that require work item linking on pull requests, creating traceability from business requirements through code changes to deployments. For a payments-api team, a Product Owner creates a User Story describing a new payment validation feature, developers link their feature branches to that story, and the deployment pipeline automatically updates the work item state when the code reaches production. This end-to-end traceability satisfies audit requirements in regulated industries.

Azure Repos hosts Git repositories with enterprise features including branch policies, pull request workflows, and code search across all repositories in the organization. Branch policies enforce code quality gates: minimum reviewer count, successful build validation, linked work items, and comment resolution before merge. Azure Repos supports both centralized and forking workflows and integrates with external Git clients. For organizations migrating from TFS or SVN, Azure Repos provides import tools that preserve history. The key differentiator from GitHub is deeper integration with the other Azure DevOps services and support for TFVC alongside Git for legacy codebases.

Azure Pipelines is the CI/CD engine supporting both YAML-defined and Classic visual designer pipelines. It builds, tests, and deploys applications to any platform including Azure, AWS, GCP, Kubernetes, and on-premises servers. Pipelines support parallel jobs across Microsoft-hosted or self-hosted agents, multi-stage deployments with approval gates, and integration with virtually any build tool or deployment target through a marketplace of 1000+ extensions. The pipeline execution model supports templates for reusability, variable groups for secret management, and environments for deployment tracking and governance.

Azure Test Plans provides structured manual testing, exploratory testing with session capture, and stakeholder feedback collection. Test Plans link test cases to user stories, track test execution across sprint iterations, and generate coverage reports showing which requirements have been verified. For automated testing, Test Plans integrates with pipeline test results to provide unified reporting across both manual and automated test execution. Azure Artifacts hosts NuGet, npm, Maven, Python, and Universal packages with upstream sources that proxy public registries. Artifacts provides versioning, retention policies, and feed permissions that control which teams can publish or consume packages. Together these five services eliminate tool fragmentation and provide a single pane of glass for the entire software delivery lifecycle.

The production gotcha is that organizations often adopt Azure DevOps services piecemeal without leveraging their integration. Teams use Boards without linking work items to code, losing traceability. They use Repos without branch policies, losing quality gates. They use Pipelines without Environments, losing deployment governance. The full value of Azure DevOps emerges when all five services are connected: work items linked to branches linked to pull requests linked to builds linked to deployments, creating an auditable chain from requirement to production that satisfies SOC2, ISO 27001, and regulatory compliance frameworks.