Tools Connect: Azure DevOps

Allstacks pulls tickets, cards, stories, and other units of work from your project management tools such as Azure DevOps. We combine that with data about deliverables and milestones such as releases, epics, features, and projects and activities such as estimation changes, completions, comments, and status updates to provide a very comprehensive picture of your work.

Allstacks service connection to Azure DevOps is established either via OAuth or Personal Access Token. We recommend connecting using Azure DevOps (OAuth) although Azure DevOps(Basic) maybe used for short term trials.

1 Azure DevOps (OAuth)
2 Azure DevOps (Basic) - Connect using Personal Access Token

Azure DevOps (OAuth)

Before starting, confirm that you are actively signed into Azure DevOps with the account, preferably service account, you wish to connect to Allstacks.
In Allstacks, click on "Add Tool" and select Azure DevOps (OAuth) as an option to connect to Azure DevOps SaaS. You will simply need to provide Azure DevOps URL
- Note: In some cases, you may have to Authorize access to Azure DevOps REST APIs with OAuth 2.0. We are expecting Read permissions for all categories on this page.
On clicking "ADD TOOL" you will be redirected to Azure DevOps to authorize Allstacks for read access permissions.

Review and accept Read permissions to continue.
Azure DevOps Tools Connection: Review and accept Read permission scopes
On successful connection, you will see a list of resources you can toggle on and off the projects. In the event this list is blank you may need to press “Refresh Resources”.

Azure DevOps (Basic) - Connect using Personal Access Token

Before starting, confirm that you are actively signed into Azure DevOps (ADO) with the account, preferably service account, you wish to connect to Allstacks.
In Allstacks, click on “Add Tool” and select Azure DevOps (Basic) as an option to connect to ADO SaaS.
The Azure DevOps Instance URL should point to the base URL for your ADO project collection. To view the base URL, you could sign in to the ADO application-tier server, open Administration Console, and select the Team Project Collections node:https://learn.microsoft.com/en-us/azure/devops/server/admin/manage-project-collections?view=azure-devops-2022#view-information-or-configure-existing-project
Create ADO personal access token (PAT) with read access permission scope, and connect ADO to Allstacks using that token. We are expecting Read permissions for all categories on this page.
- We recommend setting the expiration date to the maximum duration of one year for customers.
- Note: Make sure you select “Show All Scopes” at the bottom of the token creation menu.

Below are the required permissions for your Allstacks connection.

Now in Allstacks clicking “ADD TOOL” you will direct you to the Allstacks service connection workflow. Select Refresh Resources to enable the ADO projects.

Note that the user put into the screenshot below MUST be the same user that created the PAT.

On successful connection, you will see a list of resources you can toggle on and off the projects. In the event this list is blank you may need to press “Refresh Resources”.