Azure DevOps Services (ADO) setup

Tags: Flow

Follow this step-by-step guide to connect your Microsoft Azure DevOps Services (ADO) account to Flow.

Note: This integration is only for Azure DevOps Services (ADO Cloud). This product was formerly known as Visual Studio Team Services (VSTS). If you use Azure DevOps Server, follow the instructions for creating an Azure DevOps Server integration.

Before getting started, make sure your system is supported. Git repos are supported. TFVC repos are not supported.

If PRs have not been updated, deleted, abandoned, or created within the six months prior to the initial integration processing date, the PR will not be ingested into Flow and will not appear in reports.

Important: Use a service account to create this integration. Learn more about creating a service account.

Who can use this?

 Core
Plus
 
  


Permission requirements

There are three requirements to use integration services like repos, pull requests, tickets, and webhooks:

  1. Set up personal access token scopes. Follow the instructions below to learn more.
  2. Make sure the service account is set up as a Project Collection Administrator at the organizational level.
  3. Your git host may not require webhooks. If this is the case, set the git host’s View instance-level information permission to Allow. This permission is required to establish a connection and import repos. Add the user to the reader group at the project level.

back to top


Azure DevOps Services configuration

Follow these steps to set up your Azure DevOps Services configuration.

  1. Click Settings In Flow's top navigation.
  2. In the left navigation under Integrations, click Integrations.
  3. Click the Add Integration button in the top right corner of the Integrations page.
  4. On the following Integration Provider page, click Azure DevOps.
  5. Select whether you want to connect via OAuth or via Access token.
  6. Input your email address, Personal access token, and Base URL. Use the exact email format seen in your Azure user profile. The email field is case sensitive. Your URL will look like https://dev.azure.com/{yourorganization}.

Important: Use the https://dev.azure.com domain in the Base URL field in Flow to connect successfully. This applies even if your base URL in Azure Devops Services uses the visualstudios.com domain. While you may be able to access your instance using either a dev.azure.com or visualstudios.com domain, Flow requires the format of https://dev.azure.com/{yourorganization} to successfully connect and import your data.

back to top


Connect via OAuth

To connect to ADO via OAuth:

  1. Select the OAuth tab on the Select Authentication Method page.
  2. Click Connect to Azure DevOps.
  3. Follow the prompts to sign into your ADO account.
  4. In ADO, select the organization you want to connect to Flow.
  5. Copy and paste the base URL from ADO into the Base URL field. Your URL will look like https://dev.azure.com/{yourorganization}.
  6. Click Test URL.
  7. On the following page, use toggles to select the available services you want ingested by Flow.
  8. Click Next.
  9. Name the integration.
  10. Click Create.

Flow will take you to the new integration’s Integration page and your integration will be listed on the Integrations page.

back to top


Creating a personal access token

To create a personal access token in Azure DevOps Services:

  1. Locate Personal access tokens under your user settings.
  2. On the Personal access token page, click New Token.
  3. Fill in the following information for your new personal access token:
    • Name
    • Organization
    • Expiration date
    • Scopes - Below find the minimum scopes required to connect your account.
      • Code: Read
      • Build: Read
      • Graph: Read
      • Identity: Read
      • Project and Team: Read
      • Work Items: Read
  4. Click Save.

back to top


Finalizing the connection

After creating a personal access token, complete your integration setup in Flow.

  1. Copy your access token and paste it into the Flow Personal Access Token field.
  2. Click Test connection.
  3. If the connection is successful, you'll see a Successfully connected message:

    If you receive an Authorization denied error when trying to connect your Azure DevOps Services account, verify that the access token is correct and try again.

    If you receive An error has occurred error, verify the email and base URL are correct and try again.
  4. After connecting to your Azure DevOps Services account, click Next.
  5. On the next screen, choose which services to turn on for this integration. To import pull request and ticket data in addition to repo data, leave all services on. You can turn services On and Off at any time. Click Next.

    Note: Azure DevOps Services Work Items are generally mapped to Tickets in Flow.

  6. Name the integration to identify the account you connected. Click Create.

back to top


Import repos

After creating the Azure DevOps integration, import your repos.

  1. Click Settings in the top navigation.
  2. In the left hand navigation, click Integrations.
  3. Click the integration you just created.
  4. Go to the Repos tab.
  5. Click the Repo import page link.

To learn more about managing your new Integration settings, see Manage integrations.

back to top


Troubleshooting

Follow these troubleshooting steps if you're having trouble connecting your integration.

  1. If your integration does not test successfully, check your credentials.
    • Verify your email address is the same case and spelling as seen in your Azure Profile. The email field is case sensitive.
    • Review the scopes in your access token to ensure all required scopes have been selected.
    • Confirm your base URL adheres to the required format: https://dev.azure.com/{yourorganization}. While you may be able to access your instance using either a dev.azure.com or visualstudios.com domain, Flow requires the format of https://dev.azure.com/{yourorganization} to successfully connect and import your data.
  2. If you’re unable to enable webhooks, check your Azure user permissions. In order to enable webhooks, you must be a Project Collection Administrator.
  3. If all your ADO Services ticket projects show as Vendor not supported on the Ticket projects page after your data is imported, contact Pluralsight Support (opens email form) or your Pluralsight Flow contact to unblock your repos and projects. Learn more about configuring ticket projects.

back to top


If you need help, please contact Pluralsight Support.