Help Needed - Adding another Atlassian Cloud SSO to a separate URL

Question

I manage 2 user groups in Atlassian Cloud to enable single-sign-on to Partner A's Jira project. I need to manage 2 more groups in Atlassian Cloud that allows single-sign-on to Partner B's Jira project. And I also don't want these groups to get mixed up -- it would be bad for Partner A to see Partner B's user groups, vice versa. Please provide guidance on what to do in this instance.

Answer 1

Hello Elizabeth Guo,

Thank you for sharing the details. To achieve single sign-on for both Partner A and Partner B while keeping their groups isolated, you can follow these steps:

1.Create distinct groups for each partner in your identity provider (e.g., Microsoft Entra ID) and in Atlassian Cloud:

• PartnerA-Jira-Users
• PartnerB-Jira-Users

2.Configure SSO and SCIM provisioning through Atlassian Access:

• Map each Entra ID group to its corresponding Atlassian group.
• Assign users to the correct group in Entra so they only see their respective projects.

3.Restrict access at the Jira project level:

• Use permission schemes to ensure Partner A’s group is only added to Partner A’s project and Partner B’s group only to Partner B’s project.

This approach ensures proper isolation and prevents cross-visibility between partners. If strict separation is required (e.g., compliance), consider separate Atlassian organizations for each partner.

Reference:

https://learn.microsoft.com/en-us/entra/identity/saas-apps/atlassian-cloud-tutorial

I am reaching you on teams for further assistance.