In a previous post I talked about the admin tasks required in setting up Mobile Device Management in Office 365, in this post I look at the end user experience on Android.
During this testing I’m using an Android device running version 5.1.1 and I’m using Microsoft’s Outlook App rather than the built in mail client.
Upon opening the app for the first time I’m presented with the usual login box
Because I’ve already turned on MFA on my account I get prompted to authorise the app (I strongly encourage everyone to have Multi-Factor Authentication turned on wherever it is available)
Once authenticated I’m prompted to Enrol my device before I can continue
After clicking Enrol my browser opens and I’m told I need the Intune app, which is available from the Play store
The app is a small download
It needs access to the device and lists its requirements as:
After installation and opening the app we’re presented with another Sign In prompt.
After signing in we get the option to enrol the device, it’s still not too late!
One last confirmation of what we are going to allow it to do.
Now the device goes through the enrollment process
We’re prompted to name the certificate that’s installed, I chose to leave mine the default
We’re then greeted with the Intune application page
On the My Devices tab we can see the enrolled device
To check the details and compliance information you can click on the system generated device name to bring it up
You can change the device name by clicking on the pencil icon to make it something more recognisable.
From an admin perspective we can now see the device in the portal and are able to wipe if need be.