Azure Pipelines Deployment to Environment Requires Approval

By Daniel Zoghalchali·Latchkey

An environment with an approval check holds the deployment job until a designated approver signs off. The run is not failing - it is paused by policy, and proceeds (or times out) based on the approver's response.

What this error means

A deployment job stays in "Waiting" with a note that the environment requires approval. No steps run until an approver acts, and the check can expire if no one responds in the configured window.

Deployment to environment 'production' requires approval.
Waiting for approval from: release-managers.

Common causes

Environment has an approval check

The target environment is configured with a manual approval. The deployment job is gated until an authorized approver approves or rejects.

Approver unavailable or check expiring

If no approver responds within the timeout, the check expires and the deployment is rejected - the run "fails" by policy, not by code.

How to fix it

Have an approver act on the pending check

1. Open the run; the deployment job shows a pending approval prompt.
2. An authorized approver approves (or rejects) the deployment.
3. On approval the job proceeds; on timeout it is rejected and must be re-run.

Tune the approval policy deliberately

Configure the environment check's approvers and timeout to match your release process.

# Pipelines -> Environments -> production -> Approvals and checks
# add the right approver group and a realistic timeout

How to prevent it

• Configure approver groups and timeouts to fit your release cadence.
• Ensure approvers are notified and available for time-sensitive deploys.
• Reserve manual approvals for environments that genuinely need them.

Frequently asked questions

Related guides

References

• GitHub Actions documentation