Azure Pipelines "Pool not found" / Pool Not Authorized

By Daniel Zoghalchali·Latchkey

The pool: name does not resolve to a pool available to this pipeline. The name is wrong, the pool was never added to the project, or the pipeline is not authorized to use it as a protected resource.

What this error means

The run fails before queueing with The pool <name> does not exist or has not been authorized for use. No agent is selected because the pool reference itself is invalid.

##[error]The pool 'Linux-Build' does not exist or has not been authorized
for use with this pipeline.

Diagnose it: variables, expressions, or the agent?

Azure Pipelines resolves compile-time expressions (${{ }}) before the run and runtime expressions ($[ ]) during it. Using the wrong one is the most common source of a value that is empty when you read it.

# print what the job actually resolved
- script: |
    echo "reason: $(Build.Reason)"
    echo "branch: $(Build.SourceBranch)"
    env | sort | head -40
  displayName: Dump context

# enable full diagnostics on a run: set system.debug = true as a variable

Common causes

Pool name wrong or not in this project

Agent pools are added to projects from the org. A typo, or a pool that was never granted to the project, makes pool: { name: ... } unresolvable.

Pool not authorized for the pipeline

Agent pools are protected resources. A new pipeline referencing a pool may need explicit authorization before it can use it.

How to fix it

Reference the exact authorized pool name

Use the pool name as shown in Project Settings → Agent pools.

pool:
  name: Default        # exact pool name available to this project

Add and authorize the pool

1. In Project Settings → Agent pools, add the org pool to this project if absent.
2. Open the pool → Security and authorize this pipeline (or all pipelines, if appropriate).
3. Re-run; the first reference to a new pool may prompt for authorization.

How to prevent it

• Keep pool names consistent and documented per project.
• Authorize pools for pipelines when first wiring them.
• Avoid referencing org pools not granted to the current project.

Frequently asked questions

Related guides

References

• GitHub Actions documentation