AADSTS50020: User account ‘firstname.lastname@example.org’ from identity provider ‘live.com’ does not exist in tenant ‘SonarSource’ and cannot access the application ‘0cd6ff8b-c8a8-4ab6-8f60-516f5bc5354a’ in that tenant. The account needs to be added as an external user in the tenant first. Sign out and sign in again with a different Azure Active Directory user account.
This is currently possible to sign up on SonarCloud only with a school or work Azure Active Directory Account.
This is mentioned:
- In the documentation about VSTS integration
- In the help tooltip on the login page:
If you feel that those mentions are not clear enough, we’d be happy to get your feedback on how to make them clearer!
Just to clarify. Does this mean that I need to have VSTS setup with Azure AD accounts instead of Microsoft accounts?
Yes Rob, this is it.
Got it! Many Thanks.
I’m curious, is there a technical limitation for not allowing Microsoft Account as a login. Because I’m in the same case, for our startup, we don’t created an AAD but are still using Azure DevOps.
Same issue here, cannot use SonarCloud due to this limitation with our DevOps organization
The Identity management in the Microsoft world is really complex, and we rely on a library which does not support all sorts of identities.