> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-cloud/managing-your-account/signing-in.md).

# Signing in to SonarQube Cloud

Signing in to SonarQube Cloud is easy using your DevOps platform service or through your SSO if SAML authentication is set up for your Enterprise.

Sign in to SonarQube Cloud [via your DevOps platform service](https://www.sonarsource.com/trust-center/#authentication) (GitHub.com, Bitbucket, GitLab, or Azure DevOps) or through Single Sign-On (SSO) if it's configured in your enterprise. There's no SonarQube Cloud-only account.

The **GitHub** login option supports GitHub.com accounts only. GHE.com and GitHub Enterprise Server (GHES) credentials cannot be used with this option. For initial enterprise setup, see [Before you start](/sonarqube-cloud/getting-started-with-enterprise/setting-up-your-enterprise.md#before-you-start).

<div align="left"><figure><img src="https://2223713658-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FB4UT2GNiZKjtxFtcFAL7%2Fuploads%2Fgit-blob-1c4f25a862a4c6c41d3a9272c9810a870c8770ff%2Fsonarqube-cloud-login-page.png?alt=media" alt="Sign in to SonarQube Cloud using either your DevOps service or with SSO if SAML authentication is set up for your enterprise. Use the region toggle to select the EU or US region."><figcaption></figcaption></figure></div>

{% hint style="info" %}
SonarQube Cloud doesn’t simultaneously support two accounts with the same email address. If you already have a SonarQube Cloud account and want to sign in to SonarQube Cloud with another DevOps platform account associated with the same email address, SonarQube Cloud will warn you that doing so will dissociate your first account from SonarQube Cloud (Signing in again with this account will re-associate it).
{% endhint %}

{% hint style="info" %}
If you no longer have access to the DevOps platform account or associated e-mail address that was used to sign in to SonarQube Cloud, you will not be able to restore your account and will have to create a new one.
{% endhint %}

## Signing in via your DevOps platform service <a href="#via-devops-platform" id="via-devops-platform"></a>

When you sign in for the first time, your SonarQube Cloud account is created and bound to your account on the DevOps platform.

### Prerequisites for your DevOps account's email address

To use all the features of SonarQube Cloud, the email address in your DevOps account must be verified. If it’s not the case, you’ll face the inability to join an organization, be assigned issues, receive notifications, or import an organization.

For Azure DevOps users:

* SonarQube Cloud considers an email address as verified if its domain has been verified in Microsoft Entra ID.
* If it’s not the case, a one-time email address verification is required. SonarQube Cloud provides guidance through this email verification process during your initial sign-up.

For other users, check your DevOps platform’s documentation for email verification steps. For GitHub users, see [Verifying your email address](https://docs.github.com/en/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/verifying-your-email-address#verifying-your-email-address).

{% hint style="info" %}
If you're using GitHub Enterprise Managed Users (EMU) and get the error "The email had already been verified on another account," remove the alternate email address:

1. Go to GitHub's [Email is already verified by another user](https://docs.github.com/en/account-and-profile/how-tos/email-preferences/troubleshooting-email-verification#email-is-already-verified-by-another-user) troubleshooting steps.
2. If you see `Error adding EMAIL: Email is already verified by another user`, either unverify the email on the other account or choose a different email address to verify.
3. To unverify an email address, delete it in your email settings. You can optionally re-add it without verifying to keep commits linked to your account. See [Changing your primary email address](https://docs.github.com/en/account-and-profile/how-tos/email-preferences/changing-your-primary-email-address).
   {% endhint %}

### Signing in

To sign in to SonarQube Cloud via your DevOps platform service:

1. Go to `https://sonarcloud.io/login` or `https://sonarqube.us/login`, and use the region toggle to select your region.
2. Select your DevOps platform. You’re redirected to your DevOps platform login page.
3. Enter your existing credentials on your DevOps platform service page.

## Signing in with SSO <a href="#with-sso" id="with-sso"></a>

If SSO is configured for your SonarQube Cloud enterprise, sign in directly with the SSO link shared by your administrator. You do not need to create a SonarQube Cloud account through a DevOps login provider first. If you do not have the link, select **Log in with SSO** on the main login page and enter your enterprise key. See [Setting up SSO](/sonarqube-cloud/getting-started-with-enterprise/setting-up-sso.md) for additional information.

Signing in with SSO creates a separate account from your DevOps platform account. For account history, administrator permissions, and recovery access, see [Transition from DevOps-platform authentication to SSO](/sonarqube-cloud/quickstart-guides/transition-from-devops-platform-authentication-to-sso.md).

{% hint style="info" %}
In systems using SSO, a one-time email address verification is required if your administrator has not [verified your company’s email domain for SSO](/sonarqube-cloud/administering-sonarcloud/enterprise-security/sso-and-provisioning/complete-setup.md#email-domain). In that case, SonarQube Cloud provides guidance through this email verification process during your initial sign-up.
{% endhint %}

### With the SSO login link <a href="#with-the-sso-login-link" id="with-the-sso-login-link"></a>

1. Select the SSO login link sent to you by your administrator. The **Log in with SSO** page is displayed and your organization key is prefilled (the key that identifies your organization in SonarQube Cloud).
2. Bookmark the link for future logins.
3. Select **Log in**.

### From the main login page <a href="#from-the-main-login-page" id="from-the-main-login-page"></a>

1. Go to `https://sonarcloud.io/login` or `https://sonarqube.us/login`, and use the region toggle to select your region.
2. Select **Log in with SSO**. The **Log in with SSO** dialog is displayed
3. Enter your enterprise key and select the **Log in** button.

## Signing out <a href="#signing-out" id="signing-out"></a>

To sign out from SonarQube Cloud:

1. Select your account menu in the top right corner of the SonarQube Cloud interface.
2. In the menu, select **Log out**.

## Related pages

* [Choosing your server region](/sonarqube-cloud/getting-started/choosing-your-region.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-cloud/managing-your-account/signing-in.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
