Azure Pipelines pricing in 2026
./azure-pipelines --parallel-jobs --not-per-minute
Azure Pipelines is priced by concurrency, not by the minute. Every organisation gets one free Microsoft-hosted parallel job with 1,800 minutes a month (private projects), plus one free self-hosted job. Above that you buy parallel jobs: $40/month per extra Microsoft-hosted job or $15/month per extra self-hosted job, both with unlimited minutes. Because paid lanes have no minute cap, a team needing three concurrent Microsoft-hosted jobs pays 2 x $40 = $80/month (one is free), which is why Azure stays cheap at high build volume.
Azure Pipelines is the CI/CD half of Azure DevOps, Microsoft's older DevOps suite that also includes Boards, Repos and Artifacts. Its pricing model is the outlier in this comparison: where GitHub Actions, GitLab CI and Bitbucket Pipelines all meter build minutes, Azure sells parallel jobs, which are lanes of concurrency with no minute cap on the paid tier. That single design choice makes Azure unusually cheap for teams with high build volume but modest concurrency, and it changes how you should think about the bill. This page works through the free tier, what a parallel job actually is, what real teams pay, and the 2027 public-projects retirement that is quietly ending free open-source CI on Azure.
Pricing here comes from the public Azure DevOps Services pricing page and the Microsoft Learn parallel-jobs documentation (doc last updated June 2026), verified 4 August 2026 (free tier 1 Microsoft-hosted job / 1,800 min, $40 per extra Microsoft-hosted job, $15 per extra self-hosted job). Check the live pages before committing, as rates and grants change.
The parallel-job price list
| Job type | Free tier | Paid price | Minutes on paid |
|---|---|---|---|
| Microsoft-hosted | 1 job · 1,800 min/mo | $40 / job / mo | Unlimited (360 min/run cap) |
| Self-hosted | 1 job + 1 per VS Enterprise sub | $15 / job / mo | Unlimited (no time limit) |
# The Microsoft-hosted free grant (1,800 min/mo, 60-minute per-run cap) requires linking the org to an Azure subscription. The self-hosted free tier is granted automatically and adds one lane per active Visual Studio Enterprise subscriber. New organisations cap at 25 Microsoft-hosted parallel jobs before you must contact support. Source: Azure DevOps Services pricing page and Microsoft Learn parallel-jobs doc, verified 4 August 2026.
Concurrency, not minutes: why the model matters
A parallel job is a lane in the pool. One lane runs one pipeline job at a time; five lanes run five at once. You can queue as many pipelines as you want, and the parallel-job count only decides how many run simultaneously instead of waiting. Microsoft's own sizing rule is roughly one parallel job for every four to five developers. That means a 20-person engineering org often runs comfortably on four or five parallel jobs.
The consequence for the bill is large. On a per-minute platform, doubling your build volume doubles the metered cost. On Azure, doubling build volume changes nothing as long as your concurrency need is unchanged, because paid parallel jobs carry unlimited minutes. A team running 300,000 build minutes a month through three concurrent Microsoft-hosted jobs pays for two paid lanes ($80) plus the free one, full stop. The same 300,000 minutes on GitHub Actions or Bitbucket Pipelines would be a four-figure metered bill. Where Azure loses is bursty, high-concurrency workloads: if you need ten lanes for a short window each day, you pay for ten lanes all month.
What real teams pay
These map team size to a typical concurrency need using Microsoft's one-lane-per-four-to-five-developers rule, priced at the published parallel-job rates. Minutes do not enter the maths on paid lanes because they are unlimited. Treat them as planning anchors, not quotes.
Up to 5 developers whose builds fit inside 1,800 Microsoft-hosted minutes a month run on the free parallel job for nothing, or use the free self-hosted lane on their own hardware for unlimited minutes.
Around four parallel jobs at 20 developers: one free plus three paid Microsoft-hosted lanes at $40 = $120 a month, with unlimited build minutes. Self-hosting some lanes at $15 each cuts this further.
Roughly ten parallel jobs: one free plus nine paid Microsoft-hosted at $40 = $360 a month for unlimited minutes. Mixing in self-hosted lanes at $15, or running heavy jobs on your own agents, is where large Azure shops trim the bill.
# Figures are this site's own model: parallel-job counts from Microsoft's one-lane-per-4-5-developers rule, multiplied by the published $40 (Microsoft-hosted) rate, less the one free lane. Your real concurrency need depends on build duration and trigger patterns. Azure DevOps Basic user licences (first 5 free, then $6/user/mo) are separate if you also use Boards and Repos.
The 2027 public-projects retirement
Azure DevOps used to give public projects a generous free grant: ten Microsoft-hosted parallel jobs with unlimited minutes, aimed at open-source. That door is closing. Microsoft has retired public projects: new public projects can no longer be created, and existing public projects keep their free parallelism only until they convert to private in 2027. If you are planning open-source CI, do not build it on Azure Pipelines expecting free public-project compute. GitHub Actions, also Microsoft-owned, still offers unlimited free minutes on public repositories, and is where Microsoft is steering open-source workloads.
Plenty of third-party pricing pages still quote the old ten-free-jobs-for-public-projects allocation. Treat that as stale: the grant survives only on legacy public projects and only until the 2027 conversion. For a live account started today, the numbers that matter are the private-project free tier (one Microsoft-hosted lane, 1,800 minutes) and the paid parallel-job rates above.
When Azure Pipelines is the right pick
Azure Pipelines fits teams already inside the Microsoft ecosystem, especially those on Azure DevOps for Boards and Repos, and teams with high build volume but modest concurrency. The unlimited-minutes-per-lane model means a busy backend team can run enormous monthly build volume for a flat handful of $40 fees, which no per-minute platform can match at that scale. It also handles Windows, Linux and macOS Microsoft-hosted agents, and integrates cleanly with Azure deployment targets.
It is a weaker pick for teams whose source of truth is GitHub, where running GitHub Actions against the same repo avoids cross-service friction; for open-source projects, now that the public-project free grant is being retired; and for bursty workloads that need high concurrency in short windows, where paying for lanes all month is wasteful. Compare the metered alternatives in the full platform comparison, and see how the per-minute model works on the GitHub Actions free tier and Bitbucket Pipelines.
Related platforms and comparisons
Frequently Asked Questions
# click any question to expand