You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have a strange setup when it comes to email and cloud authentication and this is currently causing me some problems with Crowd. Currently I use Azure AD to provision my accounts, add to groups etc and sync to crowd. My actual email is handled by Google Apps with is automatically provisioned by AzureAD when a new user is created.
This therefore means that Azure AD has no email attribute for any user (although their AzureAD UPN does match their primary email in Google Apps) and this therefore means that Crowd does not have any knowledge of the user's email.
Is there any way now to tell crowd to use the UPN as the users email rather than pull the default email attribute from Azure AD? Currently users can't receive any email as their profiles have no values assigned.
Hi @Ajay Furber
As per Atlassian's documentation, Crowd's email attribute is mapped with Azure AD 'mail' attribute. The problem is that only Azure AD users with an Exchange Online mailbox have a 'mail' attribute.
You might want to take a look at the ODCC add-on which allows to use Azure AD 'mailNickname' attribute (which is always provisioned) concatenated to the '@' character plus the value of your domain name.
(Disclaimer: I work for the vendor of the ODCC add-on)