We’ve just gotten started on our 14-day SonarCloud trial period and have followed the setup guide for Azure Devops but we’re running into issues. Our private organization has been imported and connects correctly (as can be verified by following the link saying that we’re bound to Azure Devops) but when trying to find a repo in the Analyze Projects screen we get the “no repositories found for this organization” message.
We’ve tried elevating the permissions of the user that created the PAT but it hasn’t made any difference. The azure conditional access policy is Disabled, as per the guide.
I’ve not been able to find much information about this particular issue, so it feels like it’s something elementary we’re missing. What else might be causing a connection issue between our Azure DevOps and SonarCloud? Any tips on things to try?
The root cause of the issue was found, the user who created the PAT (a service account made for the task) was set to the Stakeholder access type where it should have had Basic instead. Changing the user type gave access to the repositories.
Should someone else face the same issue in the future, they can try the following:
Curl azure devops API with their AzureDevOps organization name to get the list of projects, and then for each projects, fetch the list of the repositories. If nothing is returned while fetching the repository list, it means there is something wrong on AzureDevops configuration and this is why SonarCloud can’t access the repositories.