There are two requirements to use integration services such as repos, pull requests, tickets and webhooks:
Set up personal access token scopes. Follow the instructions below to learn more.
Make sure the service account is set up as a Project Collection Administrator at the organizational level.
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.
Azure DevOps configuration
Follow these steps to set up your Azure DevOps configuration.
First create a new integration.Starting on your Flow home page, go to the top navigation bar and click Settings. Using the left navigation under Integrations, click Integrations.
Click the Add Integration button in the top right-hand corner of your integrations screen.
On the following Integration provider page click Azure DevOps.
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}.
Note: 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 uses the visualstudios.com domain.
Creating a personal access token
Follow the instructions below to create a personal access token in Azure DevOps.
Locate Personal access tokens under your user settings
On the Personal access token page click, New Token.
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
Click Save.
Finalizing the connection
After creating a personal access token, complete your integration setup in Flow.
Copy your access token and paste it into the Flow Personal Access Token field.
Click Test connection.
If the connection is successful you will see the following message:
If you receive an Authorization denied error when trying to connect your Azure DevOps account, verify the access token and try again.
If you receive An error has occurred error, verify the email and base URL are correct and try again.
After connecting to your Azure DevOps account, click Next.
On the next screen select the 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 Work Items are generally mapped to Tickets in Flow.
Name the integration to identify the account you connected. Click Create.
You can begin to import your repos by going to your repo import page. Click the repo import page link. To learn more about managing your new Integration settings, see Manage integrations.
Import repos
After creating the Azure Devops integration, you are ready to import repos. Begin importing repos by going to your repo import page. Click the repo import page link. To learn more about managing your new Integration settings, see manage integrations
Troubleshooting
Follow these troubleshooting steps if you are having trouble connecting your integration.
If your Integration does not test successfully, you may need to check your credentials.
Check to make sure 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}
If you’re unable to enable Webhooks, check your Azure user permissions. In order to enable webhooks, you must be a Project Collection Administrator.
We use cookies to make interactions with our websites and services easy and meaningful. For more information about the cookies we use or to find out how you can disable cookies, click here.
You have disabled cookies and are browsing in private mode. For the best possible experience on our website, please accept cookies. For additional details please read our privacy notice.
