Azure DevOps | Request review/removal of 'new customer' restriction on Microsoft-hosted parallel job purchase

Hello Marco Túlio Rangel - Bluepartner,

Greetings! Thanks for raising this question in the Q&A forum.

You are right that this is not a technical fault. The message "As a new customer, you're limited to 1 parallel job" is a billing-side limit applied to the Azure subscription or billing account linked to your Azure DevOps organization. It is not something that Azure DevOps settings, pipelines, or agent configuration can override. It can only be reviewed and lifted by the Azure DevOps backend or billing team through a support case, and other customers with the same message have had it cleared that way. Q&A moderators and community members cannot remove the restriction directly.

Check the billing link first. In Azure DevOps go to Organization settings > Billing and confirm the organization is linked to an active, paid Azure subscription (Pay-As-You-Go, EA, or CSP) and not to a free, trial, sponsorship, or disabled subscription. Then check Organization settings > Pipelines > Parallel jobs and note the current Microsoft-hosted count and the exact error message. Also confirm that the person buying has the Owner or Contributor role on the subscription and is an organization owner.

Check why the count dropped from 2 to 1. Open the billing view in the Azure portal under Cost Management + Billing and confirm that the Azure DevOps parallel job resource for the organization still shows the quantity you purchased. If the quantity is lower than expected, the change may have been triggered by the same billing restriction. Keep screenshots of the Parallel jobs page before and after.

Use the right support type. Because the lock is in billing, open a case as a billing or subscription management request, not as a technical Azure DevOps request. These are available on every support plan at no cost. In the portal go to Help + support > Create a support request, choose Issue type: Billing (or Subscription management), select the subscription linked to the organization, and describe the issue. Include these details so it can be routed correctly:

Organization: https://dev.azure.com/<org-name>
Subscription ID: <subscription-id>
Message: "As a new customer, you're limited to 1 parallel job"
Request: review and remove the new customer limit on Microsoft-hosted parallel jobs
Previous count: 2, current count: 1 (changed on 2026-10-28)
Existing cases: 2610280040002783

Note that the two case numbers in your post are identical, so please double check that there is not a second case number to list. Ask in the case for an exception to the new customer policy and for a written response from the Azure DevOps billing team.

1. Try a different subscription as a workaround. Other users in the community report that linking the organization to a new Pay-As-You-Go subscription and then setting the Microsoft-hosted job count again allowed them to buy the job. Only do this if it is acceptable for your billing structure, because it changes which subscription is charged.
2. Use self-hosted agents while waiting. Self-hosted parallel jobs are priced separately (one is included free, extra ones cost less than Microsoft-hosted jobs), so you can run additional pipelines on your own agents or a scale set agent pool until the Microsoft-hosted limit is lifted. Use pool: name: <your-self-hosted-pool> in your YAML.

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,
Jerald Felix.