Migrating from SonarCloud to SonarQube Enterprise – SSO setup and organization migration questions

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:

  1. What are the impacts of migrating to SonarQube Enterprise?
  2. Will my current SonarCloud organization be modified or affected?
  3. Will a new organization be created automatically, or will the migration preserve the existing structure transparently?
  4. Is it mandatory to complete this upgrade in order to enable SSO (Microsoft Entra ID)?
  5. If so, what are the exact steps to enable SSO for my current organization, or for the new enterprise entity?
  6. Can I perform this upgrade and SSO configuration without breaking current CI/CD flows in Azure DevOps?

Steps to reproduce:

  1. Log into SonarCloud with an organization under the new Enterprise plan.

  2. Click on the organization.

  3. 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!

Hey there.

Congrats on upgrading to Enterprise!

All your questions are answered in our Enterprise onboarding documentation, but in summary:

When you upgrade to Enterprise:

  1. A new Enterprise will be created
  2. Your existing organization will be moved under that Enterprise (that Enterprise becomes the “parent” of the organization"

Everything about the existing organization will stay in tact.

Yes. SSO can only be enabled on an Enterprise.

For that, I will defer to the docs on Setting up SSO. There are specific pages for Microsoft Entra ID!

Yes, however when you eventually remove the DevOps Platform-authenticated users from your organization, you’ll want to make sure that you switch out any tokens you’re setup for analysis (likely in your Azure DevOps Service Connection) with a new token for an SSO-authenticated user.

Thank you to the Excelent answer and clarify.

Now, I’m ok to execute this steps.

Regards,