Restore

Learn how to restore Azure DevOps repository backups using Cloudback, including the authorization flow and what gets restored.

Cloudback can restore your Azure DevOps repository data from any backup archive. This includes the full Git repository, pull requests with review threads and comments, labels, and attachments.

For the general restore workflow (how to initiate a restore, select a target, and monitor progress), see Restoring a Backup.

Restore Authorization

Cloudback uses a separate OAuth application for restore operations, following the principle of least privilege:

• Backup uses read-only access to clone repositories and download metadata

• Restore uses read-write access to create repositories and push data

If this is your first time restoring, you will be prompted to authorize on the Microsoft consent page. Write access is only granted when you explicitly initiate a restore.

Target Selection

• Select the target organization and project

• Enter the new repository name

• A new repository is always created — you cannot restore to an existing repository

What Gets Restored

Entity	Details
Repository	All branches, tags, and refs via git push --mirror
Pull Requests	Source branch, target branch, title, description
Review Threads	Status (active, fixed, won't fix, closed, by design, pending), file context (path and line positions)
Thread Comments	Comment body with original author and timestamp
PR Labels	Label names applied to each pull request
PR Attachments	Files attached to pull requests

Note: Original author information and creation dates are embedded as text in PR descriptions and comments, since the Azure DevOps API does not support creating entities on behalf of other users.

Learn More

• Azure DevOps Backup Contents — What data is in each backup

• Restoring a Backup — General restore workflow

• Bulk Restore — Restoring multiple repositories at once