Unable to Update PAT from ADO

SonarQube Cloud
, ,
1

  • ALM: Azure DevOps

  • CI: Azure DevOps

  • Issue:
    Recently one of our repos stop pushing new branches to SonarCloud resulting in this error when running in CI
    ERROR Could not find the pullrequest with key '111'

    After troubleshooting I discovered the Organization Binding menu showed the current PAT as invalid. This is the first oddity, as the current PAT doesn’t expire until August of this year.
    I decided to generate a new PAT to replace this one and keep getting this error when trying to update it.
    Failed authentication, the token used is likely not valid

    Looks like the PATCH /dop-translation/organization-bindings/{some_id} is returning a 400 with the above as the response message.

  • To reproduce: Navigate to Administration > Organization binding > Edit token. Enter new valid token > Update token

  • For reference:
    I have looked into some various other PAT issue threads but none of them seem to cover this issue.
    Update exiting (vaild) PAT
    Valid Azure DevOps PAT stops working after a few weeks
    Updating PAT token not working

2

Hey there.

I was just able to update the PAT in my Azure DevOps org, so I doubt there’s a widespread issue here.

Is it possible that something changed in your Azure DevOps organization to no longer allow calls in from the outside? Sometimes you need to whitelist certain IPs.

You can also run into issues if you have Conditional Access in Microsoft Entra ID
turned on.

3

Thanks Colin. This was caused by a new policy in Microsoft Entra.

1 Like