Azure DevOps

The Azure DevOps integration connects Azure DevOps Services repositories to Cloud Agents and Bugbot.

Supported features

Cloud Agents clone your code, work on branches, and open pull requests. Bugbot reviews pull requests and posts its findings as comments.

The following features don't support Azure DevOps yet:

• Automations
• Bugbot autofix
• Security Agents, including Security Reviewer and Vulnerability Scanner

These features work with GitHub today. Azure DevOps support is on the roadmap.

Setup

Requires access to the Azure DevOps organizations and repositories you want to use with Cursor.

1. Go to Integrations in the dashboard
2. Click Connect next to Azure DevOps
3. Sign in with the Microsoft account you use for Azure DevOps
4. Review the Microsoft Entra OAuth consent screen and approve access
5. Return to Cursor and select repositories from your Azure DevOps organizations
6. Configure Cloud Agents on the repositories you want Cursor to use

To disconnect your Azure DevOps account, return to the integrations dashboard and click Disconnect Account.

Set up Bugbot

Bugbot reviews Azure DevOps pull requests under a Microsoft Entra service principal that Cursor provisions in your tenant. That service principal installs the service hooks Bugbot listens to, reads pull request diffs, and posts review comments and build statuses. Setup runs once per Azure DevOps organization.

Bugbot on Azure DevOps works on team repositories. Personal-scope repositories aren't supported.

Grant Microsoft Entra admin consent

Requires a Microsoft Entra ID administrator holding the Global Administrator, Application Administrator, or Cloud Application Administrator role. Consent applies to the whole tenant, so a repository administrator alone can't complete it.

1. Connect Azure DevOps from Integrations in the dashboard while signed in as an administrator of the Azure DevOps organization
2. Ask your Entra administrator to grant admin consent for the Cursor application in your tenant
3. Tell your Cursor contact once consent is granted

Cursor asks for access to the Azure DevOps API, plus the standard sign-in scopes. It asks for no Microsoft Graph data. Your tenant keeps the service principal, and you can revoke it in Entra at any time.

Give the service principal access to your organization

After consent, Cursor adds the service principal to your Azure DevOps organization and requests a Basic access level for it. Both happen automatically, using the administrator account that connected Azure DevOps. The service principal then appears under Organization settings → Users.

Three things can stop that:

• The connected account can't add users to the organization. Reconnect Azure DevOps as an administrator of the organization.
• No Basic access level is available. Free a Basic seat, or assign one to the service principal under Organization settings → Users.
• The service principal can't read the repository. Grant it Read permission on that repository under Project settings → Repositories → Security.

Enable Bugbot on repositories

1. Open Bugbot in Automations
2. Find your Azure DevOps repositories in the installations list
3. Turn Bugbot on for each repository you want reviewed

Bugbot installs its service hooks when you turn a repository on, and removes them when you turn it off. Turning Bugbot off for a repository, or disconnecting Azure DevOps, stops reviews for that repository right away.

How reviews are triggered

Bugbot reviews each pull request as it opens and updates. Someone can also ask for a review on demand by commenting cursor review or bugbot run.

Comment triggers have one Azure DevOps limit. They work for people whose Azure DevOps sign-in address matches a Cursor account in the team that owns the repository. A comment from anyone else is ignored without a reply. Automatic reviews carry no such limit, and they cover every author.

Filter which authors get reviewed

Bugbot reviews every author by default. To narrow that, turn off Run for All Authors in the repository's Bugbot settings, then pick Only Review PRs by... or Skip PRs by....

That list takes Azure DevOps sign-in addresses, not usernames, and the field is labeled that way. A sign-in address looks like taylor@contoso.com, and it's the value your organization administrator reads under Organization settings → Users. A username matches nobody, so Bugbot stays quiet for that author.

Differences from other providers

Repository settings and repository rules work on Azure DevOps. These don't:

• Auto-Enable for New Repositories. Turn Bugbot on for each new repository yourself.
• Automatically Learn Rules. Repository rules you write by hand still apply.
• Personal Bugbot settings. Repository settings apply to everyone instead.
• Autofix. Bugbot reports its findings without opening fix commits.

Build statuses and branch policies

Bugbot posts a build status on each reviewed pull request under the context cursor-bugbot/review. See CI check statuses for what each conclusion means.

If you make that context a required status branch policy, set the policy's Reset conditions to Reset status whenever there are new changes. Without it, a status from an earlier push keeps satisfying the policy after new commits land.

Repository URLs

Cursor supports Azure DevOps Services repository URLs in this format:

https://dev.azure.com/{organization}/{project}/_git/{repository}

Azure DevOps uses an organization, project, and repository hierarchy. Cursor shows repositories as {project}/{repository} under the Azure DevOps organization.

If your organization still uses a *.visualstudio.com URL, open the repository in Azure DevOps and copy the dev.azure.com URL before adding it to Cursor.

Permissions

Cursor connects to Azure DevOps through Microsoft Entra OAuth. The connection lets Cursor:

Bugbot adds a second identity. Cursor provisions a Microsoft Entra service principal in your tenant and uses it for every Bugbot action, so reviews keep running when the person who set the integration up changes roles or leaves.

Troubleshooting

Next steps

Once your Azure DevOps integration is connected, configure the features that use it:

• Bugbot - automated PR reviews that catch bugs and security issues
• Cloud Agents - AI agents that run in the cloud on your repositories
• Cloud Agent setup - saved environments, multi-repo setup, secrets, and Dockerfiles