Cannot increase number of MS Hosted Parallel Jobs in Azure DevOps

Question

We have been using Azure DevOps for more than 5 years.

We have more than 25 V-Studio developer accounts and 20 Basic accounts.

I am trying to increase the number of MS Hosted CI/CD paid parallel jobs to more than 4, but I get the following error. This makes no sense, since the configuration is already at 4, and we are not a "new" customer.

As a new customer, you're limited to 1 parallel job. Check back again soon to increase MS Hosted CI/CD.

Answer 1

Hi @Brian Jones ,

As a new customer, you're limited to 1 parallel job. Check back again soon to increase MS Hosted CI/CD.

Azure DevOps gives private projects a 1-job free tier, but it no longer auto-grants that when you spin up a new org. Buying your first paid Microsoft-hosted job simply removes the 60-min timeout on that one job it doesn’t give you a second concurrent slot.

How to actually get 6+ paid parallel jobs

Your organization must be billed via a Pay-As-You-Go or Enterprise Subscription not just VS credits with a spending limit. You need to be in the Project Collection Administrators group.

In Azure DevOps go to: https://dev.azure.com/‹your-org› =>Organization settings (gear) =>Pipelines =>Parallel jobs. Click Change or purchase parallel jobs if you haven’t ever, set the total number of jobs you want, and click Save. Behind the scenes you’re purchasing exactly the count you enter. So, if you have 4 and you enter 6, you're buying 2 more. It can take up to 30 minutes to show up.

New organizations have a default cap of 25 Microsoft-hosted parallel jobs. If you genuinely need >25 concurrently, file a limit-increase request:

• Open a general Azure support ticket and ask to raise your MS-hosted parallel job quota. Provide your organization name, region and desired total.

Free-tier grant for private projects: If you ever need that extra 1-job free tier restored, fill out the parallelism request form to get the grant back: https://aka.ms/azpipelines-parallelism-request. That’s separate from paid purchases and typically takes 4–5 business days to approve.

Hope this helps!

---

If the resolution was helpful, kindly take a moment to click on and click on Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 2

The error message about being “limited to 1 parallel job as a new customer” conflicts with the documented limits and with the fact that the organization already has 4 Microsoft-hosted parallel jobs. The documented behavior is:

• New organizations get a maximum limit of 25 Microsoft-hosted parallel jobs by default, and this limit can be increased by contacting support.
• Parallel jobs are purchased at the organization level and shared by all projects.
• The “new customer” wording is related to capacity and free-grant behavior, not to long‑standing organizations like the one described.

Given that the organization is older than 5 years and already has 4 paid Microsoft-hosted parallel jobs, this behavior indicates a platform-side restriction or capacity issue that cannot be resolved from the UI alone. The supported path is:

1. Verify current limits and usage
   • In Azure DevOps, go to Organization settings → Pipelines → Parallel jobs.
   • Confirm the current number of Microsoft-hosted parallel jobs and whether any warning or limit banner is shown.
   • Optionally, use the Pool consumption report on the Analytics tab of the Microsoft-hosted agent pool to confirm that jobs are hitting the concurrency limit and justify the need for more capacity.
2. Ensure prerequisites are met
   • Confirm that billing is correctly set up for the organization.
   • Confirm that the account used to change the setting is in the Project Collection Administrators group.
3. Attempt to change the quantity again
   • In Organization settings → Pipelines → Parallel jobs, select Change for Microsoft-hosted jobs.
   • Enter the desired higher quantity and save.
   • If the same “new customer” error appears and blocks the change, treat this as a service-side limitation rather than a configuration problem.
4. Escalate through Azure DevOps support
   • Because the documentation states that new organizations have a maximum of 25 Microsoft-hosted parallel jobs and that higher limits require contacting support, and because the organization is not new, the only supported way to remove this incorrect “new customer” restriction is to open a support case with Azure DevOps.
   • In the support request, include:
     • Organization URL.
     • Screenshot of the Parallel jobs page showing 4 existing Microsoft-hosted jobs.
     • The exact error text: “As a new customer, you're limited to 1 parallel job. Check back again soon to increase MS Hosted CI/CD.”
     • Confirmation that billing is active and that the requester is a Project Collection Administrator.
   • Ask support to:
     • Correct the organization’s Microsoft-hosted parallel job limit so it matches the documented default (up to 25) or the requested higher value.
     • Remove any incorrect “new customer” flag or capacity restriction applied to the organization.

Once support adjusts the limit, return to Organization settings → Pipelines → Parallel jobs and increase the Microsoft-hosted parallel jobs to the desired number. It can take up to 30 minutes for new parallel jobs to become active.

---

References:

• Configure and pay for parallel jobs
• Troubleshoot pipeline failure to start
• Azure Pipelines agents
• What is Azure Pipelines?