I configured Azure Dev ops as my repo source in the integrations, but Cursor still fails to work on the repo. When issued a command from Slack I get an error like: “Cursor can’t write to {myorg}/{myrepo}. Please check the app installation, repository permissions, and IP restrictions.” (with the correct org and repo).
This is preventing our company from doing cloud work on Azure Dev ops repos altogether.
Steps to Reproduce
Connect Azure Dev Ops in integrations. Set a repo on Slack, then issue a command that requires code changes.
Expected Behavior
Cursor should be able to work on the repo normally.
Operating System
Windows 10/11
Version Information
Desktop Version 3.19.13 (but I’m referring to cloud and I don’t know what version that uses)
The Slack message is unfortunately generic here. What’s actually happening is that Azure DevOps is rejecting the Microsoft account Cursor is connected with. The same check fails when starting a cloud agent from the desktop app too, so it isn’t specific to Slack.
Could you try the following so we can pin it down?
Click Connect again. On the Microsoft sign-in page, make sure you pick the exact work account you use to open Azure DevOps (not a personal Microsoft account, and not a different directory).
After you’re redirected back, look at the repository list on that page. Does the forgottenmines organization (and the Doshma project repos) appear?
In Azure DevOps, open Organization settings, then Microsoft Entra: Is the organization connected to a Microsoft Entra directory, and is that the same directory your account belongs to (member, not guest)?
Two things to know in advance: organizations backed by a personal Microsoft account (not connected to Entra) aren’t supported yet, and if your account is only a guest in the organization’s directory, the connection also won’t work today.