Troubleshooting Azure DevOps permission errors

This article explains how to identify and resolve common permission-related errors in Azure DevOps by interpreting API error codes and messages.

When performing backup or restore operations with Azure DevOps, you may occasionally encounter access related errors. While some messages are generic, Azure DevOps often provides specific error codes and descriptions that point directly to the missing permission.

---

Understanding permission errors

If a task fails due to insufficient privileges, Xopero ONE 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.

Error code	Message example	Resolution
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.

---

Resolving permission errors

If you encounter one of the specific errors listed above, follow these steps to adjust your configuration:

1

Look at the error message to see if the scope is project, organization, or repository.

2

Ensure the identity mentioned in the error (e.g., identity '...\\[email protected]') matches the account used for the Xopero ONE integration.

3

Adjust settings in Azure DevOps.

1. Navigate to Project Settings or Organization Settings in Azure DevOps.

2. Go to the Permissions or Security tab.

3. Find the user or the group the user belongs to and set the missing permission (e.g., Create new projects) to Allow.

4

Once the permissions are updated, go back to Xopero ONE and restart the failed task.

Just like with GitHub integrations, Xopero ONE dynamically processes error messages to help you identify exactly which permission needs to be added to your Azure DevOps account. Always check the task summary for a detailed list of required permissions.