It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Migrating from G Suite to other Identity Providers (Okta, Azure AD, OneLogin etc)

Just want to share my experience here if you have G Suite integration with your Atlassian Cloud site and you are planning to migrate to a different Identity Provider (Okta, Azure AD, OneLogin etc) to apply Atlassian Access features.

Before you start

Before migrating, make sure you have subscribed for Atlassian Access and understand the features and pricing.

How to migrate

Disable G Suite Integration 

  • Go to your site's Administration at admin.atlassian.com:
    • If you're an admin for one site, you'll land on the Users page of your site.
    • If you're an admin for multiple sites or an organization admin, click a site's name and URL to open the Administration for that site.
  • Select G Suite in the sidebar.
  • Select Disconnect account and follow the prompts. 

When you disconnect your G Suite integration:

  • Your users will still be able to log in to your site's products with their Google credentials. However, their details won't be synced.
  • If your domain hasn't been claimed by an Atlassian organization, then users with accounts from that domain will no longer be managed and will be able to edit their account details.

Disconnect account option is greyed out while the sync is in progress. If the sync is taking very long time, admin can terminate the sync by revoking GSync’s refresh token in Google.

  • G Suite Admin can go to https://myaccount.google.com/permissions
  • Select Atlassian Cloud from Third-party apps with account access page and click on 'Remove access'
  • This will fail the sync in Atlassian side.

Verify Domain(s) in Atlassian Organisation

The domains verified as part of G Suite integration, will be removed automatically from the Atlassian Organisation when the G Suite integration is disabled. 

Make sure you verify the domains in your Atlassian Organisation in order to apply Atlassian Access feature.

DNS TXT method may take up to 72 hours for the new TXT record to propagate across internet depending on your DNS host.

This may delay the migration if you are planning to do everything on the same day. The workaround is to create a new Atlassian Organisation and subscribe for Atlassian Access in it, and verify the domains before the migration day. Once migrated, you may transfer Products from old organisation to new organisation

Once the domain is verified, Claim accounts with in your domain. When you claim accounts, users with the domain receive an email telling them about the change and what it means to have a managed account. We recommend you notify users that they'll receive this email and who to contact to modify their account.

Apply Atlassian Access features

Now, it's time to Apply Atlassian Access features.

 

0 comments

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Continuous Delivery

Our Atlassian Partners continue to support their customers during coronavirus pandemic

Across the world, governments and healthcare authorities are demonstrating the power of collaboration to find solutions to the COVID-19 pandemic, to protect our communities, and to get things back to...

669 views 0 11
Read article

Community Events

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

Events near you