Azure DevOps

#What Opriven does with Azure DevOps

• Read repositories, branches, commits, and pull requests to find the change that caused a failure
• Inspect build definitions, runs, and logs to see which pipeline broke and where
• Read work items and queries for the context behind a change
• Search wikis and test plans for the runbook or coverage relevant to the failure

#Connecting Azure DevOps

Only connect this if your team uses Azure DevOps for source control, work items, or pipelines. It is not required for the Azure cloud integration.

Prerequisites

• An Azure DevOps organization
• Permission to create Personal Access Tokens
• Access to the projects you want Opriven to inspect

1. Open Personal Access Tokens

   In Azure DevOps, click your profile icon and select User Settings > Personal Access Tokens.

2. Create a new token

   Click + New Token, name it Opriven, select the organization, set an expiration matching your rotation policy, and choose Custom defined scopes.

3. Grant read-only scopes

   Select Read only for Code, Work items, Build, Test Management, Wiki, and Project and team. Do not enable any write, manage, or execute scopes. See Microsoft's Personal Access Tokens guide.

4. Create and copy the token

   Click Create, then copy the token value — it is only shown once.

5. Share the token with Opriven

   Paste your Organization URL (https://dev.azure.com/<your-org>) and the Personal Access Token, then click Connect.

#Permissions and access

Opriven uses a read-only PAT. No write operations are performed in your Azure DevOps organization. Tokens are stored encrypted. Azure DevOps PATs have a maximum one-year lifetime — rotate before expiration and update the credential in Opriven. Revoke access at any time by deleting the token.

All tenant data is processed in isolated environments. See security and compliance for details.