Azure Devops

Use the Azure Devops connector to manage software development pipelines.

Integrating your application with Azure Devops lets you use these operations in an automation. It exposes 20 actions and 1 trigger, listed below. Add the connector from the Connections area, authenticate, then select its operations in the automation builder. Capabilities: actions, triggers, knowledge (RAG).

Authentication

Before you begin, make sure you have the following information:

Connection Name: Choose a meaningful name for your connection. This name helps you identify the connection within your application or integration settings.

Authentication Type: Azure Devops supports the following authentication methods:

• Personal Access Token (PAT)

• OAuth 

• Service Principal / Managed Identity

• Microsoft Entra ID

Authentication & setup

Azure DevOps REST APIs support multiple authentication methods, with Microsoft Entra ID being the recommended approach for production applications.

Personal Access Token (PAT)

Use this method for ad-hoc requests, personal scripts, and early prototyping.

1. Log in to the Azure DevOps portal.

2. Click the User Settings icon in the top-right corner.

3. Select Personal Access Tokens from the dropdown menu.

4. Click + New Token.

5. Provide a name for the token to identify its purpose.

6. Select the Organization where the token will be used.

7. Set an Expiration Period in line with your security policy.

8. Under Scopes, grant the required permissions — typically Code, Build, Release, and Work Items, depending on your integration needs.

9. Click Create.

10. Copy the generated token immediately — it is not displayed again.

11. In UnifyApps, paste it into the Personal Access Token field.

Microsoft Entra ID

Use this method for production integrations. It authenticates as an application registered in your Microsoft Entra ID (Azure AD) tenant.

1. In the Azure portal, go to Microsoft Entra ID > App registrations and select New registration.

2. Give the application a name and register it.

3. On the app's Overview page, copy the Application (client) ID and the Directory (tenant) ID.

4. Go to Certificates & secrets > New client secret, create a secret, and copy its Value immediately — it is not displayed again.

5. Go to API permissions > Add a permission, select Azure DevOps, and add the delegated permissions your integration requires. Grant admin consent if your tenant requires it.

6. Make sure the application has access to your Azure DevOps organization. In Azure DevOps, go to Organization settings > Users and add the service principal with an appropriate access level and project permissions.

7. In UnifyApps, enter:

• Client ID: the Application (client) ID from step 3.

• Client Secret: the secret value from step 4.

• Tenant ID: the Directory (tenant) ID from step 3. You can also find this in the Azure portal under Azure Active Directory > Overview.

• Scopes: defaults to 499b84ac-1321-427f-aa17-267ca6975798/.default, the Azure DevOps resource application ID. Leave the default unless you have a reason to change it.

Service Principal / Managed Identity

Use this method for machine-to-machine and automated scenarios where no user is present.

1. Register an application in Microsoft Entra ID, or identify an existing managed identity, as described in steps 1–4 above.

2. In Azure DevOps, go to Organization settings > Users, add the service principal or managed identity, and assign it an access level and the project permissions the integration needs.

3. In UnifyApps, enter the Client ID, Client Secret, and Tenant ID.

No scope selection is required for this method.

OAuth 

Use this method to authorize the connection interactively, on behalf of a signed-in user.

1. Select the Scopes the integration requires. The default selection is vso.work, vso.build, vso.code, vso.release, vso.test, and vso.analytics. Select only the scopes you need.

2. Optionally enter your Tenant ID to restrict authorization to a specific Microsoft Entra tenant.

3. Complete the Microsoft sign-in and consent prompt when it appears.

Actions

Triggers