I was able to resolve the issue by submitting a support ticket to Azure DevOps Support. The problem was a deleted service account in Azure DevOps; the account can only be added back with backend access (Azure DevOps Support).
Microsoft-hosted agent does not pick up jobs – stuck at "Acquiring an agent from the cloud"
Our Azure Pipelines jobs have been stuck indefinitely in the queue. The job never starts processing, even though a Microsoft-hosted agent is shown as online.
What we see:
- Pool: Azure Pipelines, Image: ubuntu-latest
- Agent shows as "Online" with status "Running build" but never actually starts processing
- Log shows: "Pool provider seems slow, we notified pool provider... still agent has not started processing it"
- Job stays stuck after the "Job preparation parameters" phase completes
What we've tried:
- Cancelling and re-running multiple times
- Minimal pipeline with only
echo "Agent is alive"– same issue - Verified parallel jobs: 1 Microsoft-hosted parallel job available (Free tier, 0/1800 minutes consumed)
What we see:
- Pool: Azure Pipelines, Image: ubuntu-latest
- Agent shows as "Online" with status "Running build" but never actually starts processing
- Log shows: "Pool provider seems slow, we notified pool provider... still agent has not started processing it"
- Job stays stuck after the "Job preparation parameters" phase completes
What we've tried:
- Cancelling and re-running multiple times
- Minimal pipeline with only
echo "Agent is alive"– same issue - Verified parallel jobs: 1 Microsoft-hosted parallel job available (Free tier, 0/1800 minutes consumed)
Job-log:
##[error]The request: 6177 was abandoned due to an infrastructure failure. Notification of assignment to an agent was never received.
Pool: Azure Pipelines
Image: ubuntu-22.04
Started: Feb 10 at 2:58 PM
Duration: 22d 20h 46m
Job preparation parameters
ContinueOnError: False
TimeoutInMinutes: 60
CancelTimeoutInMinutes: 5
Expand:
MaxConcurrency: 0
########## System Pipeline Decorator(s) ##########
Begin evaluating template 'system-pre-steps.yml'
Evaluating: eq('true', variables['system.debugContext'])
Expanded: eq('true', Null)
Result: False
Evaluating: resources['repositories']['self']
Expanded: Object
Result: True
Evaluating: not(containsValue(job['steps']['*']['task']['id'], '6d15af64-176c-496d-b583-fd2ae21d4df4'))
Expanded: not(containsValue(Object, '6d15af64-176c-496d-b583-fd2ae21d4df4'))
Result: True
Evaluating: resources['repositories']['self']['checkoutOptions']
Result: Object
Evaluating: pair['key']
Result: 'fetchDepth'
Evaluating: pair['value']
Result: '1'
Finished evaluating template 'system-pre-steps.yml'
********************************************************************************
Template and static variable resolution complete. Final runtime YAML document:
steps:
- task: 6d15af64-176c-496d-b583-fd2ae21d4df4@1
inputs:
repository: self
fetchDepth: 1
########## ms.advancedsecurity-tasks.dependency-scanning-decorator ##########
Begin evaluating template 'assets/dependency-scanning-injection-decorator.yml@'
Evaluating: and(or(eq(resources['repositories']['self']['ref'], resources['repositories']['self']['defaultBranch']), and(eq(variables['build.reason'], 'PullRequest'), eq(variables['system.pullrequest.targetbranch'], resources['repositories']['self']['defaultBranch']))), or(eq(resources['repositories']['__designer_repo']['ref'], resources['repositories']['__designer_repo']['defaultBranch']), and(eq(variables['build.reason'], 'PullRequest'), eq(variables['system.pullrequest.targetbranch'], resources['repositories']['__designer_repo']['defaultBranch']))), or(eq(resources['repositories']['self']['type'], 'Git'), eq(resources['repositories']['__designer_repo']['type'], 'Git')), eq(variables['build.advancedSecurityEnabled'], 'true'), eq(variables['build.dependencyScanningInjectionEnabled'], 'true'))
Expanded: and(or(eq('refs/heads/test/marc/azure-pipeline', 'refs/heads/main'), and(eq('Manual', 'PullRequest'), eq(variables['system.pullrequest.targetbranch'], resources['repositories']['self']['defaultBranch']))), or(eq(resources['repositories']['__designer_repo']['ref'], resources['repositories']['__designer_repo']['defaultBranch']), and(eq(variables['build.reason'], 'PullRequest'), eq(variables['system.pullrequest.targetbranch'], resources['repositories']['__designer_repo']['defaultBranch']))), or(eq(resources['repositories']['self']['type'], 'Git'), eq(resources['repositories']['__designer_repo']['type'], 'Git')), eq(variables['build.advancedSecurityEnabled'], 'true'), eq(variables['build.dependencyScanningInjectionEnabled'], 'true'))
Result: False
Finished evaluating template 'assets/dependency-scanning-injection-decorator.yml@'
********************************************************************************
Template and static variable resolution complete. Final runtime YAML document:
steps: []
MaxConcurrency: 0
Azure DevOps
4 answers
Sort by: Most helpful
-
Marc Brändli 0 Reputation points
2026-07-14T11:26:11.48+00:00 All suggested configuration changes have been tested and ruled out. Requests 6177 and 6872 were abandoned with "Notification of assignment to an agent was never received" — a backend fault. The free grant shows active (1 parallel job, 0/1800 min). This has persisted since Feb 10 across multiple resolved incidents. Please escalate this to the Azure Pipelines product team via ICM to check whether hosted parallelism for org Ernst-Schweizer has been zeroed or flagged on the backend. I cannot open a support case as this org has no paid support plan.
-
Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator
2026-02-10T13:12:39.7033333+00:00 Hi @Marc Brändli, could you please confirm below details:
- Has this issue occurred with any previous builds, or is it isolated to certain jobs?
- Are you able to run jobs successfully using a different pipeline, or is the problem consistent across all pipelines?
Since the job is stuck at Acquiring an agent from the cloud, the service simply hasn't allocated an agent yet. Your configuration is fine, the job is valid, and the stall is a transient service-side problem.
Free-tier pools can experience temporary delays, and this can happen even when your parallel jobs are available.
As Alex mentioned, for immediate and reliable builds, you can use a self-hosted agent or a VM Scale Set pool, a single VM with an agent avoids this class of problems entirely.
- If urgency is low, you can wait and retry later, as these stalls usually resolve on the service side without any changes from your configuration.
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
-
Alex Burlachenko 25,120 Reputation points MVP Volunteer Moderator2026-02-10T11:31:12.77+00:00 Hi Marc,
The fastest working option is to change the image. Use ubuntu 20.04 or windows latest. Very often ubuntu latest gets stuck at certain times due to image rollout issues. If you need something urgent and reliable, use a self hosted agent, even a temporary one. single VM with an agent immediately avoids this entire class of problems.
If it is not urgent, wait and try again later. These stalls do happen with Microsoft hosted pools and are usually resolved without any action from your side. Cancelling and rerunning within the same time window is often pointless.
By my opinion your configuration is correct, the limits are available, and the pipeline is valid. The agent was simply not actually provisioned from the cloud. I assume this is a service side issue, not a configuration problem.
rgds,Alex