Azure DevOps Connection
The Azure DevOps connection type enables automations to interact with Azure DevOps Services (cloud) or Azure DevOps Server (on-premises) — creating and updating work items, reading pipeline results, querying repositories, and triggering builds. Credentials are stored once and reused across any number of Azure DevOps-enabled workflow steps.
Connection Details
| Property | Value |
|---|---|
| Type ID | AZURE_DEVOPS |
| Category | DevOps / Version Control |
| Testable | Yes |
Friendly Example
| What you enter | Example |
|---|---|
| Connection name | Azure DevOps - Release Board |
| Used for | Automatically creating work items from monitoring alerts and reading build pipeline status as part of an incident response workflow |
| Main details to collect | Organization URL and a Personal Access Token (PAT) with appropriate scopes |
| Best person to provide it | Azure DevOps organization administrator |
After it is saved, workflow builders select Azure DevOps - Release Board in a node instead of re-entering credentials each time.
Mandatory Fields
| Field | What It Means | Example |
|---|---|---|
organizationUrl | Full URL of your Azure DevOps organization. For cloud this follows the pattern https://dev.azure.com/<org>. For on-premises Server use your internal base URL. | https://dev.azure.com/contoso |
personalAccessToken | A scoped Personal Access Token that authenticates all API calls. Encrypted at rest. | xyzabc123... |
A PAT with too many scopes is a security risk; one with too few causes 403 Forbidden errors. Create the PAT with only the scopes listed in the Setup Instructions section below.
Advanced Fields
| Field | What It Means | Example |
|---|---|---|
defaultProject | Azure DevOps project name pre-filled for workflow steps that do not specify a project explicitly | BackendPlatform |
timeoutSeconds | Maximum seconds to wait for an Azure DevOps API response before the connector raises a timeout error | 30 |
Setup Instructions
-
Open Azure DevOps. Go to dev.azure.com (or your on-premises Server URL) and sign in with the account you want to use for the integration. Using a dedicated service account (e.g.,
automation@contoso.com) is strongly recommended so the PAT does not become invalid if the owner leaves. -
Open Personal Access Tokens. Click your user avatar in the top-right corner, then select Personal access tokens. On Azure DevOps Server, this setting is found under User Settings > Security > Personal Access Tokens.
-
Create a new token. Click New Token. Fill in:
-
Name: something descriptive, e.g.,
Qinfinite Automation -
Organization: select the organization this token should cover (or All accessible organizations if your automations span multiple orgs)
-
Expiration: set an expiry aligned with your security policy (90 or 180 days is common); set a calendar reminder to rotate it before expiry
-
Scopes: choose Custom defined, then enable only the scopes your automations require:
Scope Required when Work Items — Read & Write Creating or updating work items Code — Read Reading source repository contents Build — Read Querying pipeline and build results Release — Read Querying release pipeline status
-
-
Copy the token immediately. Azure DevOps shows the full token only once. Paste it into the Qinfinite Personal Access Token field before closing the dialog.
-
Save the connection in Global Configurator. Enter the organization URL and the PAT, then click Test Connection to confirm end-to-end connectivity before saving.
For Azure DevOps Server, your organization URL typically looks like https://tfs.contoso.com/tfs/DefaultCollection. Confirm the exact URL with your DevOps team — it varies by IIS site binding and virtual directory configuration.
Troubleshooting
| Symptom | Likely Cause | Fix |
|---|---|---|
401 Unauthorized on every request | The PAT is incorrect, expired, or was copied with extra whitespace | Regenerate the PAT in User Settings > Personal Access Tokens and update the connection |
403 Forbidden on a specific operation | The PAT was created without the required scope, or the service account lacks access to the target project | Check the PAT scopes and ensure the service account is a member of the target project with the appropriate permission level |
404 Not Found when targeting a project or repository | The defaultProject name or the project key passed by a workflow step does not match an existing project in the organization | Verify the project name in Azure DevOps — project names are case-sensitive in the REST API |
| Test Connection succeeds but work item creation fails | The service account has read-only access to the project | Grant the service account the Contributor role in Project Settings > Permissions for the target project |