In some instances, users of an Azure AD organization may see the following errors when attempting to log into CodeScene:
1. Automatic connection to Azure DevOps could not be established
This can occur when a user has left and rejoined your organization, resulting in a break in the Azure mapping. The issue resides in Azure, but our recommendation is a workaround of manually finishing the authentication as described in the steps provided in the following screenshot:
2. Registration Error: Azure DevOps Organization Required
This can happen in cases where you didn't have the necessary permissions to access or join an organization, you didn't get an invite from your administrator to join, or the Azure DevOps organization you were part of has been deleted or no longer exists.
To resolve the issue, please follow the steps provided in the following screenshot:
3. The other possible errors:
You may encounter that your login identity is not handled correctly.
In Azure Cloud, there are different services:
- Azure Portal
- Azure DevOps
- Azure DevOps tokens
Each of them handles your login identity separately. This can sometimes cause issues with synchronization, meaning that at a given time, these services might show three different identities for you.
The issue is when you log in to any of these services (Azure Portal or Azure DevOps), they don't always communicate with each other quickly. You might end up with different identities in each service, even though you're the same person.
A possible solution might be to do a clean-up, by removing any extra organizations created for the login.