Environment
SaaS (https://sentry.io/)
Steps to Reproduce
- Enforce SSO on Sentry using a corporate Entra ID tenant, blocking MSA logins.
- Have an Azure DevOps organization in a different tenant from the corporate Entra ID.
- Ensure the installing user is a Project Collections Administrator in the ADO organization.
- Ensure third-party application access via OAuth is enabled in ADO organization settings.
- 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
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
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