You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Jira and AD have been connected, and AD user provisioning groups have been created. that AD groups were added as default groups for product access. Therefore, if we add any user to AD, that user will gain access to Jira and Confluence. However, they do not receive the SSO feature. I noticed the authentication policy, however we must manually add users to it. I don't want to carry things out by hand. Once a user is added to an AD group, SSO and jira access are automatically granted to them. Would you kindly consider my request?
Hi Charan, I encourage you to look through the following Atlassian documentation as it should help guide you in configuring SSO.
In my own organization I have SSO and user provisioning configured between Atlassian and Azure AD. The authentication policy configured to use SSO is set as the default policy, so users are added to it automatically. Users are added to AAD groups, and the group members are provisioned in Atlassian and are able to login to Atlassian using their Microsoft 365 credentials.
Hi Connor thank you for you information.. we use Azure an Atlassian Access like you, but my question is : I know we can provide any groups from Azure, but Is possible for example to define in Atlassian Access the group X for Jira licences users and group Y for Confluence users? ... in our case we have 1400 licences in jira and 800 in confluene
Hi gustavo, what you're describing is possible, in fact I have it setup like that in my org. I have user provisioning setup between Atlassian and Azure AD. In AAD I have created 2 security groups, JiraUsers and ConfluenceUsers, which are synced to Atlassian via user provisioning. In Atlassian, Jira product access is assigned to the JiraUsers group, and Confluence product access is assigned to the ConfluenceUsers group. All my employees are members of ConfluenceUsers so they're licensed for Confluence, but only specific employees are licensed for Jira through membership in the JiraUsers group.