Additional Android Enterprise enrollment attributes

Administrators can add custom enrollment attributes when creating an Android Enterprise enrollment configuration. These attributes are pushed to the device through an enrollment configuration (JSON) file during enrollment.

You can add up to 10 custom enrollment attributes when creating Zero-touch, Knox Mobile Enrollment, or QR code enrollment configurations in the MaaS360 Portal.
Additional enrollment attributes

The MaaS360® for Android app reads these parameters as a part of the Device Owner enrollment and issues corresponding actions to the device. This feature requires MaaS360 for Android version 7.20+.

MaaS360 supports the following attributes:
Key Supported values Description
lock_on_reboot
  • true
  • false
 true: Users cannot skip the enrollment screens. If the device is turned off during the setup, the device is locked to MaaS360 on reboot to resume the enrollment from where the enrollment process left off.
device_name_prefix csn Assigns the device CSN and the device model number as a device name. If the device CSN attribute is added, the order of precedence for the device name is custom device name > asset name > username > device CSN. For more information about the custom device name, see https://www.ibm.com/support/pages/node/5737563.
enable_debug_log
  • true
  • false
  • true: Debug mode is enabled on the device. MaaS360 generates a detailed log of application activity that assists the support team in troubleshooting the issue.
  • false: Debug mode is disabled on the device and the MaaS360 agent cannot capture device logs.
use_persistent_device_id
  • true
  • false
 When set to true, MaaS360 generates a consistent device identifier that remains the same for the device even if the work profile is removed and re-enrolled, or the device is wiped and re-enrolled.
Note: This setting is supported on Android 11 and earlier devices only. The consistent device ID is automatically generated for Android 12+ devices.
force_enrollment_before_provisioning
  • user_controlled
  • Yes
  • No
  • user_controlled: Users can control whether they want to enroll devices before or after the initial device setup.
  • Yes: MaaS360 forces device enrollment on factory reset devices before the initial device setup.
  • No: MaaS360 starts device enrollment after the initial device setup.
enrollment_request_mechanism
  • parallelEnrollment
  • useLegacy
  • useAdvance
  • parallelEnrollment: MaaS360 allows enrollment of multiple devices simultaneously. By default, an enrollment request is used for the enrollment of one device only. If you enroll multiple devices, MaaS360 creates a new enrollment request for each user (or email address that is specified in the QR/JSON).
  • useLegacy: MaaS360 uses this value by default if the Authentication Mode for Enrollment in the MaaS360 Portal is set to Passcode. You must use this value only for the troubleshooting of authentication issues during the Device Owner (DO) or Work Profile on Corporate Owned (WPCO) enrollments.
  • useAdvance: This is the default value. If an enrollment request is already available for the existing user or email ID, MaaS360 uses that enrollment request. If an enrollment request is unavailable, MaaS360 creates a new request automatically in the background.
The supported values are alphabets, numbers, and the underscore sign _.