Forum Discussion
NikolayI
Apr 12, 2022Brass Contributor
Outlook - cannot add Google G Suite account - javascript disabled?
I am trying to add Google G Suite account to Outlook. When I enter the G Suite account email it shows the Google login screen. Then I get a question by Google to choose "Organizational G Suite a...
zuary
Sep 13, 2022Copper Contributor
I found a simple fix and it worked 3 times already:
The problem is that when you upgrade from G-Suite Legacy to Google's Workspace Business google builds another totally different account with the same name, that is your_name@your_domain.
Now you have 2 accounts with the same email address, one is Individual (the old legacy one), the other is your new business account. This situation causes outlook to fail when trying to install the email account in outlook, or even to fix or change the password to the old outlook account that worked fine until now.
The solution is to get rid of the Google's individual account, or change its email address.
How to do that:
When you try to sign in to chrome with that email address you get 2 choices: Individual, or Business?
Choose the Individual. You can't login to it since you don't have it's password, don't try, instead click on "forgot password". Follow the conversation there, when asked, put an old password (the one you had prior to the upgrade for example), you will get a security code to your mail, which is alright because you can enter your new email account in gmail.com , not needing outlook for it, you should now see that google changed the account to a temporary name like
email address removed for privacy reasons .
You should be able now access this temporary mail in gmail.com, when you first sign in you are asked to choose a permanent name for it, choose something and you are now set with the Individual account renamed. Now you may proceed to install/fix your account in outlook.
(The renamed individual account holds some data and permissions to some google apps that you registered to while it was a legacy account, most of your data, like emails, photos, calendar, drive, where transferred to your new business account, therefore what is left of your old legacy account is probably negligible)
The problem is that when you upgrade from G-Suite Legacy to Google's Workspace Business google builds another totally different account with the same name, that is your_name@your_domain.
Now you have 2 accounts with the same email address, one is Individual (the old legacy one), the other is your new business account. This situation causes outlook to fail when trying to install the email account in outlook, or even to fix or change the password to the old outlook account that worked fine until now.
The solution is to get rid of the Google's individual account, or change its email address.
How to do that:
When you try to sign in to chrome with that email address you get 2 choices: Individual, or Business?
Choose the Individual. You can't login to it since you don't have it's password, don't try, instead click on "forgot password". Follow the conversation there, when asked, put an old password (the one you had prior to the upgrade for example), you will get a security code to your mail, which is alright because you can enter your new email account in gmail.com , not needing outlook for it, you should now see that google changed the account to a temporary name like
email address removed for privacy reasons .
You should be able now access this temporary mail in gmail.com, when you first sign in you are asked to choose a permanent name for it, choose something and you are now set with the Individual account renamed. Now you may proceed to install/fix your account in outlook.
(The renamed individual account holds some data and permissions to some google apps that you registered to while it was a legacy account, most of your data, like emails, photos, calendar, drive, where transferred to your new business account, therefore what is left of your old legacy account is probably negligible)
- BlessedMomSep 13, 2022Copper ContributorThank you for this information. The registry fix worked though. While I did not need this fix, I am copy pasting to my notes in case it arises another time and the registry fix doesn't work. Thank you!