Hi Shannon,
Welcome to the Atlassian Community!
First, let's check if the identity provider you're using is officially supported. Please see the list of supported providers in the link below. Besides the ones there, GSuite is also an alternative, but the process to log in with Google is somewhat different than what is explained in here:
https://confluence.atlassian.com/cloud/saml-single-sign-on-943953302.html
SSO can also work with identity providers that are not officially supported, but some more manual configuration work is needed.
SSO works with claimed domains. Once you claim a domain , all users with email addresses @that domain will be forced to use SSO. It is best practice to have a secondary (temporary) site admin in your Cloud site whose email address is not @that domain while performing the integration and until everything turns out fine.
Furthermore, no user is deleted from your site. Eventually, if you enable user provisioning, some users might be added, depending on the groups that you sync with Atlassian Cloud and the default product access that you have configured.
Besides that, keep in mind that in order to enable SSO, you will need a separate subscription to Atlassian Access. This subscription provides you various functionalities (like SSO, enforcing 2FA and password policies for all users etc) but also gives you elevated support levels from Atlassian.
However, if (somehow) something goes wrong during the implementation of SSO on your cloud site, please open a support ticket with us and provide as many details as possible regarding the issue and the last operations that you performed and might have caused it, and we'll figure things out together.
Claudiu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.