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.
Did you know Atlassian Access offers more than SAML single sign-on for Atlassian cloud products, like Jira and Confluence? Whether you're just starting to plan for your organization or in the pr...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events