Recommended SonarCloud architecture for multiple Azure DevOps organisations under one Enterprise pla

SonarQube Server / Community Build
,
1

We are an Enterprise customer with one SonarCloud enterprise (PETRONAS Digital) and three Azure DevOps organisations: Digital-Delivery, petronasvsts, and OEX-PPM.

We understand that SonarCloud org-to-ADO org binding is one-to-one and permanent. Our current SonarCloud org is bound to Digital-Delivery. To cover petronasvsts and OEX-PPM, we would need to create separate SonarCloud orgs under the same enterprise.

We are currently at 92% of our 40M LOC shared capacity with an active “Action Required” warning. We have approximately 20 to 30 additional projects being migrated to Digital-Delivery, plus we need to cover the other two ADO orgs.

Our questions:

  1. What is the recommended architecture for this multi-ADO-org scenario under one Enterprise?
  2. When creating a new SonarCloud org for petronasvsts, does it automatically sit under the same enterprise hierarchy and share the LOC pool?
  3. Can LOC capacity be reallocated between existing organisations within the enterprise, or does expansion always require a tier upgrade?
  4. Is there a process for an account review given our LOC warning and incoming project volume?
2

Hello @Rhyss_Haiqal,

I can see you also have a support ticket in our Help center open for this. Since the support team will be able to look into the specifics of your organization directly and help you more efficiently there, I’d recommend continuing the conversation in that channel.

In the future please submit your requests to the Help center since your team has a Support contract.

I’ll close this thread to avoid any duplication.

Cheers,

Stevan