Protected resources

Overview of protected Azure DevOps and Azure DevOps Server resources, including repositories, wikis, and metadata secured by backup.

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

---

Backup coverage

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

The list is presented in alphabetical order.

ARTIFACTS	BOARDS	BOARD PROCESSES
Artifact Settings Deleted Package Options Feed Feed Name Packages Package Sharing Options	Work Item Attachments Work Item Comments* Work Items** Work Items Related Work	Work Item Types*** Work Item Types - Layout Fields Groups Pages Picklists Work Item Types - States

_{*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).}

PIPELINES	PROJECT
Environments Pipelines* Variable Groups**	Project Wiki

_{*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.}

PULL REQUESTS	REPOSITORY	TEST PLANS
Closed Pull Requests* Comments Creation Date Creator Description Merged Pull Requests* Open Pull Requests Reviewers Tags	Branches Commits Commit Creators Commit History Commit Messages Default Branch Git Objects LFS Tags	Configurations Configuration Variables Test Cases (assignment to Test Suites) Test Plans Test Points (state & outcome) Test Results Test Run** Test Suites***

_{*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.}