ALM used: Azure DevOps
CI system used: Azure DevOps
Scanner command used: Azure DevOps task SonarCloudPrepare@1 (token masked)
Languages of the repository: TypeScript, JavaScript, Java, Python
SonarCloud project URL (if public): Not applicable
Issue description:
We were previously using SonarCloud, and recently upgraded to the SonarQube Enterprise (4M LOC) cloud plan.
Now, when I click on my current organization, I see the following message:
"Upgrade to enterprise
Upgrading to an enterprise will create a new enterprise entity under which all of your SonarQube Cloud organizations can be grouped. No data will be lost, and you can downgrade at any time."
I understand that a new enterprise entity will be created, but I have a few important questions before proceeding:
- What are the impacts of migrating to SonarQube Enterprise?
- Will my current SonarCloud organization be modified or affected?
- Will a new organization be created automatically, or will the migration preserve the existing structure transparently?
- Is it mandatory to complete this upgrade in order to enable SSO (Microsoft Entra ID)?
- If so, what are the exact steps to enable SSO for my current organization, or for the new enterprise entity?
- Can I perform this upgrade and SSO configuration without breaking current CI/CD flows in Azure DevOps?
Steps to reproduce:
-
Log into SonarCloud with an organization under the new Enterprise plan.
-
Click on the organization.
-
See the message about upgrading to enterprise and creating a new entity.
Potential workaround:
We are trying to avoid re-creating our organization from scratch or breaking the integration with Azure DevOps pipelines. Ideally, we want a transparent migration path to Enterprise while enabling SSO.
Looking forward to clarification on this process and best practices for a smooth transition.
Thanks in advance!

