SonarCloud Organisation user onboarding process

  • ALM used: Azure DevOps
  • CI system used: Azure DevOps
  • Scanner command used when applicable: n/a
  • Languages of the repository: n/a
  • Steps to reproduce: n/a
  • Potential workaround: unknown

To roll-out SonarCloud in our orgnanisation we need to define or automate the developer onboarding process. If a new developer joined the organisation the process would look something like:

  1. Manager creates support ticket
  2. Support staff creates a new user in AD
  3. Support staff adds user to group that permits access to Azure DevOps
  4. Wait until AD syncs with AAD
  5. Developer logs into and authenticates using AAD credentials
  6. Developer views their account profile and tajkes note of their SCM Account ID (i.e. joe-blogs12345)
  7. Developer updates support ticket with SCM Account ID
  8. SonarCloud administrator adds a new member to the organisation
  9. SonarCloud administrator adds a user by searching for the developer by SCM Account ID
  10. SonarCloud administrator applies necessary permissions

As you can see the process is quite long and requires a lot of hand-off between the support team, the developer and the SonarCloud admin.

Given the size of the organisation and the frequency that developers come and go the overhead of user management will quickly become a burden on our support team. How are other organisations managing developers in SonarCloud? Is there a way to streamline and/or automate the onboarding process?


Hi @warner-godfrey!

Currently, there is no other way to simplify this process. In the next couple of months, we are going to improve the organization & project onboarding for Azure DevOps (MMF-1829 should be one of the first steps), which is a first step towards creating a stronger link between SonarCloud and Azure DevOps worlds. Once SonarCloud orgs are bound to Azure DevOps ones, we might be able to automate some stuff like adding members automatically to the org (like what is done for GitHub).