Explanation
Why the waste happens and who it affects.
These inefficiencies result in unnecessary cost and delivery friction, especially when pipelines create queues due to limited agent availability.
Billing model
The pricing dimensions that drive this cost.
Azure Pipelines bills by parallel jobs per month, not by execution time. Private projects get one free Microsoft-hosted parallel job (60-minute job limit, 1,800 minutes/month) and one free self-hosted parallel job; each additional Microsoft-hosted or self-hosted parallel job is a monthly charge. Self-hosted agents avoid Microsoft-hosted charges but require infrastructure and maintenance. Public projects are retired and convert to private in 2027.
How to detect
5 checks to find it in your estate.
- Review pipeline job execution history for unnecessary or duplicated stages
- Identify pipelines with high agent usage but low business value
- Check for frequent pipeline runs that could be conditionally suppressed
- Evaluate whether self-hosted agents exist but are underutilized
- Look for consistent agent queue delays, signaling insufficient capacity
How to fix
5 ways to remove the waste.
- Audit and streamline pipelines to remove redundant or unnecessary stages
- Use conditional logic to limit execution of non-critical pipelines
- Prioritize agent capacity for pipelines supporting core or production workloads
- Consider introducing or expanding self-hosted agents for predictable builds
- Monitor and adjust agent pool size to eliminate queue backlogs
Documentation
Vendor references for pricing and configuration.