migrate from Google Workspace to Microsoft Outlook.

[Nagarjuna Reddy]

Hi 

Our organisation  has migrated from Google Workspace to Microsoft Outlook.
Our primary Atlassian admin account (ganesh.shirole@accionlabs.com) was created using
“Continue with Google” authentication.

The Google account no longer exists and we do not have access to that mailbox.
Atlassian still forces Google sign-in, so we are completely locked out of the admin account.

We urgently need:
1. Removal of Google SSO dependency for the admin account
2. Conversion of the account to password-based login
3. Update the admin email from ganesh.shirole@accionlabs.com to our new Outlook email domain
4. Restoration of access to the workspace and Bitbucket repositories

Please help us regain access to our Atlassian organisation and Bitbucket workspace.

[Alexander Nilsson]

Hi Nagarjuna,

when an Atlassian admin account was originally created via “Continue with Google” and that Google account no longer exists, regaining access and removing the Google SSO dependency involves several key steps:

1. Contact Atlassian Support immediately: Since you are locked out of your primary admin account with no Google access, only Atlassian Support can verify domain ownership and help re-establish admin access. You can start here: Atlassian Support Contact.
2. Verification of Domain Ownership: Atlassian will likely ask you to verify ownership of the organization’s domain (e.g., accionlabs.com) using DNS records or other proofs to confirm legitimate access rights.
3. Disable Google SSO / Switch Authentication: Once verified, Atlassian Support can help disable Google SSO for the affected admin account and convert it to a password-based Atlassian login, effectively removing the dependency on the now-defunct Google account.
4. Update Admin Email Address: During this process, the support team can assist in changing the admin’s primary email to the new Outlook domain email, thus aligning with your updated identity provider.
5. Regain Workspace and Bitbucket Access: After the above steps, you will regain admin access to your Atlassian organization, including Bitbucket repositories and other product access, enabling normal management going forward.

Additional Recommendations:

• Set up an alternate recovery admin account (with password-based login) post-recovery to avoid lockouts from third-party SSO providers in the future. See: Manage admins in Atlassian.

Unfortunately, there is no self-service method for this scenario, as it involves identity provider changes and admin access restoration. Immediate communication with Atlassian Support, providing proof of ownership and identity, is essential.

Hope that helps.

Many greetings,
Alex