The BES must be able to support policies and restrictions for Android for Work App edition and Andoid L devices.
- an admin can create corresponding policies and assign to users/groups in the BES console
- the resulting policy is provisioned to Android for Work on the user's device
- the following policies should be supported
Note, that some of the policies do not apply to Mixed-Use/BYOD Activations
Password (guidance should be policies provided by Android for Work API; minimum below):
Minimum Length
Minimum Number of Uppercase Letters
Minimum Number of Lowercase Letters
Minimum Number of Letters
Minimum Number of non-letter characters
Minimum Number of Symbols
Time to Lock (Lock work space after inactivity)
Password History
Password expiration timeout
Failed passwords for Wipe
Device functionality (guidance should be policies provided by Android for Work API; minimum below):
Disable WiFi (for Corporate-only)
Disable bluetooth (for Corporate-only)
Disable USB mass storage (for Corporate-only)
Disable camera (for Corporate-only)
Disable roaming (for Corporate-only)
Block adding of accounts (for Corporate-only)
Disable notifications on keyguard screen
Security
Require encryption
Browser (applies to the Android for Work browser)
--> as listed in the Google AfW documentation
Note: some of the policies may no be available in the current Android release. Please inform EPM on success for specific settings so follow on requirement can be generated.
Use Case:
An enterprise wants to enable their device users to use Android for Work on Android-L AfW certified devices and use BES as their EMM service.
Business Justification:
- Android for Work is expected to be the unified approach to EMM on Android devices.
- BlackBerry needs to support AfW to remain relevant as an EMM vendor for Android.
- policies and restrictions are key EMM functionality to allow enterprises to enforce their security requirements.