Atlassian Access and multiple Directories

[Colin Goudie]

We have 2 'sister' companies, 1 on G-Suite and 1 on Office365/Azure AD

We (G-Suite company :) ) use Atlassian and starting to expand it's use. Ideally we will start with Confluence cloud so my first though was provision Atlassian Access to see if it could authenticate both sets of users against G-Suite and AzureAD.

But it appears you can only have 1 SAML Directory on Atlassian Access or have I missed something?

[Ed Letifov _TechTime - New Zealand_]

Colin, are the two companies using the same email domain?

SAML configuration in Atlassian Access is tied to an "organisation", that claims ownership over domains. During login the user is asked to enter their email, the domain of the email is checked against all domains claimed by organisations (across the whole Atlassian Cloud), the organisation is found and then that organisation's SSO is used (if configured).

The "organisation" is technically a logical/virtual record that is only tied to the real company by the domains it is linked to.

If your two sister companies are using different domains you should be able to create two organisations, claim these different domains in their respective organisations, and configure different SSO providers.

[Colin Goudie]

No they are not.

At some point they may, but looking for the quickest wins.

Thinking I might provision Gsuite from 365 or visa versa ?

[Ed Letifov _TechTime - New Zealand_]

SAML configuration in Atlassian Access is tied to an "organisation", that claims ownership over domains. During login the user is asked to enter their email, the domain of the email is checked against all domains claimed by organisations (across the whole Atlassian Cloud), the organisation is found and then that organisation's SSO is used (if configured).

The "organisation" is technically a logical/virtual record that is only tied to the real company by the domains it is linked to.

If your two sister companies are using different domains you should be able to create two organisations, claim these different domains in their respective organisations, and configure different SSO providers.