# SonarCloud Pull Request Run not working

**URL:** <https://community.sonarsource.com/t/sonarcloud-pull-request-run-not-working/87702>\
**Category:** SonarQube Cloud\
**Tags:** azuredevops, pipeline, sonarqube-cloud\
**Created:** [March 21, 2023, 3:11pm UTC](https://community.sonarsource.com/t/sonarcloud-pull-request-run-not-working/87702 "2023-03-21T15:11:05Z")\
**Posts on this page:** 1\
**Showing post:** 25

<div class="post-metadata">

**Author:** ![aura](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/aura/32/33600_2.png) [@aura](https://community.sonarsource.com/u/aura)\
**Post date:** [April 17, 2023, 3:39pm UTC](https://community.sonarsource.com/t/sonarcloud-pull-request-run-not-working/87702/25 "2023-04-17T15:39:14Z")

</div>

Hello @hitika26

Thanks for the additional information.

> I am not the one who created the PAT for SonarCloud, and I am not having the PAT that was used here. But I asked the user who created and added that, he had again updated the PAT but the problem still persists.

Did you try the recommendation on the [documentation](https://docs.sonarcloud.io/getting-started/azure-devops/#set-up-your-organization) about how to setup the connection with the required permissions and configuration in Azure DevOps for SonarCloud? In particular, the sections _Location of Personal Access Tokens in SonarCloud_ and _Use a technical user_ ?

Additionally, could you please make sure the Azure DevOps user creating the PAT is a basic user? I found [this thread](https://community.sonarsource.com/t/no-repositories-found-for-this-organization/78591/7) in our community about issues with the user type.

Unfortunately, our internal logs show that the pull request can’t be found and it leads to the PAT being incorrect.

Could you please send me _ **screenshots** _ of the following?

1. In Azure DevOps, when creating (or editing) a new token, show that it has scope custom define and the code has read & write selected
2. In Azure DevOps, under Organization settings, ensure that Azure Active Directory Conditional Access Policy Validation is _disabled_ if needed.
3. In Azure DevOps, under Organization settings, ensure the user creating the PAT has Basic access level
4. In your terminal, show that the curl command with `--verbose` flag suggested [here](https://community.sonarsource.com/t/sonarcloud-pull-request-run-not-working/87702/21) is working as expected
5. In SonarCloud, under the Organization Administration section and Azure DevOps connectivity management, show the status of the current token. If it’s invalid, you will see this:  
 ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/8/8/880bb43ddb449c59ae88020f5cc0c2ee4db2946a.png)

I will need all this information to proceed with the investigation so please make sure to send them all and let me know if you have any questions.

---

_[View the full topic](https://community.sonarsource.com/t/sonarcloud-pull-request-run-not-working/87702)._