The adoption of JumpCloud’s Office 365™ and G Suite™ (formerly Google Apps) user provisioning and synchronization capabilities has grown exponentially since their releases. JumpCloud’s DaaS efficiently provides Office 365 and G Suite with a backing, authoritative, and cloud-based directory – a directory that can unify their identities between the services and other resources an employee requires.
Now we have added new and improved methods to manage the connections between JumpCloud and these widely-depended upon business platforms, which this blog post will walk you through, along with other new productivity updates.
Office 365 and G Suite Provisioning Control via User Details
To improve on-boarding efficiencies connecting an employee identity to Office 365 and G Suite, we have updated a User’s Details to demonstrate and provide the administrator better control directly within this user interface. This update ensures a JumpCloud administrator can stay ‘within context’ while working on a user account, staying in one user interface to assign them resources such as access to servers and workstations (e.g. ‘System Bindings’ tab) and now Office 365 and G Suite (through the ‘Directories’ tab).
Within this new UI, selecting either the G Suite or Office 365 options will provide a fairly quick visual heads up for the admin to determine that their user is bound to these services. Further, the selecting/un-selecting capabilities in this UI will provide the exact functionality that the Office 365 Provisioning Group or G Suite Provisioning Group provide. For example, selecting the desired service will bind the user to it or – if needed – it will provision a new identity to the service if currently non-existent within the service. Un-selecting the service will effectively stop access to the service (‘blocked’ account in Office 365 or ‘suspended’ account in Google).
In this example, the UI indicates to the administrator that the employee is bound to and currently ‘synced’ successfully with the Office 365 service.
If the connection for any reason is interrupted or the sync to the service is unsuccessful, the administrator will be made visually aware of these conditions and caused through hover-over tool tips as demonstrated here:
* Note that sync/error message handling is limited to Office 365 in this release. G Suite will be addressed in a follow up release.
Re-authorize connections to Office 365 and G Suite
JumpCloud now offers the ability to re-authorize a connection between Office 365 or G Suite without the need to de-authorize or otherwise disconnect from the service. The user interface has been modified to accommodate these new features, resulting in some re-positioning as well. Specifically:
a. Re-authorize Connection Button: This new feature enables an administrator to refresh tokens of privileged user accounts who are maintaining the persisted connection between JumpCloud and the service through OAuth 2.0. This will also help to resolve connection issues and will not result in the ‘un-selection’ of any currently bound JumpCloud users.
b. Deactivate Service Button: This has been re-positioned in the UI and is a feature only utilized when the administrator has cause or need to disconnect the services. This will result in un-selecting users in the services Provisioning tag, yet not affect their access on the service side.
Serial number collection from Windows, Mac OS X and Linux hosts
New for this release is the ability for JumpCloud to collect the serial number information directly from a Windows, Linux or Mac OS X host. This is important for administrators who are interested in leveraging JumpCloud for light-duty asset management tasks for resources like laptops and workstations. This can be found in the system’s details, as seen below: