Provisioning Users in Google Apps with Directory-as-a-Service

Written by Rajat Bhargava on November 26, 2015

Share This Article

If you are an IT admin in a growing business and are leveraging Google Apps, you have the challenge of provisioning new users in Google Apps and elsewhere. If to you, ‘elsewhere’ consists of a number of devices, applications, and networks, then the challenge lies ahead. It’s not only going to be time consuming and tedious, but the risk of mistakes is huge.

Automate User Provisioning: Google Apps and Beyond

Generally, IT admins like to solve problems systemically. They like to attack the root cause and solve it for as many cases as possible. Merely manually provisioning Google Apps or even leveraging a system that may automate the provisioning of Google Apps without solving user management for other IT resources isn’t a realistic solution.

Ideally, an IT admin would enter a new user in their system once and be able to provision them to virtually all of the IT resources that they will need.  Those resources could include their device, any servers they may need to access, applications, and the WiFi network among other potential options. Why is that important? It’s important because it’s a repeatable process that ensures users will have the proper levels of access. It ensures that systems don’t get missed and that the same credentials can be used in all necessary locations.

One Central System: Directory-as-a-Service

There is a system that handles provisioning in Google Apps and other IT resources. It’s called Directory-as-a-Service, and delivered as a SaaS-based service that can provision, deprovision, and modify user access to Google Apps, devices, WiFi networks, and other applications. It serves as a cloud-based directory service which has two advantages. IT admins have one central system to leverage in order to systematically provide or terminate access, and users have one set of credentials to access all of their systems, applications, and Google Apps.

How It Works

The cloud-based directory is integrated with Google Apps through APIs. When a user is provisioned in DaaS, an API call is made to Google Apps to create the user and their password.  Once that occurs, the user and the password they entered is set. If a user needs to be terminated, a similar API call can be made to delete the user. That same user can be provisioned on devices, applications, and onto the WiFi network as is deemed appropriate.

If you would like to learn more about how you can centrally provision users in Google Apps along with your other IT resources, check out Directory-as-a-Service. Or feel free to give JumpCloud a try. Your first 10 users are free.

Continue Learning with our Newsletter