autobotAI

Azure DevOps

Overview

The Azure DevOps integration allows autobotAI to seamlessly connect with your Microsoft Azure DevOps cloud (https://dev.azure.com) or on-premises Azure DevOps Server environments. This integration empowers automated security workflows, continuous inspection of code repositories (Git), automated tracking and remediation via work items, and comprehensive management of CI/CD pipelines and builds.

This guide provides step-by-step instructions for configuring the Azure DevOps integration within your autobotAI account. By completing this configuration, you enable autobotAI bots and AI workflows to securely interact with your Azure DevOps projects, repositories, work items, and build pipelines.

Prerequisites

Before starting the setup, ensure you have the following:

  • An Azure DevOps Organization (https://dev.azure.com/{organization}) or an accessible Azure DevOps Server / On-Premises instance.
  • Authentication Credentials (choose one of the following methods):
    • Personal Access Token (PAT) (Recommended / Standard): A token with appropriate scopes (e.g., Code Read/Write, Work Items Read/Write, Build Read/Execute).
    • Service Principal (Entra ID / Azure AD) (Optional): If authenticating via Service Principal instead of a PAT, you will need the Application (Client) ID, Client Secret, and Directory (Tenant) ID associated with an application registered with sufficient permissions in Azure DevOps.

Steps to Set Up Azure DevOps Integration

Step 1:
Navigate to the Integrations page by selecting Integrations from the main navigation menu. Click the + Add Integration button in the top-right corner to open the integration marketplace.

Step 2:
From the marketplace list, under the Code Repository category, select Azure DevOps + Add to launch the Azure DevOps integration form.

Step 3:
Fill in the configuration parameters as follows:

Note: Fields marked with an asterisk (*) are mandatory.

  • Alias*: Enter a descriptive name or alias for this connection (for example, Azure DevOps Cloud - Engineering or ADO Production).
  • Tags: Optionally assign tags to organize and categorize multiple integrations across different business units or environments.
  • Organization Name: The Azure DevOps organization name (cloud URL format: https://dev.azure.com/{organization}). Leave blank only if you are using a custom base_url that already includes the collection path.
  • Base URL: The base URL of your Azure DevOps service. Use https://dev.azure.com for Azure DevOps Cloud (default), or enter your server URL for Azure DevOps Server / On-Premises deployments.
  • Personal Access Token (PAT): Enter your Azure DevOps Personal Access Token. This is required unless you are authenticating via a Service Principal.
  • Application (Client) ID (Optional): Enter your Entra ID / Service Principal Client ID (use only when authenticating via Service Principal instead of a PAT).
  • Client Secret (Optional): Enter the client secret corresponding to your Service Principal.
  • Directory (Tenant) ID (Optional): Enter your Azure AD / Entra ID Tenant ID for the Service Principal.

Double-check your credentials and configurations, then click Create to establish the integration.

Step 4:
After saving, your new integration will appear in the Integrations list. Click on the Play button next to your Azure DevOps integration entry to run an automated verification check ensuring connectivity and valid authentication.

Additional Information

How to Generate an Azure DevOps Personal Access Token (PAT)

If you are using PAT authentication, follow these steps to generate a secure token:

  1. Sign in to Azure DevOps:
    Open your browser and navigate to https://dev.azure.com/{your-organization}.

  2. Open Personal Access Tokens:
    In the top-right corner near your profile photo, click the User settings icon (gear/slider icon) and select Personal access tokens.

  3. Create New Token:
    Click the + New Token button.

  4. Configure Scopes and Expiration:

    • Name: Give your token a recognizable name (e.g., autobotAI-Integration-Token).
    • Organization: Select the specific organization or All accessible organizations.
    • Expiration: Select an appropriate expiration timeline (e.g., 90 days, 1 year, or custom).
    • Scopes: Choose Custom defined and grant the required permissions based on your bot automation requirements:
      • Code: Read & Write (to monitor repositories, inspect code, or automate branch management)
      • Work Items: Read & Write (to automatically create or update tracking bugs and remediation tasks)
      • Build: Read & Execute (to monitor CI/CD pipelines or trigger build executions)
      • Project and Team: Read (to discover projects and teams)

  5. Copy and Save:
    Click Create. Copy the generated token string immediately. Important: Azure DevOps will not display the token secret again once you close the window. Paste the token into your autobotAI integration form.