Answer: Bugbot may not review your Azure DevOps pull requests if the repository isn't turned on in Bugbot in Automations, if the repository belongs to a personal-scope rather than a Cursor team, if the Cursor service principal isn't in the project's Project Administrators group, or if author filtering excludes the pull request author's Azure DevOps sign-in address. Status: Confirmed Entry: tool/cursor/troubleshooting/bugbot-not-reviewing-azure-devops-prs Revision: 1 Digest: sha256:a5a256d6ae7c7d45 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:10:53Z Last changed: 2026-11-13T03:10:53Z Last verified: 2026-11-20T12:38:13Z Next check: 2026-11-21T12:38:13Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Repository enabled | Confirm the repository is turned on in | [1] | 2026-11-20 Team scope requirement | Bugbot on Azure DevOps doesn't review personal-scope repositories | [1] | 2026-11-20 Required group | Project Administrators | [1] | 2026-11-20 Author filter | Azure DevOps sign-in address rather than username | [1] | 2026-11-20 Sources: [1] Anysphere. "cursor.com/docs/integrations/azure-devops.md". https://cursor.com/docs/integrations/azure-devops.md Role: primary. Accessed: 2026-11-20T12:38:13Z Quote: "Confirm the repository is turned on in [Bugbot in Automations](https://cursor.com/automations/from-cursor/bugbot)." (Supports: Repository enabled) Quote: "Confirm the repository belongs to a Cursor team. Bugbot on Azure DevOps doesn't review personal-scope repositories." (Supports: Team scope requirement) Quote: "Confirm the Cursor service principal is in the project's **Project Administrators** group under **Project settings** → **Permissions**." (Supports: Required group) Quote: "If you filter authors, confirm the pull request author is listed by Azure DevOps sign-in address rather than username." (Supports: Author filter) Snapshot SHA-256: 0112fa96f1bad7a8f2a82f682d48b09d525426e9376550e6b3b0c6db90a5f55d (captured 2026-11-13T03:10:52Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:10:53Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:38:13Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:38:13Z Last attempt: 2026-11-20T12:38:13Z Notes and limitations: Extracted automatically from a single official source (section "Bugbot doesn't review my pull requests"). Related: https://latestn.com/tool/cursor/troubleshooting/check-migration-needed How do I check whether my Cursor Agent SDK project needs migration to architecture v2? https://latestn.com/tool/cursor/troubleshooting/cli-auth-status How do I check my Cursor CLI authentication status? https://latestn.com/tool/cursor/troubleshooting/cli-not-authenticated-fix How do I fix 'Not authenticated' errors in Cursor CLI? https://latestn.com/tool/cursor/troubleshooting/agent-cannot-access-repo What should I do if the Cursor agent can't access my repository? https://latestn.com/tool/cursor/troubleshooting/api-error-responses What are the common error responses from Cursor APIs? https://latestn.com/tool/cursor/troubleshooting/bitbucket-workspace-not-found Why can't Cursor find my Bitbucket workspace or list my Data Center repositories? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:10:53Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cursor/troubleshooting/bugbot-not-reviewing-azure-devops-prs/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cursor/troubleshooting/bugbot-not-reviewing-azure-devops-prs POST: https://latestn.com/dispute/tool/cursor/troubleshooting/bugbot-not-reviewing-azure-devops-prs with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cursor/troubleshooting/bugbot-not-reviewing-azure-devops-prs?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). Why doesn't Bugbot review my Azure DevOps pull requests in Cursor? Revision 1, last verified 2026-11-20T12:38:13Z. https://latestn.com/tool/cursor/troubleshooting/bugbot-not-reviewing-azure-devops-prs (accessed 2026-11-21T10:03:11Z). @misc{LatestN_tool_cursor_troubleshooting_bugbot_not_reviewing_azure_devops_prs_r1, title = {Why doesn't Bugbot review my Azure DevOps pull requests in Cursor?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cursor/troubleshooting/bugbot-not-reviewing-azure-devops-prs}}, note = {Revision 1; digest sha256:a5a256d6ae7c7d45; last verified 2026-11-20T12:38:13Z; accessed 2026-11-21T10:03:11Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cursor/troubleshooting/bugbot-not-reviewing-azure-devops-prs