I don’t really know where to start with this, I am confusing myself more and more with each snippet of troubleshooting I do. Apologies for the brain dump I am about to write!
I have two issues:
1. BitBucket users not able to loging using Azure/EntraIS SSO
So we have an Enterprise which has Azure/EntraID SSO configured.
Under that we have only one organisation which is bound to BitBucket.
I can log in to the platform using SSO and I can see everything.
I can also login using BitBucket and see everything.
I am an admin for all.
I have tried to replicate this for a standard user.
My chosen test user is able to log in using BitBucket and their account appears in the Members section of my Organisation.
I have added them to the users/groups in Enterprise app configuration in Azure/EntraID.
But when they log in, their name does not appear in the same Members list so I cannot assign any groups to them and they cannot see anything.
2. Azure DevOps users cannot be added to groups
To complicate things even more, I have another bunch of users who wish to bind to Azure DevOps.
I have created a new test Organisation for this and bound it.
If I log in with my Azure DevOps account, when I log back in as admin (using SSO or BitBucket) so that I can add this DevOps linked account to the correct group, the organisation has vanished from my admin view.
It must still be there because if I try to recreate it I get the message “This Azure DevOps organization has already been bound to a SonarQube Cloud organization.”
So, where has it gone? How do I admin it?
I am not really having a great time with this and the whole integration/account management side of things is way too overcomplicated.
Please help!
Also, how do I get some premium support to help with this?
- ALM used → Bitbucket Cloud & Azure DevOps
- CI system used → Bitbucket Cloud & Azure DevOps
- Scanner command used when applicable (private details masked) → N/A
- Languages of the repository → English
- Only if the SonarCloud project is public, the URL → N/A
- And if you need help with pull request decoration, then the URL to the PR too → N/A
- Error observed (wrap logs/code around with triple quotes ``` for proper formatting) → See above
- Steps to reproduce → See above
- Potential workaround → No workaround