Starting July 7th, Email verification will be required for all users logging in to SonarQube Cloud through Azure DevOps.
This one time only step adds a layer of security to help protect our service and user accounts.
How does it work?
The next time you log in through Azure DevOps starting July 7th, a verification modal will appear on SonarQube Cloud, prompting you to enter the code sent to your email address.
Once the correct code is entered, youāll proceed to access the product as usual ā no impact on your experience beyond this one-time check.
Please reach out to us if you experience any issue
In our organization, we use Azure DevOps accounts for logging into SonarQube Cloud. However, we have a number of contractors who are provided with Azure DevOps accounts but do not have email inboxes or licenses associated with those accounts. As a result, they will not be able to receive the email verification code required by the new process.
Is there a recommended or viable solution for users in this situation? For example, is it possible to configure an alternative verification method, or can we associate a different email address for these accounts? Any guidance or workaround you can provide would be greatly appreciated, as this change will impact our contractorsā ability to access SonarQube Cloud.
This also introduced problems for us.
We have accounts used for Azure DevOps as well which is not associated/linked to a physical email account and for this reason not getting notifications. Luckily were able to register and add another account to continue working, with multiple other accounts still being impacted resulting in new registrations and adding individuals to our organization.
Iām sorry to hear this has created friction for you. We introduced email verification as a security measure to protect our customersā accounts.
For your contractors, I see two potential options:
If possible, you can override their email addresses in Entra ID with emails they can access.
Temporarily assign them a license to provision a mailbox so they can receive the verification code. Once verified, you can remove the license if itās no longer needed.
Please let me know if one of these approaches helped you unblock your teams.
Iām having a similar issue. I only have 1 account for use with a government project, and it cannot receive emails from external addresses. The email is linked to a valid Entra account, without inbox access itās no longer possible to log into Sonar Cloud. I cannot adjust my billing either without account access.
There must be another option for two factor authentication than forcing inbox access. If not, at least consider dropping the restriction for affected users or providing responsive customer support. As it stands, anyone affected is effectively locked out.
Iām agree with some other user, there must be another option for 2MFA, our users donĀæt have access to inbox access in their accounts, in my case only the admin account has a inbox access , but anyway the mail with confirmation code isnāt work , this mail has never was received. Your āfeatureā is affecting many teams in many companies.
I understand the frustration this has caused, and Iām sorry youāre experiencing such disruption. To clarify, this verification step is not multi-factor authentication (MFA), and it wonāt challenge users at every login. Itās a one-time email verification implemented to address a security concern.
That said, I recognize it is blocking some of your users from accessing SQC. Please send me a direct message here in the community with the email addresses or domains affected that have no possible workaround. I will escalate this with our security team to find a solution to unblock your users.
This measure was introduced to protect your accounts, not to prevent access. From what I see, the majority of users have been able to verify their email successfully, but I want to ensure we resolve the issue for your teams as well.
Please enter the 6-digit verification code that was sent to ****@.onmicrosoft.com.
The problem here is that for the registered account we will not receive any emails as this tenancy is only for the development (not configured to receive emails). We need to find out how to add alternate email addresses at the sonar cloud to avoid this in future.
But now we are completely blocked to continue our development, so we want quick support to unblock the login issue. could someone please help us asap.
We are in the same boat as everyone else and suddenly today all our 3rd party developers lost access to sonarcloud enterprise. So how can we move forward?
Starting July 7th, Email verification will be required for all users logging in to SonarQube Cloud through Azure DevOps.
How does it work?
