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

Xopero ONE allows organizations to restore individual Azure DevOps repositories along with their associated metadata. The process ensures repository integrity and consistency while minimizing impact on other projects, supporting efficient disaster recovery, migration, and point-in-time restore operations.

Recovery process

The following steps demonstrate how to quickly restore a single Azure DevOps repository using Xopero ONE Management Service.

Xopero ONE enables single project recovery for Azure DevOps, allowing organizations to restore individual projects along with their selected metadata, ensuring data integrity and consistency while minimizing disruption to other projects and repositories.

The below steps demonstrate how to quickly restore a single Azure DevOps project using Xopero ONE Management Service.

The Azure DevOps & DevOps Server backup process in Xopero ONE securely connects to your DevOps environment, captures repositories, projects and related metadata, and stores verified backup copies that can be restored when needed.

General information

Xopero ONE is designed to protect DevOps ecosystems, including Azure DevOps.

To ensure your entire Azure DevOps environment is reliably backed up, make sure to include all repositories along with their related metadata — the best practice is to create a backup plan for critical repositories and metadata that change daily (or even more frequently), for example, using the recommended Grandfather-Father-Son (GFS) rotation scheme.

Additionally, create a separate backup plan for unused repositories that you need to keep for future reference. This type of backup primarily serves Azure DevOps archival purposes, and with unlimited retention, you can store your copies for as long as needed — even indefinitely.

You can also delete repositories from your Azure DevOps account while keeping a copy in storage, which helps bypass Azure DevOps limits.

Incremental and differential backups help save storage space. In Xopero ONE you can define different retention and performance settings for each type of backup (full, incremental, and differential). For example, our software allows you to include only the blocks of Azure DevOps data that have changed since the last backup, reducing storage usage, speeding up the process, and limiting bandwidth.

Use different types of storage to replicate backups, minimize the risk of outages or disasters, and comply with the 3-2-1 backup rule (which means having at least three copies of your data on two different storage types, with at least one copy stored in the cloud).

Xopero ONE is a multi-storage system that allows you to store your data:

• In the cloud (Xopero Cloud Storage, AWS S3, Wasabi Cloud, Backblaze B2, Google Cloud Storage, Azure Blob Storage, or any S3-compatible public cloud).

• Locally (NFS, CIFS, SMB network shares, or local disk resources).

• In a hybrid or multi-cloud environment.

Rate limits enhance security by preventing an overwhelming number of requests that could disrupt, block, or destabilize the application's functionality—the system enforces these limits for stability. For more information, visit .

In Azure DevOps Server (on-premises), API limits are flexible and depend on server resources and configuration. Unlike the cloud version, there are no fixed, global request limits—administrators set performance parameters and limits tailored to the organization's specific needs.

Azure DevOps protected resources define which parts of the environment Xopero ONE can access, backup, and restore.

Backup coverage

The following tables list all Azure DevOps and Azure DevOps Server resources covered by backup.

_{*The restored comment is attributed to the account performing the restore; content includes the original comment author information and the original creation date.}

_{**Assignee and identity-type fields are not restored directly; instead, a comment is added identifying the original assignee and related values.}

_{***A work item type consists of a name, description, color, icon, enabled/disabled status, and its internal configuration (layout and states).}

_{*Configuration and definitions are restored; logs, run history, and artifacts are not. Only YAML pipelines that use Azure Repos are supported.}

_{**Secret variables are not backed up due to an API limitation.}

_{*Included in backup, but can be restored only to GitHub and GitLab.}

_{**Test run history is backed up and restored. The run state (for example, in progress or needs investigation) is restored in a separate step after the run is created.}

_{***Automated test settings (associated pipelines) are not restored due to current pipeline restore limitations.}

Restoring multiple Azure DevOps projects enables organizations to quickly recover projects, repositories, and source code at scale, ensuring consistent and reliable restoration across the development environment.

Recovery process

The below steps demonstrate how to restore multiple Azure DevOps projects at once using Xopero ONE Management Service.

Recovering multiple Azure DevOps repositories simultaneously enables organizations to quickly restore only the selected repositories, ensuring consistent and reliable recovery across the development environment.

The following steps demonstrate how to restore multiple Azure DevOps repositories at once using Xopero ONE Management Service.

Adding an Azure DevOps Server to Xopero ONE connects your projects and repositories to the platform, enabling seamless backup management and secure data protection.

Using a Personal Access Token (PAT)

Creating an Azure DevOps (or DevOps Server) backup plan ensures your projects and data are securely protected and easily restorable.

Backup plan setup

Adding an Azure DevOps organization to Xopero ONE connects your environment to the platform, enabling secure backup of projects, repositories, and related data.

Using OAuth

When adding an organization, you may be prompted to grant additional permissions to the Xopero ONE application — make sure your browser allows Xopero to open pop-up windows.

Depending on your browser, you can either adjust the settings to allow pop-ups or permit the authorization window to open once.