Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Access denied. Needs Use permissions for pool Default to perform the action

I get following error when trying to save a release pipeline on Azure dev. What exact permissions do I need to ask from my administrator?

Access denied. <<user id>> needs Use permissions for pool Default to perform the action. For more information, contact the Azure DevOps Server administrator.
like image 944
Channa Avatar asked Apr 24 '19 02:04

Channa


People also ask

What is TFS agent pool?

An agent pool represents a group of agents, often related to one another by sharing a common network segment or purpose. A workspace may be configured to use one of the organization's agent pools to run remote operations with isolated, private, or on-premises infrastructure.

What is the use of agent pool in Azure DevOps?

In Azure DevOps Server, agent pools are scoped to the entire server; so you can share the agent machines across projects and collections. Agent pool jobs run a job on a single agent. If you need to run a job on all agents, such as a deployment group for classic release pipelines, see Provision deployment groups.

What is pool in Azure DevOps Yaml?

A: The Azure Pipelines pool provides all Azure DevOps organizations with cloud-hosted build agents and free build minutes each month. If you need more Microsoft-hosted build resources, or need to run more jobs in parallel, then you can either: Host your own agents on infrastructure that you manage.


1 Answers

I found granting Admin to a pool very confusing (and time-consuming to resolve) but I think I can explain how I got it to work for my org. This is a further explanation, based upon what @Leo Lui-MSFT said, as that was not quite clear enough for me.

My problem: I wanted to give a user access to update a pool that the user had not created (ie, was not an Owner).

Attempted solution: Making the user Admin on the pool did not let the user do that.

Successful solution: I had to go to https://dev.azure.com/my-org/_settings/agentpools > Security > Add . I then added the user and assigned the Admin role.

This has the side effect of giving the user Admin on every pool in the org (which was not what I wanted to do). If this is not your desire then go into the pool you do not wish to grant Admin access to, set Inheritance off and then remove the user from that pool.

This feels wrong, to me. I should have been able to make a user an Admin of a single pool without granting org-wide Admin over all pools.

Also as all pools seem to be created with Inheritance defaulted to true then to remove that user as an Admin from all other pools could be time-consuming and when more pools are created then I would need to remember to turn inheritance off.

That is my experience. If I have missed something please let me know.

like image 61
Badgerspot Avatar answered Sep 19 '22 14:09

Badgerspot