Troubleshooting
Problem
Starting with Android L (5.0) the feature that had been used in the past to block blocklisted applications on non-SAFE devices was removed, and a new access permission was required in order to maintain this functionality.
MaaS360 for Android version 5.75 adds this permission, but it is not part of the standard activation workflow, and initiates a prompt that some end-users and admins may find confusing.
The setting that MaaS360 needs access to is called "Usage Data Access" This will give MaaS360 the ability to block blocklisted app usage on MDM controlled devices.
If the device is on an MDM policy with App Compliance settings, the user will get a prompt if it is not enabled, and appear as out of compliance in the portal

Symptom

Cause
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
15 August 2019
UID
ibm10959709