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
We're getting ready to move to SAML SSO using Azure. Everything seems straightforward, but we'd like to tell our users what to expect. For example, when we moved Slack to SSO, users saw a button saying (something like) "Login using your [company name] account".
What will users see when they try to access Confluence/Jira for the first time after we change to SSO? Will they have to enter their account password once? Every time they login? Never? Any experience you've got to share would be appreciated.
Once you enable SAML SSO, your users will automatically be opted into logging in with SSO. From this point on, your users will enter their email address on the blue Atlassian login screen, hit the NEXT button, and automatically be redirected to your identity provider where they'll have to enter their credentials to authenticate via Azure.
This will be the same experience every time they login.
Let me know if you have any other questions!
Hello! Thank you for the answer, that's great :-)
We've discussed this in-house and we believe that for domain-joined devices our users will only have to log in once. This is based on our experience with Azure > SAML SSO for other SAAS products, where users with domain-joined devices are always seamlessly "logged through" (after the first login), and users without domain-joined devices have to log in every time they start a new session.
Does this tally with Atlassian's Azure SSO experience?