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
Our organization is changing identity providers. Our current and future identity providers are both Microsoft Azure. We are essentially moving to a new tenant. As part of this move, our domain(s) are also moving to the new identity provider (tenant).
I was wondering if there are any anticipated issues with updating the SAML single sign-on from our old identity provider configuration to the new? Caching issues, delays, etc.? The user names will be the same in the new identity provider. It appears that simply updating the SAML single sign-on config in Atlassian Cloud should just work. We just want the transition to go as smooth as possible. From what I have read, it sounds like the instant the "save" button is clicked, the new SAML single sign-on configuration takes effect.