Required permissions

Required permissions for Azure DevOps and Azure DevOps Server specify the access levels Xopero ONE needs to securely back up and restore your data.

Permissions for Azure DevOps

User access levels

The account used for integration must have an appropriate access level assigned within Azure DevOps:

• Basic.

• Visual Studio Subscriber — professional or enterprise tier.

• GitHub Enterprise — similar to basic.

• Stakeholder (not recommended) — this level has limited access and cannot properly protect repositories.

To integrate Azure DevOps with Xopero ONE using OAuth, make sure the account has an administrator role. Otherwise, you may encounter permission errors or find that the approval button is inactive.

When integrating Azure DevOps via OAuth, the following scopes are required:

• Build: read and execute (vso.build_execute)

• Code: read, write and manage (vso.code_manage)

• Environment: read and manage (vso.environment_manage)

The ability to authorize the Xopero ONE OAuth application depends on your organization's User consent settings within Azure DevOps. The following options are available:

• Organization — when generating PAT, you must enable the All accessible organizations value in the Organization field.

• Build: read and execute

• Code: read, write and manage

• Environment: read and manage

To ensure both backup and restore operations succeed, the following permissions are required:

1. Organization level:

   1. General:

      1. Create new projects (restore)

For on-premise installations, use the personal access token (PAT) method.

• Organization — when generating PAT, you must enable the All accessible organizations value in the Organization field.

• Build: read and execute

• Code: read, write and manage

• Environment: read and manage