Azure DevOps admin consent loop when installing the integration

[rodolfoBee]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

With a user with Owner or Manager permissions in Sentry but no admin permissions in Azure:

1. Go to integrations -> Azure devops and try to install the integration
2. Get the prompt that an Admin in Azure needs to consent to the requested scoped access required by the Sentry app
3. An admin in Azure consents to the scopes required.
4. Try to install the integration in Sentry again.

Expected Result

With Azure admin's consent already given the integration is installed.

Actual Result

The integration is not installed and an admin is requested to give consent again.

The current workaround is to use a user with required permissions in both services to install the integration:

Sentry organization owner, manager, or admin permissions, as well as Azure organization owner permissions, or be a user in the Project Collections Administrators group.

This has been reported in a few internal issues, including this one

Product Area

Settings - Integrations

Link

No response

DSN

No response

Version

No response

[getsantry]

Auto-routing to @getsentry/product-owners-settings-integrations for triage ⏲️

[sentaur-athena]

This is a known issue. Will provide an update soon.

[sentaur-athena]

We disabled consent for everyone. @rodolfoBee can you please confirm if the issue is fixed?