This account should be treated in the same way that the build service identities are treated. In practice, the tokens that involve this identity are granted read-only permissions to pipeline resources and the one-time ability to approve policy requests. This user account is similar to the build service identities but supports locking down permissions separately. Responsible for managing the link creation between GitHub and Azure Boards.Īdded as needed to support the Pipelines policy service scope tokens. You should not have to manage members of this group. Responsible for performing Azure Boards read/write operations and updating work items when GitHub objects are updated.Īdded when Azure Boards is connected to GitHub. The service account you specify for the agent (commonly Network Service) is automatically added when you register the agent.
Download permissions reset by ohanaware registration#
The agent registration process takes care of it for you. In most cases, you should not have to manage members of this group. Has permission to listen to the message queue for the specific pool to receive work. These user accounts are added at the organization or collection level.
These include those described in the following table. There are a few service accounts that are generated by the system to support specific operations. However, the basic functionality available to you remains the same unless explicitly mentioned.
These differences result from updates made to Azure DevOps. The images you see from your web portal may differ from the images you see in this topic.
0 kommentar(er)
