The settings you’ve already updated (Organization Name, URL, Key) are SonarCloud’s own metadata, they don’t affect the underlying Azure DevOps connection. The AZURE_DEVOPS_UNABLE_TO_FETCH_REQUESTED_RESOURCE error means SonarQube Cloud is still trying to reach your old ADO URL ( Azure DevOps Services | Sign In ).
The ADO connection is stored separately. To update it:
Go to Organization → Administration → Organization settings → DevOps Platform Integration
Find the Azure DevOps connection record
Update the ADO organization URL from dev.azure.com/OrgA to dev.azure.com/OrgB
Provide a fresh Personal Access Token with the required permissions on OrgB
Once updated, project imports should work again. Note: this is specifically supported for renames of the same ADO organization (same org, new URL), it’s distinct from moving to a wholly different ADO organization, which SonarQube Cloud doesn’t support without creating a new SonarCloud organization.
Let us know if you hit any issues after updating the integration settings.
I need to correct my previous response, I confused the steps for SonarQube Server vs SonarQube Cloud. The Organization binding setting only allow updating the Personal Access Token, not the ADO organization URL.
SonarQube Cloud doesn’t have a mechanism at the moment for changing ADO binding (which includes the organization URL). There is no self-service UI path to update it from dev.azure.com/OrgA to dev.azure.com/OrgB.
The only supported path is to create a new SonarCloud organization, bind it to dev.azure.com/OrgB, and recreate/re-analyze your projects. Note, this does mean losing previous analysis history.