Hi Alex, is there a chance we could get some follow-up on this? I manage the G Suite account at my company, and the idea that an irresponsible or disgruntled employee could take down our whole account is very worrying. (Especially since our G Suite accounts are tied to our GCP account.)
Assuming the story isn't simply made up, I'd rest easier knowing whatever caused the problem (both the initial mass banning and Google's unwillingness to help) has been fixed.
We're limited on what we're able to share in public forums related to specific customer situations.
If you're not already doing the following we recommend the following steps to protect your G Suite account
- have more than one super admin
- ensure an up-to-date recovery email is in the account profile
- ensure an up-to-date recovery phone is in the account profile
- ensure account profile is properly updated
- use two factor authentication for all users (ideally user security keys)
- at a minimum, ensure that your G Suite administrator users are using two factor authentication
If the story in the OP is true, none of those steps would have mattered, because the entire organization was banned. Protecting admin accounts is very doable, preventing all your employees from ever doing anything bad with their accounts is impossible.
I realize you can't comment on specific incidents, but a simple statement from Google saying "no, we definitely won't ban entire organizations including connected personal accounts because of one user's actions" would go a long way to put people at ease here.
To be honest, your team should make addressing this story in public a priority because it has given you a lot of negative attention. There are hundreds of comments spread out between this HNews post, the sysadmin cross-post, and the tifu post. I'd be really curious to know if the entire story was made up altogether or if there was any missing info that was pertinent to what happened and why.
Assuming the story isn't simply made up, I'd rest easier knowing whatever caused the problem (both the initial mass banning and Google's unwillingness to help) has been fixed.