Azure DevOps: what this connector can do

Member·4 minutes to read

What this page is for

docs/connectors/azure-devops.md is the setup guide for whoever runs your organisation's Botseon deployment — registering the Microsoft Entra ID app and entering its credentials. This page is the other half: what Azure DevOps actually lets a bot do once it is connected to your account, what it asks you for along the way, its limits, and how to take the connection away again, in Botseon and at Microsoft.

List the organisations and repositories this account can reach, read pull requests, and read work items.

What a bot can do with it

Read — Azure DevOps tells a bot things, nothing changes

Tool	What it does
`azure-devops.list_organizations`	List the Azure DevOps organisations this account belongs to.
`azure-devops.list_repositories`	List the Git repositories this account can reach, in one organisation or in all of them.
`azure-devops.list_pull_requests`	List pull requests on a repository.
`azure-devops.get_pull_request`	Read one pull request: its branches, author, reviewers, status and description.
`azure-devops.list_work_items`	List recently changed work items in a project, optionally in one state.
`azure-devops.get_work_item`	Read one work item: its type, title, state, assignee and description.

Write

This connector has no write tools. A bot can only read through it.

The permissions it asks for, in plain words

Every call a bot makes through this connector is tagged with what kind of thing it is. Only the tags below ever apply here — a tag this connector's tools never carry is not listed, because it can never ask you for it.

read — Looks something up. Nothing changes, and nothing is sent anywhere. A bot never has to ask first for this.

Limits

List the organisations and repositories this account can reach, read pull requests, and read work items. Nothing outside that list is possible through this connector, however a bot is asked to use it.

Azure DevOps is also only ever as wide as the scopes your organisation's connected app actually requests — the exact scopes are on the operator's own setup page, docs/connectors/azure-devops.md, because narrowing or widening them is a decision for whoever runs your deployment, not for this page.

Disconnecting

In Botseon

Open Plugins from the sidebar, press this connector's card to open its detail page, and under Accounts press Remove next to the account — or Uninstall to remove the plugin and every account connected to it at once. Either one revokes the stored connection immediately: nothing more is read or changed through it from that moment on. Install a plugin walks through the same screen step by step.

At Microsoft

Removing the account in Botseon also asks Microsoft to revoke the token, when this deployment's connector is configured with a revoke URL. Confirm the grant is actually gone by opening the My Account → Apps and services page at account.microsoft.com (or your organisation's Microsoft Entra My Apps page) and removing Botseon there too if it still shows up. That is also where you can revoke access without going through Botseon at all, which is worth knowing if you ever lose access to your Botseon account.

What Botseon keeps, and how your data is used

Whatever a bot reads or writes through this connector becomes part of your conversations and the record of that run — the same records, and the same retention schedule, as everything else a bot works on. Botseon is the processor for that content; your organisation decides what it may read and remember, and can delete it sooner than the schedule would on its own.

Your data is sent to a model provider only to produce the bot's answer, and for nothing else — it is not used to train any model. The Privacy Policy's Models and How long we keep it sections have the full detail, including exactly how long each kind of record is kept for.