Azure DevOps Server (ADO Server) setup

Follow this step-by-step guide to connect your Azure DevOps Server (ADO Server) account to Flow. Data about ADO Server work items appear in the Work log, but not in other ticket-based reports.

For a successful connection:

• Allowlist Flow's static IP addresses on port 443 over HTTPS.

• Have an SSL certificate that uses a public certificate authority.

• Have a public DNS record pointing to the IP address exposed for Flow analysis.

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

Azure DevOps Server Version requirements

To integrate with Flow, your Azure DevOps Server version must be 2019 or higher.

Permission requirements

To use all integration services, such as repos, pull requests, tickets, and webhooks, ensure the following:

• You have reviewed the personal access token scopes outlined below.

• The service account is a Project Collection Administrator at the organizational level.

To enable webhooks, the service account must be a Project Collection Administrator and have at least one repository imported from a project.

If you don't need webhooks, allow the View instance-level information permission to establish a connection and import repos. Add your service account to each project you want to import into Flow.

Open

Create a personal access token

Create a personal access token in Azure DevOps Server (external site).

1. Fill in the following information for your new personal access token:

   • Description

   • Expiration date

   • Select the following minimum scopes to connect your account:

     • Code (read)

     • Code (search)

     • Identity (read)

     • Project and team (read)

     • Service Endpoints (read and query)

     • User profile (read)

     • Work items search (read)

     • Work items (read)

2. Click Create.

Create your integration

To connect your Azure DevOps Server account:

1. Click Settings in Flow’s top navigation.

2. In the left navigation under Integrations, click Integrations.

3. Click Add integration.

4. On the Integration Provider list, click Azure DevOps Server.

5. Optional: If you see the Direct Connection or Hybrid Connection, select one.

6. Next, select your authentication method with ADO: Access token.

7. Input your email, password, personal access token, and base URL of the service account. The base URL looks like: https://{your_ADO Server_domain}/{yourorganization}.

Open

8. Input your username, password, Personal access token, and Base URL.

9. Click Test connection. If the connection is successful, you'll see a Successfully connected message:

Open

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

• If you're notified that An error has occurred, verify the username, password, and base URL are correct and try again.

After connecting to your Azure DevOps Server account, click Next.

10. On the following page, use toggles to select the available services you want ingested by Flow: Repos, Pull Requests, and Tickets.

11. Toggle the Repos, Tickets, and Pull requests services on or off to determine which data types Flow will ingest for this integration. After you've made your selections, click Next. Azure DevOps Services Work Items are generally mapped to Tickets in Flow.

12. Name your integration. This is the name Flow will display for the integration. Choose a name that will help you identify the integration later.

13. Click Create.

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

Troubleshooting

If you can't get your integration set up, try these troubleshooting options:

Could not connect to URL

If you receive a Could not connect error message when you test your integration:

• Check that your base URL is correct. It should be in the following format:
  https://{your_ADO_Server_domain}/{yourorganization}

• If you're behind a firewall, review the initial setup of the connection—allowlist IPs, have a public DNS, and have a certificate signed by a public CA.

Authorization denied

If you receive an Authorization denied error, check your credentials and personal access scopes, then try again.

Connection tests successfully, but I can't see all my projects and repositories

If you don't see all the projects or repos you expect, double-check your permissions at the organization and project level. If you aren't a Project Collection Administrator, you need to be added to each project you want to add to your Flow account.