Share via

No response to Azure DevOps parallelism grant request — submitted twice

Rudy Lopes | Steelcraft Framing 0 Reputation points
2026-05-18T04:21:12.2466667+00:00

Tags: azure-devops, azure-pipelines

I submitted the free parallelism grant request form (https://aka.ms/azpipelines-parallelism-request) for our Azure DevOps organisation twice and have received no acknowledgement or approval on either submission.

Details:

  • Organisation name: steelcraftgroup
  • First submission: April 21, 2026
  • Second submission: May 5, 2026
  • Region: Australia East
  • Project type: Private

We are a small business (fewer than 5 users) using the free tier. We have a pipeline ready to deploy but cannot run it without at least one parallel job. We have also attempted to raise a support request through the in-product Help and Support channel but were directed to paid support plans only.

Could someone please check the status of our request or advise on the correct path to get this resolved? Happy to provide further details via private message.

Azure DevOps
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Siddhesh Desai 7,055 Reputation points Microsoft External Staff Moderator
    2026-05-22T02:47:04.4166667+00:00

    Hi @Rudy Lopes | Steelcraft Framing

    Thank you for reaching out to Microsoft Q&A.

    The issue you are encountering is expected behavior for new Azure DevOps organizations. Free hosted parallelism (even the single parallel job for private projects) is no longer automatically granted due to abuse prevention controls and instead requires manual approval via the request form. While typically these requests are processed within a few business days, there are known scenarios where requests are delayed or no acknowledgment is sent, especially during high request volumes or backend processing delays. Since you have already submitted the request twice (April 21 and May 5, 2026) and have not received any response, this indicates that your request is likely stuck or not yet processed by the backend team, and you will need to actively follow up or use alternative approaches to unblock your pipeline.

    Refer below points to resolve this issue or this is the workaround:

    Follow up with Azure DevOps free tier support team

    Send an email to the dedicated support mailbox used for parallelism requests:

    Email: azpipelines-freetier@microsoft.com Include your organization name, submission dates, project type, and clearly mention that no acknowledgment has been received. This is the most effective way to get your request reviewed manually.

    Raise a ticket on Developer Community

    https://developercommunity.azure.com/AzureDevOps

    Since in-product support requires a paid plan, you can raise this issue here:

    Visual Studio Developer Community Provide all details (organization name, dates, screenshots if possible). These tickets are monitored by Microsoft engineers and can help escalate internally when requests are stuck.

    Use a self-hosted agent as a temporary workaround

    You can configure a self-hosted agent which does not require parallelism approval and works immediately.

    High-level steps:

    Go to Project Settings → Agent Pools → Add pool (Self-hosted)

    Download the agent and configure it on your V

    mkdir myagent && cd myagent 
# Download agent package (from portal) 
tar zxvf <agent-package>.tar.gz 
./config.sh 
./run.sh

    Update your YAML pipeline:

    pool:
  name: <your-self-hosted-pool>

    Purchase 1 parallel job

    If your deployment is time-sensitive, you can purchase 1 Microsoft-hosted parallel job from:

    • Organization Settings → Billing → Parallel Jobs

    This enables pipelines immediately and you can later revert if the free grant is approved.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-05-18T04:21:30.9166667+00:00

    Parallelism grant requests for new Azure DevOps organizations are processed manually and can take several business days. There is no automatic acknowledgement beyond the form submission itself.

    Key points from the documented process:

    1. New organizations no longer receive free concurrent pipelines automatically. This applies to both public and private projects in new organizations.
    2. To get the free grant, the only supported path is to submit the Azure DevOps Parallelism Request form. The request is then reviewed by the Azure DevOps team.
    3. The documentation explicitly notes that:
      • The free grant of parallel jobs for public projects and for certain private projects in new organizations is temporarily disabled by default.
      • Requests can take several business days to process, and during some periods processing can take longer.
    4. Until the grant is approved, pipelines in the organization will fail with an error such as No hosted parallelism has been purchased or granted when using Microsoft-hosted agents.

    Given this, the correct path is:

    1. Ensure that the request form was completed with all required details:
      • Name
      • Azure DevOps organization name
      • Whether the grant is for public or private projects
      • For public projects: repository links and a brief project description
    2. Wait for the engineering team to complete review. The documentation states that processing may take several business days and can be longer during busy periods.
    3. As an alternative to waiting for the free Microsoft-hosted parallelism grant, consider:
      • Purchasing additional parallel jobs as described in the parallel jobs licensing documentation.
      • Using self-hosted agents, where limits are governed by the number of agents rather than the free Microsoft-hosted grant.

    Once the request is approved, the free parallel job grant will appear under Project settings → Parallel jobs, and pipelines using Microsoft-hosted agents should start running without the “no hosted parallelism” error.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.