getsentry / getsentry/sentry

Azure DevOps integration cannot be installed in cross-tenant Entra ID + SSO-enforced environments

Open
#117,206 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug Product Area: Settings - Integrations
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 23m
Merged PRs (30d)
607

Description

Environment

SaaS (https://sentry.io/)

Steps to Reproduce
  1. Enforce SSO on Sentry using a corporate Entra ID tenant, blocking MSA logins.
  2. Have an Azure DevOps organization in a different tenant from the corporate Entra ID.
  3. Ensure the installing user is a Project Collections Administrator in the ADO organization.
  4. Ensure third-party application access via OAuth is enabled in ADO organization settings.
  5. Navigate to Settings > Integrations > Azure DevOps and click Add Installation.
Expected Result

The OAuth flow lists the ADO organizations the user has access to and the installation completes successfully.

Actual Result

The OAuth flow returns no ADO organizations and the installation cannot be completed. Personal Microsoft accounts (MSA) are not supported by the integration, App Registrations are not supported, and tenant ID cannot be specified in the OAuth flow.

Product Area

Settings - Integrations

Link

No response

DSN

No response

Version

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in Settings > Integrations > Azure DevOps and trace the OAuth flow described in the reproduction steps. Verify how organization discovery behaves when Sentry's Entra ID tenant differs from the Azure DevOps tenant; done means the user's accessible organizations are listed and installation completes successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, python
Domain
authentication, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.