Archive: Microsoft Intune announces Preview 2 for Android Enterprise fully managed devices

Some feedback from the recent testing I have performed.  The deployment process has been hit and miss when performing the deployment process using the same device. On occasions it would never finish the installation of the Authenticator and Intune apps, other occasions it will be instant (feels like its nearly impossibly quick to install the 2 apps - however they appear to have installed...) On other occasions it appears that all applications have installed prior to the two core apps installing. We use dynamic groups to allocate some apps, we also have apps required on all Android devices (thus testing deployment times between static and dynamic groups).  Then we come onto the Compliance policy issue, the allocation and removal of this policy does not seems to be consistent either.  We removed the policy in order for configuration policies to apply, enrolled a device during this time and the Password enforcement workflow at enrolment  still applied (which comes from the compliance policy). We have also seen applications stating that they are installed successfully, when there is no sign of them on the device.  All of the above recent points raised in this forum, I too have experienced, but then cannot replicate it reliably. 

That all said, when it does work, its a beautiful experience, that paired with the long awaited Microsoft Launcher for Enterprise will be make our end user experience truly great. We want to get to the point where all deployments are OOBE and performed by the end user, this is the final link to that panacea.  If you would like to see our experience, check out our video: https://www.youtube.com/watch?v=AOyUnNd1LXM on YouTube.  Although some sections have been sped up, this was a real deployment process using Fully Managed Android. 

The only other feature requests to MS I want is the ability to have an application configuration policy (like Outlook) for the Microsoft Launcher allowing us to control the look, feel, feeds and accounts used.  This will allow us to provide a consistent look and feel across different devices e.g. Samsung and Pixels etc. I would also like the Intune app configuration to be part of the enrolment process (there does not seem to be a reason to auto deploy it without then configuring it - the device is already user aware (based on the enrolment) - use that information to then register the device into AzureAD via the Intune app automatically.