What it does
Azure Pipelines is the CI/CD service in Azure DevOps. A pipeline definition groups work into stages, jobs, and steps, and jobs can run on Microsoft-hosted or self-hosted agents. Parallel-job capacity is shared at the Azure DevOps organization level, so it affects how many pipelines can run at once across projects.
Start with a YAML pipeline that separates build, test, and deployment into stages or jobs. Choose a Microsoft-hosted agent when you want Microsoft to supply the runner, or a self-hosted agent when the job needs local tools, private network access, or a custom machine. Use job dependencies to sequence the workflow; the YAML schema treats stages as the major divisions and supports jobs or steps when a smaller pipeline is enough.
The free parallel-job allowance is one Microsoft-hosted job with 1,800 minutes per month and one self-hosted job with unlimited minutes. Additional jobs are charged monthly, and the Microsoft-hosted paid job has a 360-minute per-job limit. Organization concurrency is shared across projects, so a busy pipeline can queue other work. The free grant requires linking the organization to a valid Azure subscription.
Strengths
- YAML can model pipelines as stages, jobs, and steps.
- Microsoft-hosted and self-hosted agents cover managed and custom build environments.
- Free parallel-job allowances are available for evaluation.
Watch out for
- Parallel capacity is shared across projects in the organization, so jobs may queue.
- The free parallel-job grant requires a linked Azure subscription.
- Microsoft-hosted paid jobs have a 360-minute per-job limit.
Best for
- Teams building, testing, and deploying applications across multiple stages
- Organizations already using Azure DevOps and needing hosted or private runners
Sources
- Azure Pipelines | Microsoft Azure (Oct 25, 2026)
- Pipeline definition | Microsoft Learn (Oct 25, 2026)
- Configure and pay for parallel jobs | Microsoft Learn (Oct 25, 2026)
- Azure DevOps Services Pricing | Microsoft Azure (Oct 25, 2026)