Atlassian Access Licensing for JSM customers

[George Matrozos]

Hi, in this article, there is a description on how to provision internal customers of a JSM service desk. https://confluence.atlassian.com/cloudkb/configure-atlassian-access-saml-single-sign-on-and-user-provisioning-for-customer-accounts-in-jira-service-management-1038778740.html

My question is that we have a JSM with 10 agents and 10 Atlassian access licenses for SSO and user provisioning (Azure AD). Customers belong to the same verified domain. Is there a need for licensing those customers with Atlassian Access? Will these customers have SSO if I dont license them with Access?

[Jack Brickey]

Hi @Talha Farooq , No that would not be possible. There needs to be a 1:1 relationship between Atlassian instance and domain. Might I inquire as to why you need three instances instead of one? Please note @email1, @email2, @email3 represent separate domains.

[Talha Farooq]

Hi @Jack Brickey what is not possible? Just a use case I have in my mind. In case we go with three instances, we will have 3 separate domains? Can I then claim these domains from one of the instances and implement SSO?

[Dirk Ronsmans]

@Jack Brickey ,

Isn't Atlassian Access available for a specific organisation which can then hold multiple instances?

True a instance has it's own domain ( abc.atlassian.net, def.atlassian.net, ... ) but is it not so that the IdP used with Atlassian Access can be used for all instances under the same organisation?

[Jack Brickey]

@Dirk Ronsmans , Yes that is my understanding though I have not used Access myself. @Talha Farooq , something to consider and investigate.

[Nic Brough -Adaptavist-]

Yes, that's correct.  Adaptavist uses Okta + Access for all of our Cloud Atlassian sites (and we've got a lot - we spin them up for dev/test, but also for handling projects with clients)