Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Switching SAML Identity Providers


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.



1 answer

1 accepted

0 votes
Answer accepted
Brant Schroeder Community Leader May 30, 2019

I believe you are correct.  You can find documentation on it here Scroll to the bottom about updating.

Thanks!  Do you know if there are any potential or anticipated issues for us to look out for?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events