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.

Context: 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.

## Matched source
Source: Published skill
Original query: "Azure DevOps: No hosted parallelism has been purchased or granted"
Key terms: azure, been, devops, granted, hosted, parallelism, purchased