Hi Team,
We are facing an issue that a user who had
-
I have SonarQube integrated with Microsoft Entra ID (Azure AD) using SCIM provisioning. I’m experiencing an issue where a user cannot access SonarQube after their email address (UserPrincipalName) was changed in Azure AD.
Environment:
-
SonarQube version: [v2025.6]
-
Authentication: SAML + SCIM with Azure AD
-
SCIM attribute mappings:
- SAML user login attribute* http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress
- SAML user name attribute* http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname
Problem:
-
User had access to SonarQube with email:
olduser@domain.com -
UserPrincipalName was changed in Azure AD to:
newuser@domain.com -
User was removed from the Azure AD access package and re-added
-
When reprovisioned, Azure AD sends the old email address (
olduser@domain.com) instead of the new one -
The user cannot authenticate with their new email
What I’ve tried:
-
Removing and re-adding the user to the access package in Azure AD
-
Forcing provisioning sync in Azure AD
-
Attempting to deactivate the user in SonarQube UI (no deactivate option appears for SCIM-managed users)
-
Verifying the attribute mappings are correct
-
Any suggestions on how to solve the problem?