I’m pleased to announce the general availability (GA) of Android Zero-touch Enrollment in JumpCloud! We are continuing to deepen the capabilities of JumpCloud’s Android EMM by expanding on the foundation that was delivered over the last several quarters. With this release, we now support Android Zero-touch Enrollment, along with other enrollment enhancements and expansions of our Android device policies.
IT administrators can now preconfigure company-owned devices purchased from authorized resellers and when the devices first turn on, they are automatically forced into the settings defined by the IT administrators. This reduces the effort on IT to manually provision each device.
IT admins can interact with the integrated zero-touch iframe to configure basic information and also make further configuration changes in the zero-touch enrollment portal.
To support the zero-touch enrollment process, we also enhanced our enrollment token creation process. The updated process allows for customization of the enrollment token values as well as the generation of DPC extras required for zero-touch enrollment. DPC extras allow for the pre-configuration of various native and EMM-based variables. Finally, we’ve continued to enhance our existing Android device policies and deliver new ones (ex. Proxy Settings).
JumpCloud Android EMM covers all major uses supported by Google’s Android Management API which enables our customers to consolidate all their endpoint management solutions (both desktops and mobility) in order to reduce time, costs, and resources. It also offers a unified and streamlined Device, Identity, and Access management experience for IT Admins and MSPs that increases visibility, security and control to their COD and supported user BYOD devices.
Enrollment Token Configuration: IT administrators can now curate the contents of the enrollment token used for enrollment via QR code or via DPC identifier method (afw#setup), as well as the DPC extras for zero-touch enrollment configuration. Settings like token usage (single or multi-use), configuration of the token duration (either the 1 hour default or a custom value up to approximately 10,000 years), and even WiFi can be configured for the enrollment token. To make manual company-owned device enrollments easier, IT administrators can specify the SSID and password of a WiFi network that will be used at the time of enrollment. Finally, IT admins have visibility into all active enrollment tokens and if necessary, they can invalidate/delete them individually or in bulk.
Enhanced Policy Management: Addition of advanced features are available across each solution set (work profile, fully managed device, and dedicated device). Application-based Restrictions, Device Restrictions, and WiFi Configuration policies all get expanded settings. We also introduce a new Proxy Settings policy enabling IT admins to configure either a direct or PAC script HTTP proxy on the Android devices.
Reduction of security risks: Limit or eliminate the potential security risks for BYOD to work. Ensure that corporate apps, data, and management policies are restricted to the work profile so that the device is fully secure to be used for work purposes. JumpCloud provides admins with the option to deploy custom JSON payloads for any setting as well as pre-built policies for passcodes and more.
Increased productivity and lower user friction: Provide satisfaction for end users as they get to use the device of their choice. JumpCloud’s Android EMM enhances mobile work productivity by making it possible to use the devices that they are familiar with.