Answers: <p>This is a good question because you would assume you could do what you are after, but as far as I know you can't yet. From the docs on <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/licensing/concurrent-jobs?view=azure-devops#sharing-of-parallel-jobs-across-projects-in-a-collection" rel="nofollow noreferrer">sharing of parallel jobs across projects in a collection</a></p>
  
  <blockquote>
    <p>Currently, there isn't a way to partition or dedicate parallel job capacity to a specific project or agent pool.</p>
  </blockquote>
  
  <p>I considered trying to do buckets via capabilities on a subset of my agents, and then companion demands in the pipelines, but that will not work either because <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/process/demands?view=azure-devops&amp;tabs=yaml" rel="nofollow noreferrer">hosted pipelines don't work with demands</a>.  </p>
  
  <p>In my case we had some greedy pipelines that fan out into multiple parallel jobs, that we had to update to run sequentially with <code>dependsOn</code> for each job. I think if your case is relatively simple you could potentially check the queue length or number of running builds in a first stage but that could get complex and might be tough to scale. </p>
  
  <p>Hopefully this feature gets added soon. I will look to see if I can find one to vote up on the developer community forums. I am also interested in other ideas on how to solve for this issue! </p>
  
  <p>Edit found a feature <a href="https://developercommunity.visualstudio.com/idea/721308/limit-parallel-jobs-for-a-pipelinefolder-of-pipeli.html" rel="nofollow noreferrer">vote on it here</a> </p>
  
Answers: CC BY-SA 4.0
Answers: 2020-01-31T21:39:32.303Z
Answers: +1 for the feature voting link!
Answers: dbJones
Answers: CC BY-SA 4.0
Answers: 2020-01-30T00:52:55.543Z
Answers: 2020-01-30T01:02:14.757Z
Answers: 2020-01-30T01:02:14.757Z
Answers: Eric Smith
Body: <p>I am using Azure DevOps.</p>
  
  <p>I have 5 Microsoft-hosted agents. And 10 pipelines.
  One pipeline in particular can get a bit grabby, so I want to restrict it to use just 2 agents.</p>
  
  <p>But I want my other 9 pipelines to have access to the 3 remaining agents. </p>
  
  <p>I figure Agent Pools is the right way to solve this. By default, Azure DevOps sets us up with 1 single "Azure Pipelines" pool with our self-hosted agents. I would like to split this into 2 pools.</p>
  
  <p>However, when I go to "create new pool" I only get the option to add "self-hosted" agents.</p>
  
  <p>How do I create a new Agent Pool with some of my existing Microsoft-hosted agents?</p>
  
Tags: <azure-devops><azure-pipelines>
Title: Azure DevOps - how to create a 2nd Microsoft-hosted Agent Pool
UserDisplayName: dbJones
ThreadText: # Azure DevOps - how to create a 2nd Microsoft-hosted Agent Pool
  
  (Asked by: username_0 on 2020-01-29)
  
  I am using Azure DevOps.
  
  I have 5 Microsoft-hosted agents. And 10 pipelines.
  One pipeline in particular can get a bit grabby, so I want to restrict it to use just 2 agents.
  
  But I want my other 9 pipelines to have access to the 3 remaining agents.
  
  I figure Agent Pools is the right way to solve this. By default, Azure DevOps sets us up with 1 single "Azure Pipelines" pool with our self-hosted agents. I would like to split this into 2 pools.
  
  However, when I go to "create new pool" I only get the option to add "self-hosted" agents.
  
  How do I create a new Agent Pool with some of my existing Microsoft-hosted agents?
  
  **Tags:** azure-devops, azure-pipelines
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-01-30. Score: 1 | Accepted answer
  
  This is a good question because you would assume you could do what you are after, but as far as I know you can't yet. From the docs on [sharing of parallel jobs across projects in a collection](https://docs.microsoft.com/en-us/azure/devops/pipelines/licensing/concurrent-jobs?view=azure-devops#sharing-of-parallel-jobs-across-projects-in-a-collection)
  
  > Currently, there isn't a way to partition or dedicate parallel job capacity to a specific project or agent pool.
  
  I considered trying to do buckets via capabilities on a subset of my agents, and then companion demands in the pipelines, but that will not work either because [hosted pipelines don't work with demands](https://docs.microsoft.com/en-us/azure/devops/pipelines/process/demands?view=azure-devops&tabs=yaml).
  
  In my case we had some greedy pipelines that fan out into multiple parallel jobs, that we had to update to run sequentially with `dependsOn` for each job. I think if your case is relatively simple you could potentially check the queue length or number of running builds in a first stage but that could get complex and might be tough to scale.
  
  Hopefully this feature gets added soon. I will look to see if I can find one to vote up on the developer community forums. I am also interested in other ideas on how to solve for this issue!
  
  Edit found a feature [vote on it here](https://developercommunity.visualstudio.com/idea/721308/limit-parallel-jobs-for-a-pipelinefolder-of-pipeli.html)
  
  > **Comments:**
  > **username_0**: +1 for the feature voting link!  
  
  ---
  
  