Connect Azure DevOps
Connect an Azure DevOps organization and its repositories: sign-in and consent, the personal access token, the service hooks, and replacing the token.
Connecting Azure DevOps takes three things: a Microsoft Entra sign-in that identifies your organization, a personal access token (PAT) that codingassist uses to work with your repositories, and service hooks on each repository you connect.
Connect the organization
Sign in
At app.codingassist.bot, click Continue with Azure DevOps and sign in with a Microsoft work or school account.
Approve access
The first time, an Approve Codingassist dialog asks for Azure DevOps access. An Entra administrator approves it. A user who is not an administrator can click Copy an approval link and send it to one.
Pick the organization
Under Select an organization, choose the organization and click Authorize & continue. Only organizations where you are in Project Collection Administrators can be selected; for the others, click Request access.
Save the PAT
Paste a personal access token for that organization and click Save PAT.
Connect a repository
On the Repositories page, under Available to connect, click Connect next to the repository. Only Owners and Admins can connect repositories, and each plan has a repository limit. See Billing.
For each connected repository, codingassist creates three Azure DevOps service hooks:
| Event | Used for |
|---|---|
| Pull request created | Starts a review |
| Pull request updated | Starts a review of the new commit |
| Pull request commented on | Answers commands in comments |
Connecting a repository also queues the indexing of its default branch, used to find similar code during reviews. See Data governance.
The personal access token
codingassist uses the PAT for every call to Azure DevOps after sign-in. With it, codingassist:
- lists projects and repositories
- reads pull requests, changed files and work items
- posts the summary comment, inline comments and the status
- creates the service hooks when a repository is connected
Create the token with an expiry that suits your policy. When it expires, reviews stop until it is replaced.
Replace the token
Open Access tokens
In the web app, go to Organization > Access tokens.
Revoke the current token
Click Revoke. A new token cannot be added while a valid one is active.
Add the new token
Click New token, paste the new PAT and save it. Use Recheck to confirm codingassist can use it.