Azure DevOps Services Overview

Azure DevOps is a cloud-hosted suite of developer tools from Microsoft that covers the full software delivery lifecycle. It combines project management, source control, build and release automation, test management, and artifact storage into one integrated platform. Teams using Azure DevOps can plan sprints, commit code, run automated builds, deploy to production, and track quality metrics — all from a single service with deep integrations to other Azure services.

Azure DevOps comprises five services: Azure Boards (Agile work item tracking — epics, stories, tasks, bugs), Azure Repos (unlimited Git repositories or legacy TFVC), Azure Pipelines (CI/CD automation for any language, platform, and cloud), Azure Test Plans (manual and exploratory testing, test cases, and quality metrics), and Azure Artifacts (universal package feed for NuGet, npm, Maven, Python, and container images).

The Azure DevOps hierarchy starts with an organisation — the top-level container associated with your Azure AD tenant, typically named after your company. Inside an organisation you create projects, each representing a software product or team. Each project gets its own Boards, Repos, Pipelines, Test Plans, and Artifacts. Access control, billing, and settings are configured at the organisation level but can be overridden per project.

Azure Boards supports three process templates: Basic (simple Issues and Tasks), Agile (Epics, Features, User Stories, Tasks, Bugs), and Scrum (Epics, Features, Product Backlog Items, Tasks, Bugs). Work items flow through configurable states. The Kanban board visualises in-progress work; sprint backlogs plan capacity; backlogs prioritise all unstarted work. Link work items to commits, pull requests, and test cases for full traceability.

Azure Repos provides unlimited private Git repositories with branch policies, pull request workflows, and code review tools. Branch policies enforce quality gates on protected branches — requiring minimum reviewers, passing build validation, linked work items, and comment resolution before merging. Each repository integrates directly with Azure Pipelines, triggering builds and deployments automatically on branch push or pull request.

Azure Pipelines is a CI/CD service that builds, tests, and deploys applications written in any language to any platform — Azure, AWS, GCP, on-premises. Pipelines are defined in YAML files stored alongside code in the repository. Key concepts include stages (logical phases like Build, Test, Deploy), jobs (parallel execution units), and steps (individual tasks). Azure Pipelines provides 1,800 free build minutes per month for open-source projects.

Azure Artifacts hosts versioned package feeds for NuGet (.NET), npm (Node.js), Maven (Java), pip (Python), and Universal Packages (arbitrary binaries). Share internal libraries between projects or teams without publishing to public registries. Upstream sources proxy public registries (npmjs.com, nuget.org) through your feed, giving you a single endpoint for all packages and the ability to audit and cache dependencies.

Pipelines run on agents — VMs or containers that execute pipeline jobs. Microsoft-hosted agents are fully managed, pre-configured VMs (Ubuntu, Windows, macOS) provided by Microsoft — no setup required. Self-hosted agents run on your own infrastructure (on-premises or Azure VMs), giving you control over the environment, pre-installed tools, and access to private networks. Use self-hosted agents when builds need VNet access, specialised hardware, or faster startup than cloud VMs provide.

Environments in Azure Pipelines represent deployment targets (Dev, Staging, Production) and track deployment history. You can attach approval and check gates to environments — a deployment to Production requires manual sign-off from a release manager. Other checks include business hours gates (only deploy between 09:00-17:00), wait timers, and Azure Monitor alert checks (don't deploy if there are active critical alerts). This gives teams governance over high-risk production deployments.

Service connections store authenticated connections to external services (Azure subscriptions, GitHub, Docker Hub, SonarQube, Kubernetes clusters) so pipelines can use them without embedding credentials in YAML. The Azure Resource Manager service connection uses a service principal or managed identity to deploy Azure resources. All credentials are encrypted and scoped to the project or pipeline, preventing credential exposure in pipeline logs.

Microsoft owns both Azure DevOps and GitHub, and both support CI/CD. Azure DevOps is preferred in enterprises deeply invested in Microsoft tools, needing Azure Boards, Test Plans, or Artifacts. GitHub is preferred for open-source projects, developer-centric workflows, and when teams already use GitHub repositories. GitHub Actions is GitHub's CI/CD platform. Azure Pipelines integrates with both Azure Repos and GitHub — you can use Azure Boards and Artifacts with GitHub repositories.

Test your understanding of Microsoft Azure Fundamentals (AZ-900) concepts from this lesson.

In this lesson you learned: Azure DevOps provides five integrated services covering planning (Boards), source control (Repos), CI/CD (Pipelines), testing (Test Plans), and package management (Artifacts), environments with approvals gate high-risk deployments, and service connections securely store external service credentials for pipeline use. Next up we explore building a CI pipeline with Azure Pipelines.