Microsoft Teams: "Couldn't verify write access" for Azure DevOps repos; GitHub and web Cloud Agents work

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Summary

When using the Cursor bot in Microsoft Teams against an Azure DevOps repository, the bot fails for multiple users with:

Couldn’t verify write access to <org>/<project>/<repo>. Make sure to connect your account.

This does not appear to be a permissions or account-linking issue. The same Cursor account can successfully run a Cloud Agent on the same Azure DevOps repo from the web UI, and the Teams bot works when pointing at a GitHub repo instead.

Environment

  • Integration: Microsoft Teams (@Cursor bot)
  • Source control: Azure DevOps Services (dev.azure.com)
  • Repo format: {organization}/{project}/{repository}
  • Teams account linked to the same work email used for Cursor
  • Azure DevOps repo permissions for the tested user include: Read, Contribute, Create branch, Contribute to pull requests (all Allow)

Steps to Reproduce

  1. Install / connect the Cursor Microsoft Teams app.
  2. Link the Teams account to Cursor.
  3. Connect Azure DevOps in Cursor Integrations and select the target repo.
  4. In Teams, mention @Cursor with a prompt targeting that Azure DevOps repo.
  5. Observe the write-access error.
  6. Repeat with several other team members who also have Teams linked and ADO access → same error.
  7. Control A: From cursor.com/agents, start a Cloud Agent on the same Azure DevOps repo with the same account → succeeds.
  8. Control B: In Teams, run @Cursor against a GitHub repo instead → succeeds.

Expected Behavior

Teams @Cursor should verify write access and start a Cloud Agent on the connected Azure DevOps repo, the same way it does for GitHub and the same way web Cloud Agents do for that ADO repo.

Actual Behavior

Teams returns:

Couldn’t verify write access to <org>/<project>/<repo>. Make sure to connect your account.

The card still shows that the Microsoft Teams account is linked and offers Link Account, even though linking already succeeded. Re-linking does not fix it. Multiple users hit the same failure on the same ADO repo.

Evidence / Isolations

Scenario Result
Teams + Azure DevOps :cross_mark: Write access verification fails
Teams + Azure DevOps (multiple users) :cross_mark: Same failure for all testers
Web Cloud Agent + same ADO repo + same account :white_check_mark: Works
Teams + GitHub repo :white_check_mark: Works
ADO permissions (Contribute / Create branch / Contribute to PRs) :white_check_mark: Sufficient

Conclusion

This looks like a bug in the Microsoft Teams integration’s Azure DevOps write-access verification path (ADO Cloud Agents are in public beta), not missing user permissions or incomplete Teams account linking.

Workaround

  • Use GitHub repos with @Cursor in Teams, or
  • Start Azure DevOps Cloud Agents from the Cursor web/app UI instead of Teams.

Steps to Reproduce

Steps to Reproduce

  1. Install / connect the Cursor Microsoft Teams app.
  2. Link the Teams account to Cursor.
  3. Connect Azure DevOps in Cursor Integrations and select the target repo.
  4. In Teams, mention @Cursor with a prompt targeting that Azure DevOps repo.
  5. Observe the write-access error.
  6. Repeat with several other team members who also have Teams linked and ADO access → same error.
  7. Control A: From cursor.com/agents, start a Cloud Agent on the same Azure DevOps repo with the same account → succeeds.
  8. Control B: In Teams, run @Cursor against a GitHub repo instead → succeeds.

Expected Behavior

Expected Behavior

Teams @Cursor should verify write access and start a Cloud Agent on the connected Azure DevOps repo, the same way it does for GitHub and the same way web Cloud Agents do for that ADO repo.

Operating System

Windows 10/11

Version Information

Cursor bot in Teams

Does this stop you from using Cursor

Yes - Cursor is unusable

7

Hi @Dmytro_Obolonyk Thanks for the forum post! We’ve confirmed this is a bug in the Microsoft Teams integration’s write-access verification for Azure DevOps repositories. When a launch comes from Teams, the step that verifies write access doesn’t yet recognize Azure DevOps repos, so it falls back to the generic “connect your account” message even though your account is linked correctly. That’s exactly why the same repo and account succeed from the web, and why GitHub repos work fine through Teams.

We’re tracking this internally and have flagged that it’s affecting more teams now that Azure DevOps cloud agents are in public beta, so it’s on our list to fix.

In the meantime, the two workarounds you already identified are the right ones:

  • Start Azure DevOps cloud agents from cursor.com/agents or the Cursor app instead of Teams.
  • Use GitHub repos when triggering @Cursor from Teams.

Thank you again for raising this, and I will keep you updated on the status of it as we look to resolve it.

8

Hi we are seeing the same issue with Azure DevOps when using Slack also, so hopefully a fix for Teams would also fix Slack.