Setup guides will get admins up and running with some of the most popular EMM features available today, including Apples Device Enrollment Program (DEP) and Android Enterprise.
DO for Managed Google Accounts
If the Android Enterprise bind has been configured with G Suite, the admin console from Google handles all of the users Google accounts (as opposed to the Gmail configuration, where MaaS360 creates the accounts). Because of this, the afw#maas360 variable will not properly configure DO on devices. In order to get a similar workflow setup, a G Suite admin must login to admin.google.com and navigate to Security-->Manage EMM Provider for Android.
At the bottom of the section under General Settings will be a checkbox - Enforce EMM policies on Android devices. When enabled, this will enforce management anytime a user attempts to sign in to Google services with their G Suite account on an Android device.
To enroll a device in DO from this point, start from a factory restored condition. Upon activating the device, the user will input their G Suite account on the the Google Account screen. This will place the device in to DO and download the MaaS360 agent (assuming that MaaS360 is the preferred EMM. If the Google agent downloads, settings will need to be adjusted in the admin console under Device Management to disable Google management).
- If a personal gmail account is used during setup, the device will not enroll during activation
- If the device is already activated and a user enters their G Suite account, the device will enroll as Profile Owner (BYOD)