'AzDO Pipeline waiting for permission to agent pool

We're using yaml pipelines with environment agents installed on local infrastructure. Each Environment is backed by a Deployment Pool which is implicitly created by AzDO. The pools reside at the org level.

Every time someone adds an environment to a pipeline it requires the project collection admin to authorize the pipeline. The devs cannot authorize the pipeline because they don't have permission at the org level. Image below shows prompt received.

Is there anyway to simplify this so the PCA is not required to authorize every on-prem pipeline?

enter image description here



Solution 1:[1]

No, we do not have any methods to skip the permit from PCA, when a pipeline is trying to target to an environment at the first time.

On the Organization Settings and Project Settings, we also do not have any built-in options to defaultly permit all new environments on all pipelines.

This is aiming to prevent the environments from being abused.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source
Solution 1 Bright Ran-MSFT