Skip to main content

Azure DevOps proof types and permissions

Note

Hyperproof connects to many third-party systems that frequently change, including the system interface. Contact your System Administrator or the third-party provider for assistance meeting the requirements to integrate with Hyperproof and collect the proof you need.

When you create a Hypersync between Hyperproof and Azure DevOps, you can automatically collect proof based on:

  • Deployments in an Environment

  • Deployment Approval Policy

  • List of Users

  • Members in Permission Group

Additional documentation

Note

You only need to connect Hyperproof to the app once, and then you can create as many Hypersyncs as you need. Additionally, you can create multiple Hypersyncs for a single control or label.

Permissions

The following scopes are required to access data in your Azure DevOps organization:

  • vso.graph

  • vso.memberentitlementmanagement

  • vso.project

  • vso.release (vso.profile is included implicitly since it’s inherited by having vso.release)

Additionally, you must be added to the project at minimum as a Project Reader with Stakeholder Access to pull data related to the project, such as deployments and group members. Currently, external users (external to your Azure and Azure DevOps organization) are not supported.

Revoking permissions previously given to the Azure DevOps Hypersync

  1. Log into https://aex.dev.azure.com/.

  2. From the Authorizations section, click Manage authorizations.

  3. Verify the app name for which you want to revoke access.

  4. Click Revoke and then confirm the action.

In this section: