We should be able to locate a lost or stolen Android device.

Support for Chromebook/Chrome O/S devices so they can be managed in BYOD scenarios, i.e. setup for Wireless, mail profile, security etc...

On Managed Devices we cannot enabled Google Backup. Users add their own Google account in the Play store and want to create/restore backups.

When a device is configured with Android Enterprise and the Microsoft Managed Home Screen in kiosk mode (as per here https://docs.microsoft.com/en-us/intune/android-kiosk-enroll), it is not possible to deploy LOB apps to these devices. If apps are sideloaded manually, they're automatically deleted by the device policy.

Being able to deploy LOB apps (or creating a whitelist) for Android Kiosk devices would allow Android Kiosk mode to be used to its full potential.

We need the ability to add system apps like the system camera or phone app to the work profile. Other EMM vendors already support this feature.

Is it possible to get Intune to allow Android for Work to be setup in Device Owner Mode? Possibly with the App and NFC "bump" to setup the config.

This possibly one of the requirement from within the NCSC guidance (https://www.ncsc.gov.uk/guidance/eud-security-guidance-android-6)

Phone number should be inventoried on Android Enterprise Dedicated and Fully Managed devices.

When Intune Compliance or MDM policy is applied to Android Devices, pattern unlock is disabled. Please add Allow Pattern Unlock to the list of password options.

https://docs.microsoft.com/en-us/intune-classic/deploy-use/android-policy-settings-in-microsoft-intune

Would be great to add support for the Fully Managed Device with Work Profile solution set as I am seeing lots of requests for this. Intune is one of the last EMM platforms to support this.

When having an Android device that is enrolled with Intune, enable the possibility to set a configuration policy that automatically enables Web browser access with respect to installing the management certificate on the device. This would simplify device compliance checks quite much.

Please support setting up Android for Work with G Suite managed accounts.
https://support.google.com/work/android/answer/6174046?hl=en&ref_topic=6174026#bind_third_party
https://developers.google.com/android/work/setup#google_accounts

This doesn't currently happen and is apparently "working as designed"

We have a large Samsung deployment where enhanced control of the OS update flows are required.
Samsung EFOTA allows us to do this.
Please add support for this feature.
https://www.samsungknox.com/en/solutions/it-solutions/samsung_e-fota

Enable a way we can enforce a policy to set a PIN code on Corporate Owned Dedicated Devices (Kiosk mode) PIN at a device level.

At present we are having to get our onsite IT staff to manually set a PIN on the device after enrollment, but still the users could go in and change the lock screen method from PIN code to Swipe, thus removing the security aspect.

Device enrollment will stuck in progress when trying to enroll OPPO device.
It stuks "setting up your work pofile" on Intune Company portal, and work profile Intune company portal won't shows up.

from OPPO support side answer is this below.

Due to the Intune company portal is not compatible with OPPO device currently, so if Intune company Portal will be updated as compatible with OPPO device, issue will be solved.

Thank you.

Allow Outlook Notifications on Smartwatches via Android Wear -

Today no Meeting or Mail notification can be displayed on a smartwatch while outlook is protected via intune work profiles

It seems that by default on android entreprise when you ask for a password on the work profile only, android choose to have the same password on both personnal and work profile.. It is called the One Lock option.

Would it be possible to disable this option ?

When you reset a passcode on an Android device, the new temporary passcode is WAY too complex: 15 characters and multiple special characters. It is just a temporary passcode for a mobile device, not a passcode to launch nuclear missiles! :-)

Make this temporary passcode much less complex. You could use e.g. the same mechanism that AAD uses for passwords to new user accounts:

Pass1234

(A capital letter + 3 small letters + 4 numbers).

This kind of temporary passcode is so much easier to enter to a mobile device.

It is not possible to enroll phones using qrcode or afw#setup method when user is MFA enabled. When the step “sign in to Microsoft” appear the user is MFA challenged but because the phone is in a state not accepting phone calls or SMS from MFA provider the challenge is timing out. Please don’t tell us to turn off or use bypass MFA for users to enroll.

Disable installation from unknown sources using Intune policies on Android devices. Android OS has an option where user can disable unknown sources so they can install THIRD PARTY apps.

setting--> General--> Privacy--> security-->under Phone Administrators -->Unknown sources

Unknown sources should be disabled for security purposes.

These apps are not tested and can control viruses hence should not be allow and is NOT on the official PLAYSTORE.

We need an option from the console for Admin to disable this option so user cannot change and allow unknown sources to be install onto the company's devices.