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
i have a question with a probably simple answer that i could not find an answer for (apologies).
When i connect Azure AD as an identity provider to enable SSO what happens to the existing users? Will this cause sideeffects for the user or does the atlassian cloud recognizes that user email@example.com is the same user firstname.lastname@example.org that is logging in via SSO?
Right now every user has an account with a password.
Thanks in advance
Hi @Justin Auth
Aside from a change in how they access/login, not a huge amount changes.
You'll have already claimed your domain, so the users will be under your management at this point (via Atlassian Access).
Once you activate SSO and enforce it via an authentication policy, the user will need to use the SSO login method assigned to them to login into any Cloud instance they have access to. This removes the need for a separate password.
Thank you for the insights and the fast response!
So for my understanding: When we don't have atlassian access right now, the accounts are considered as "unmanaged".
When we purchase Atlassian Access, we can manage the accounts, right? Does this switch causes some sideeffects?
Thanks in advance again!
Hi @Justin Auth
Yes, at present the accounts are unmanaged - that means users are creating their "own" Atlassian account using their business email. That means you can't deactivate their account (for example), even if they leave the company.
With Atlassian Access you can claim your domain, and thus manage those accounts. There's no inherent side effect for those users, it just gives you more control over those accounts (i.e enhanced security and access control practices).
So they don't have to re-register or something similiar when i claim the domain and thus their accounts. I was thinking about side effects like users' assignee status disappearing in issues or something like that. But i'm happy to hear that there are none known, inherent side effects.
Thank you for clarification.
No the intent is for you to claim their accounts - i.e accounts under a domain which your business owns.