By Ryan Squires Posted October 6, 2018
Many organizations that leverage G Suite™ consider using G Suite Directory as their core user store. It makes sense on some level. If your users spend a lot of time using G Suite applications, then it stands to reason that they should utilize the username and password combination they use frequently. But, the challenge quickly escalates and becomes a problem of how to leverage G Suite identities for more than just Google Cloud Platform components. This is a core reason as to why IT organizations use JumpCloud® Directory-as-a-Service® over G Suite Directory.
G Suite’s Aim and Limitations
Google didn’t build G Suite (formerly known as Google Apps) as a replacement for Microsoft® Active Directory®, which is widely regarded as the on-prem directory services market share leader. No, Google’s focus is on replacing Exchange, Office™, Windows® File Server, and other Microsoft productivity components while putting their own spin on the product landscape by introducing collaborative features that Microsoft did not incorporate previously.
As millions of organizations started to adopt G Suite, they quickly realized that while they could shift their productivity platform to the cloud. IT management infrastructure, namely their identity management components, would need to remain on-prem however. And, it is fair to say that G Suite Directory does include some facets of user management. But, it does not provide the same level of user management that Active Directory does in enabling access to systems, file servers, and cloud infrastructure outside of Google’s purview.
Past, Present, and Future of Directory Solutions
For organizations shifting to the cloud, having AD on prem while already shifting their productivity platform to the cloud makes little sense. It’s like having one foot in the past and another in the future, with no clear path forward for the present. So, IT organizations started searching for a cloud directory service. While G Suite Directory exists, it is a user management platform for Google Cloud Platform™ (GCP) and a web application SSO solution for select web apps. This means IT organizations are unable to manage their Windows®, Mac®, and Linux® systems, their on-prem LDAP applications like OpenVPN® and MySQL™, NAS devices and Samba file servers, AWS® cloud infrastructure, WiFi and wired connections via RADIUS, and much more. A true directory service is needed, which is why IT admins started to integrate G Suite identities with JumpCloud to create a complete cloud infrastructure, so that all these resources can be accessed from the G Suite cloud identity.
So, with JumpCloud, IT admins can provision new G Suite accounts directly from the JumpCloud console and federate the associated credentials to any of the IT resources an employee may need as listed above. This is all possible with True Single Sign-On™, a concept inherent to Directory-as-a-Service that allows users access to all the IT resources they need, not just a few Google cloud-based ones. JumpCloud Directory-as-a-Service is often the right solution for cloud forward leaning organizations.
Learn More About JumpCloud
If you’re ready to learn more about JumpCloud, please do not hesitate to drop us a line. If you’re ready to jump in, sign up for a free account that allows you to manage 10 users free, forever. It’s a great way to explore JumpCloud’s functionality and examine why you should use JumpCloud over G Suite Directory.