Ideally, we should be having a single system that manages user identity, authentication and authorization. I should be able to create a user in a single place and they get access to all of these in the right way and when they leave, lock out access from a single place.
I am wondering what do you folks use to create and manage the initial setup so that it is done right.
Do you mind sharing why you have accounts on all three? We do something similar because our product, https://iko.ai, enables people to train, track, package, deploy, and monitor machine learning models, run real-time collaborative notebooks and long-running background notebooks on their own Kubernetes clusters and their own data buckets; therefore we have to support GCP's GKE, Azure's AKS, AWS' EKS, DigitalOcean Kubernetes, etc.
I wonder if you're doing "something something multi-cloud/cloud agnostic" as well. If not, why have all three as opposed to leverage just one cloud.
Then most systems can be set up to federate with external systems. Aws for example can allow identity federation via saml iirc, azure probably has something active-directory-native.
Dunno for gsuite or other systems... but there probably is.