Hi @aurelien.poscia,
Problem:
In step 2 of the attributes and claims (see doc), the SAML user login attribute* refers to …/claims/emailaddress. We tried to match the configuration described in the officals docs however the SAML user login attribute cannot be set to …/claims/emailaddress (see below):
Workaround:
Instead sonarqube insists to use …/claims/name. By adjusting the attributes & Claims in our Azure Enterprise app we managed to get it to work (could be added to the sonarqube documentation to make things more transparent).
Additional info:
One more problem we’ve encoutered we’d like to sure…
Sonarqube requires a givenname and a surname in order for users to be synced via scim. Now that we manage technical users via Azure AD, we had previously created Azure AD technical users that were trying to be synced. Due to the fact that these users were created before the attribute mappings, their given names and surnames did not exist and the sync was failing.
Using expressions, we successfully synchronized older technical users, who lacked specific properties that scim required in order to be synced:
Hope this post helps others who may experience similar issues.
@Thomas_Abbe if you have more info, feel free to elaborate 
Kind regards
Kadir