Azure DevOps Permissions Issues and Solutions

1. Azure DevOps Login Issue

Issue:

• Azure DevOps has two types of user identification: email ID and user ID.

• Having the same email ID does not necessarily mean the user ID is the same as the email.

• The client provided access to the email ID but not to the actual user ID.

Solution:

• Ensure that you check your actual user ID in Azure DevOps.

• Request the client to grant access based on the correct user ID instead of just the email ID.

2. Azure DevOps vs. Azure Console Login

Issue:

• Azure DevOps login is separate from Azure Console login, which may cause confusion.

Solution:

• Use the correct login method for each platform.

• Verify permissions and roles in both Azure DevOps and Azure Console separately.

3. Resource Group Creation Permission Issue

Issue:

• No permissions were granted to create a Resource Group in Azure.

Solution:

• Request the appropriate permissions from the Azure administrator.

• Ensure you have at least Contributor or Owner role assigned to create resource groups.

4. Agent Pool and Self-Hosted Agent Issue

Issue:

• The default agent pool in Azure DevOps only allows Azure-managed agents.

• Unable to use a self-hosted agent in the default pool.

Solution:

• Create a new agent pool.

• Set up a new self-hosted agent in a VM within the newly created pool.

5. Pipeline Permission for Staging Agent Pool

Issue:

• The pipeline could not use the Staging agent pool due to missing permissions.

Solution:

• Navigate to Project Settings → Agent Pools → Staging → Security.

• Allow "Open Access" permission for the pipeline to use the Staging agent pool.

---

This document serves as a runbook for resolving common Azure DevOps permission-related issues. Always verify your user ID, check role-based access control, and ensure correct permissions for agent pools and pipelines.