Hi Martin,
Azure Devops Services are Transitioning to New IP Addresses https://status.dev.azure.com/_event/639229775. Could these be updated with the new IP Addresses?
The IPs documented here are the IP addresses that SonarQube Cloud uses to communicate with other services. If Azure DevOps Services is using new IP addresses, it shouldn’t affect anything on our end.
Hi Colin,
Thanks a lot. We are noticing that the Sonarcloud Quality check on PR’s in our Azure Devops are not completing, does Sonarcloud not have to update anything on their side?
It looks more like an issue with the token you have configured (global Administration > Organization settings > Organization binding. Specifically, in the backend I can see several successful API calls to Azure DevOps using that token, but a 401 when a POST is submitted to https://dev.azure.com/{organization}/{project}/_apis/git/repositories/{repositoryId}/pullRequests/{pullRequestId}/iterations/1/statuses?api-version=6.1-preview.1
I would suggest you make sure this token has the correct scopes, or try generating a new one you’re sure has the right scope.