Azure Pipelines "No agent found in pool matches the demands"
The job specified demands (capabilities) that no agent in the target pool advertises, so it could not be assigned.
What this error means
The job stays queued or fails with "No agent found in pool X that satisfies the demands" listing the required capabilities.
azure-pipelines
##[error]No agent found in pool Default that satisfies the specified demands:
docker, Agent.OS -equals LinuxCommon causes
Demand not provided by any agent
A required capability (a tool or custom demand) is not installed or registered on any agent.
Wrong pool targeted
The job points at a pool whose agents lack the demanded capabilities.
Capability name typo
The demand name does not match the capability the agent advertises.
How to fix it
Match demands to agent capabilities
- Open the pool's agent capabilities and confirm the demanded names exist.
- Install missing tools or correct the demand name.
azure-pipelines.yml
pool:
name: linux-pool
demands:
- dockerHow to prevent it
- Keep agent capabilities documented and use demand names that exactly match what agents advertise; this is a configuration mismatch, not transient.
Related guides
Azure Pipelines "No hosted parallelism has been purchased"Fix the Azure Pipelines "No hosted parallelism has been purchased or granted" error that blocks Microsoft-hos…
Azure Pipelines "All potential agents are in use" WaitFix the Azure Pipelines wait where "all potential agents are in use" because the self-hosted pool has no free…
Azure Pipelines "We stopped hearing from agent" Lost CommunicationFix the Azure Pipelines "We stopped hearing from agent" error where the service lost communication with the a…