We may have a use case for multiple organisations to access a particular instance of Confluence. If that's the case would is it possible to setup multiple SAML SSO configurations to each orgs Azure AD, or GSuite directories?
In addition, if required can we maintain Atlassian built-in accounts alongside these too?
It's a yes and no in the context of Atlassian Cloud.
When a user logs in into Cloud they enter their email first. Based on the domain of the email, an "organisation" is identified and that organisation's config in *THEIR* Atlassian Access will define if SAML will be attempted with whatever *THEY* have configured as the SAML provider. Effectively you are NOT in control and you do NOT configure SAML SSO to each org unless you own their domains.
Login with Google and Login with Microsoft present on Atlassian's login screen effectively shortcut this by attempting to rely on whatever session has already been established.
- Create your own custom emoji 🔥 - "Shake for Feedback" on mobile 📱 - An endless supply of GIFs via GIPHY 🤩 Is there anything quite as nice as a pleasant surprise? Comment below with what...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events