This article explains how to identify and resolve common permission-related errors in Azure DevOps by interpreting API error codes and messages.
If a task fails due to insufficient privileges, GitProtect will display the error returned by the Azure DevOps API in the task summary. These messages usually follow a structured format containing a message and a typeName.
If you encounter one of the specific errors listed above, follow these steps to adjust your configuration:
Look at the error message to see if the scope is project, organization, or repository.
Ensure the identity mentioned in the error (e.g., identity '...\\user@example.com') matches the account used for the GitProtect integration.
Adjust settings in Azure DevOps.
Navigate to Project Settings or Organization Settings in Azure DevOps.
Go to the Permissions or Security tab.
Find the user or the group the user belongs to and set the missing permission (e.g., Create new projects) to Allow.
Once the permissions are updated, go back to GitProtect and restart the failed task.
TF401027
"You need the Git 'CreateRepository' permission to perform this action."
The account lacks the Create repository permission at the repositories level.
VS402356
"You do not have the permissions required to perform the attempted operation on this process."
The account lacks the Create process or Edit process permission at the organization level.
TF50309
"The following permissions are needed to perform this operation: Create new projects."
The account lacks the Create new projects permission at the organization level.
VS800075
"The project with id 'proj' does not exist, or you do not have permission to access it."
Generic error, this occurs when the account has no access to the project at all. Verify the user access level and project-level memberships.