To use all integration services such as repos, pull requests, tickets and webhooks, two conditions must be met. First, please review the personal access token scopes outlined below. And second, the service account needs to be a Project Collection Administrator at the organizational level.
If webhooks are not needed, the permission required to establish a connection and import repos is View instance-level information at the user level, and the user needs to be added to the reader group at the project level.
Azure DevOps configuration
In order to connect your Azure DevOps account, you will need to 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 page click Azure DevOps.
On this page you will need to input the following information:
Email - Email associated with the service account.
Tip: This field is case sensitive. Use the exact email format seen in your Azure user profile.
Personal Access Token (see below)
Base URL - https://dev.azure.com/{yourorganization}
Tip: Even if your base URL in Azure Devops uses the visualstudios.com domain, you will need to use the https://dev.azure.com domain in the "Base URL" field in Flow for the connection to be successful.
Creating a personal access token
To create a personal access token in Azure DevOps follow the instructions below.
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
Now that you have created a personal access token you can 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 was successful you will see the following message:
If you receive an “Authorization denied” error when trying to connect your Azure DevOps account verify access token and try again.
If you receive “An error has occurred” error verify that the email and base URL are correct and try again.
Once you have successfully connected to your Azure DevOps account, click Next.
On the next screen you will be selecting the services you want turned on for this integration. If you would like to import pull request and ticket data in addition to repo data, then 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 your integration so you can identify the account you connected with. Click Create.
You have successfully created a new Azure Devops integration.
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.
Troubleshooting
If you are unable to get your integration setup or connected, please see the following guidance:
If your Integration does not test successfully:
Upon receipt the following error message when testing your integration connection, please review the following information.
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.
If your projects appear in your Webhooks tab, but nothing happens when you click enable next to a repo, this could indicate that your Azure user permissions are not sufficient. 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 policy.
