Azure DevOps
Connector maturity: Beta. See Connector maturity.
Description
The Azure DevOps connector reads the names of the secret variables kept in Azure DevOps variable groups (Azure DevOps Services or Azure DevOps Server) through the Azure DevOps REST API 7.1, so credentials that live in pipeline libraries instead of your vault can be found. It does not scan Azure DevOps users or groups.
Each variable group that has at least one secret variable appears as a Non-Human account named azure-devops:<organization>/<group name> [<id>], holding its secret variables as CI/CD secret credentials. The variables are also compared with your vault on the Secrets Outside Vault page, and the credential KRIs and credential policy rules apply to them.
System Type Classification
| Field | Value |
|---|---|
| System Type | Application |
| Default Scan Priority | 500 |
Version Support
| OrbisID Edition | Supported |
|---|---|
| Community | No |
| Pro | Yes |
| Enterprise | Yes |
Supported Protocol
| Protocol | Port | Notes |
|---|---|---|
| REST API (HTTPS) | 443 TCP | A personal access token, sent as HTTP Basic with an empty user name |
What OrbisID Discovers
| Data | Source |
|---|---|
| Projects | GET {organization}/_apis/projects |
| Variable groups and their variables | GET {organization}/{project}/_apis/distributedtask/variablegroups |
By default only the variables marked secret are reported. Turn on the system attribute Include Plain Variables (azureDevOpsIncludeAllVariables) to report every variable; a secret stored as a plain variable is otherwise missed. Variable groups linked to Azure Key Vault are always left out, because their secrets already live in a vault. A group shared with several projects is reported once.
Azure DevOps returns the value of every variable that is not marked secret. OrbisID discards the value as soon as the response is read and never stores or logs it. A variable group has a created and a modified date for the whole group, not for a variable, so OrbisID records no date for a variable: the age of the group says nothing reliable about one secret in it, and an unknown date is not treated as "never".
At most 500 projects are read. A project whose variable groups cannot be read is skipped with a warning, and variables already recorded are kept rather than removed.
Connection Requirements
Required Permissions
Create a personal access token for OrbisID (a dedicated user is best) with the scopes:
- Variable Groups: Read (
vso.variablegroups_read) - Project and Team: Read (
vso.project)
The token's user needs Reader (or higher) on the variable groups and must be a member of the projects to read. A token that can see no project fails the scan with a message saying so, instead of reporting that no secrets exist. Microsoft recommends Microsoft Entra ID authentication over personal access tokens for new integrations; OrbisID uses a token.
Credential Mapping
| OrbisID Field | Value |
|---|---|
credential.password | The personal access token (the username is not used) |
| Organization (system attribute) | The organization name, as in https://dev.azure.com/<organization> |
system.pamPlatformUrl | Optional. The full organization URL, required for Azure DevOps Server, for example https://tfs.example.com/tfs/DefaultCollection |
Network Requirements
The OrbisID server, or the On-Premise Agent for Azure DevOps Server, must have HTTPS access to dev.azure.com (or your server) on port 443.
Configuration Steps
- In Azure DevOps create the personal access token described above
- Create a Credential in OrbisID with the token as the Password
- Navigate to Systems → Add System
- Fill in the fields:
| Field | Value |
|---|---|
| Name | Descriptive name (for example Azure DevOps - acme) |
| OS Type | Azure DevOps |
| System Type | Application |
| Hostname | dev.azure.com |
| Organization (attribute) | Your organization name |
| Credential | The personal access token credential |
- Click Test Connection
- Click Save
Troubleshooting
| Symptom | Likely Cause | Resolution |
|---|---|---|
Authentication failed - check the Azure DevOps personal access token | The token is wrong or expired. Azure DevOps often answers a bad token with a sign-in page | Create a new token and update the credential |
The token can see no project | Missing scopes, or the token's user is in no project | Add the Project and Team (read) scope, or add the user to the projects |
Azure DevOps refused ... (403) | Missing Variable Groups (read) scope, or no Reader role on the groups | Add the scope or the role |
Set the Azure DevOps organization on the system | Neither the Organization attribute nor the Platform URL is set | Set one |
| Warnings that some projects were not read | The token cannot read those projects' variable groups | Grant access, or accept that they are not covered |
| Variables appear without dates | Variable groups have no per-variable dates | Expected |