One of the most popular web applications on the planet right now is the productivity platform G Suite. Formerly called Google Apps, G Suite was introduced as a challenge to the Microsoft® Office productivity suite and quickly started giving Microsoft a run for its money in the corporate productivity space. The user count on G Suite is growing, and as more IT resources move to the cloud and non-Windows platforms, being able to control G Suite identities with JumpCloud Directory-as-a-Service® (DaaS) is an interesting proposition.
G Suite Challenges Microsoft Office
Google introduced their productivity platform as a way to shift core applications to the cloud. Their Gmail platform, along with productivity applications such as Google Docs, Sheets, and Slides, were built to compete with Microsoft solutions, and that’s exactly what they did. By focusing on shifting core platforms like Microsoft Exchange, Office, Windows file server, and more to the cloud, Google made a serious dent in Microsoft’s ownership of the enterprise. Millions of organizations decided to make the jump to the cloud and Google Apps, proving the strategy was hugely successful.
However, this new setup also created a challenge for IT organizations who were trying to move to the cloud. While they could eliminate their Exchange servers, they couldn’t eliminate Microsoft Active Directory®. Admins quickly discovered that Google’s G Suite Directory wasn’t a replacement for AD, but rather a user management system for Google apps and a few select web applications. So, IT organizations moved part of their back-office infrastructure to the cloud, but still were forced to keep part on-prem as well. Obviously, that wasn’t the ideal approach for IT organizations looking to shift to the cloud.
If that wasn’t enough, many organizations that were leveraging G Suite were also using AWS for their cloud server infrastructure and shifting to Mac and Linux desktops and laptops. These non-Windows platforms and cloud servers put even more pressure on IT organizations due to the fact that Active Directory wouldn’t easily connect to those resources. Some third party solutions were created that helped connect AD to some of these specific (Read more...)
*** This is a Security Bloggers Network syndicated blog from JumpCloud authored by Jon Griffin. Read the original post at: https://jumpcloud.com/blog/control-g-suite-identities-directory-service/