External identities

[Furkan]

Hello Everyone,

We have our Azure AD connected to our Atlassian so that everyone can log in using SSO. However, I’m facing an issue that I’ve been trying to resolve on my own for hours.

Since we’re part of a large organization, our Azure AD includes multiple domains. Instead of using UPN (User Principal Name), we’ve configured it to use email addresses because all UPNs are the same across domains. This setup works correctly for users with our company’s email domain; they’re added to the necessary groups and managed by our identity provider. However, users from other domains are not managed by our identity provider, even when they’re assigned to synced groups from Azure AD.

I’m at a complete loss. Any suggestions would be greatly appreciated.

[Dave Rosenlund _Trundl_]

I imagine this is going to depend (a lot) on your specific set-up, @Furkan 

I requested assistance from Atlassian on this one. They will likely create a ticket on your behalf and include a link to it here in this thread.

Good luck,

-dave

[Andy Heinzer]

Hi @Furkan I created a support case on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/48/PCS-346004

[Susan Waldrip]

Hi @Furkan , we're going through the same thing for my site. The IT System Admin is working with the other organization's IT Sys Admins for their Azure AD to try to enable access for the other org to use SSO, and they're both working with our Windows Enterprise team to figure out the Azure part of it. The Sys Admin has also reached out to Atlassian but I don't think what they suggested has worked yet (and that may well be our setup, not Atlassian's fault). You might try contacting the equivalent in your company and see if collectively they can work it or at least put them in contact with Atlassian, as @Dave Rosenlund _Trundl_ suggested. If I find out more, I'll post it here.