Azure DevOps: No hosted parallelism has been purchased or granted

Not specified by the original author.

TL;DR

While waiting, or to skip the queue entirely, run the pipeline on a self-hosted agent, which needs no parallelism grant. Do not chase YAML changes; the error is about account entitlement, not pipeline syntax.

Steps

1. Request the free grant through the Microsoft form linked in the thread, which restores one hosted parallel job for private projects (public projects have their own path). While waiting, or to skip the queue entirely, run the pipeline on a self-hosted agent, which needs no parallelism grant. Do not chase YAML changes; the error is about account entitlement, not pipeline syntax.

When to use

You are seeing this: Request the free grant through the Microsoft form linked in the thread, which restores one hosted parallel job for private projects (public projects have their own path). Use this skill when you run into "Azure DevOps: No hosted parallelism has been purchased or granted".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Stack Overflow #68405027 (accepted answer, 86 votes): a brand-new Azure DevOps pipeline fails immediately with No hosted parallelism has been purchased or granted, even though the asker wants no parallelism at all. The accepted answer explains the naming trap: one sequential pipeline counts as one parallel job, and new organizations get zero hosted parallel jobs by default after Microsoft disabled the automatic free grant.

Verified resolution: Request the free grant through the Microsoft form linked in the thread, which restores one hosted parallel job for private projects (public projects have their own path). While waiting, or to skip the queue entirely, run the pipeline on a self-hosted agent, which needs no parallelism grant. Do not chase YAML changes; the error is about account entitlement, not pipeline syntax.

Source URL: https://stackoverflow.com/questions/68405027/how-to-resolve-no-hosted-parallelism-has-been-purchased-or-granted-in-free-tie