Azure-devops-docs: There's no way to authorize the pipeline

[mydiemho]

I can't even queue a run so there's no failed run to access the button

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: ee4ec9d0-e0d5-4fb4-7c3e-b84abfa290c2
• Version Independent ID: 3e2b80d9-30e5-0c48-49f0-4fcdfedf5eee
• Content: Resources - Azure Pipelines
• Content Source: docs/pipelines/process/resources.md
• Product: devops
• Technology: devops-cicd
• GitHub Login: @vtbassmatt
• Microsoft Alias: macoope

[WilliamAntonRohm]

@mydiemho -- My, have you tried these instructions? If that doesn't answer your question, try:

• Azure DevOps on Stack Overflow
• Azure DevOps Support Bot

I am closing this issue now. You are welcome to @ mention me for any followup.
We hope to hear from you again.

[Sureiya]

@WilliamAntonRohm Generally trying to understand the issue before closing is helpful.

[WilliamAntonRohm]

@Sureiya -- Chris, thanks for your feedback; we appreciate it. To make sure we have all the information needed to triage your issue, please provide more context around the general task.

[beavel]

Found this issue while running into the same problem. I ran into the problem from the following scenario.

Given an existing pipeline with trigger: none set, and variable group with Allow access to all pipelines disabled,
When I add the variable group to a pipeline via text editor and push the code,
Then when I go to Queue I receive the An error occurred while loading the YAML build pipeline. Variable group was not found or is not authorized for use. For authorization details, refer to https://aka.ms/yamlauthz. error message and no button to fix.

This seems related to #4643.

My two workarounds:

1. Link in the UI by going to "Edit" -> "Triggers" (to pull up the UI showing variables) -> "Variables" -> "Variable Groups" and link.
   
   
   
   • Problem with this approach is it requires the UI and unlink breaks the source link again.
   
   
2. Add a trigger for the branch I am on and push. Get the failed build with button to Authorize. Authorize. Remove the trigger.
   
   
   
   • Seems like a bit of a hack.
   
   

It's a little disappointing to see these issues open for so long with what seems to be a pretty straightforward work flow being missed in docs or resolved via UI update.

[beavel]

As an additional update, the documentation seems to be written for building a brand new pipeline. When saving/running a new pipeline for the first time, you do get the failed build with "Authorize Resource" button.

[mortenlerudjordet]

Observing the same as @beavel

[vtbassmatt]

Adding @ashokirla for variable group authorization.

[christophermlawson]

I'm also seeing the same as beavel. The workarounds above do not work for me, however. I'm currently stuck with no way to run the build.

[ashokirla]

Thanks for your feedback. Support for variable group authorization in our current backlog and will start the implementation very soon.
@shashban to keep note.

[jderus]

Im not sure if this is directly related to your issue, but there appears to be some ui/documentation wonkiness about authorizing pipelines. This is especially useful to know if you are getting an "missing pool" type error.

Project Settings -> Agent Pools -> Security allows you to grant access to all pipelines
Organization Settings -> Agent Pools -> Security does not appear to.

[cxwtool]

This issue hasn't been updated in more than 180 days, so we've closed it. If you feel the issue is still relevant and needs fixed, please reopen it and we'll take another look. We appreciate your feedback and apologize for any inconvenience.