Switching SAML Identity Providers

[Mike Skutta]

Hello,

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.

Thanks,

Mike

[Angélica Luz]

Hello @Juergen,

Welcome to the Atlassian Community!

When this message appears, it means that the user’s account has been deactivated by the Organization administrator.

Checking the details of your site, I can see that your domain is verified, so if you are inviting a user from the same domain, you need to reach out to the Org admin for them to reactivate the account.

Note that, I’m saying for you to contact them because I already confirmed that you are not the Org admin on the organization that the domain was verified, which means that you won’t be able to manage and reactivate the account.

Since the community is public, I won’t share any private information like the site and the name of the administrator, but since they are from the same domain as you, you can check internally in your company to find who is responsible for that.

After you find the Org admin, you can share these steps for them to reactivate the account and for you to be able to invite them to your site:

• Cannot reenable a disabled account
• Enabling a deactivated account to provide site-access

Kind regards,
Angélica