Is your SonarQube Cloud org bound to the correct Azure DevOps org?
Because if so, you should just need an org admin to update the token in your SonarQube Cloud organization settings. (Org-level Administration > Organization Settings > Organization binding).
our Sonar Cloud and Azure DevOps Org were setup in a functional way and used to work before the owner of the personal account for bonding left.
Just updating the token can not work as all ADO tokens are bound to an account. And the current account is disabled.
A token from a different person can not work, as a token by itself does not contain information for which account it is valid. But it will only be valid for the account who created it.
And as this was proposed before, we actually tried it but it failed as expected.
So we need the account for bonding changed in the backend / database.
I’m sorry Daniel, but I’m really not following.
SonarQube Cloud does not care who the user who created the token is. Two different users with the correct permissions can generate tokens and swap them them in/out as needed for the binding. The token just needs to have permissions to the org it is bound to.
What error do you get when you try to replace the token with a new one?