We are trying to move away from personal access tokens and instead use a Scoped Organization Token for SonarCloud.
Our SonarCloud organization contains 109 projects. We created a new Scoped Organization Token and explicitly assigned it to 3 specific projects. All these projects are private projects.
When we apply this token to our SonarCloud service connection in Azure DevOps (Edit Service Connection → paste new token → Verify), the verification fails with a server-side error.
We also waited some time after creating the token (in case propagation or initialization was required), but the error persists consistently.
The error we get is this one:
Failed to query service connection API: 'https://sonarcloud.io/api/organizations/search?member=true'. Status Code: 'InternalServerError', Response from server: '{"errors":[{"msg":"An unexpected error occurred. Please try again later."}]}'
Any help would be appreciated, as we would really like to adopt scoped tokens instead of personal ones. What can we do to make this setup work correctly?
Thanks in advance!