Recommended MDM for Android

Forums › IT Pro and developers › Recommended MDM for Android

Paul1977

5171 posts

Uber Geek
+1 received by user: 2192

#299093 10-Aug-2022 12:41

We're looking at providing Android phones for about 40 staff, which will require a variety of apps installed on them for work purposes. We use Intune as part of 365 for managing laptops, but none of the staff requiring these phones are licensed for 365 as the have no need of email or Office apps, so not sure if Intune is a good option (or if it's even any good for Android devices).

What MDM solution do people recommend for Android devices? Cloud managed would be preferred, and not too expensive.

Home: Work:
Home Work

Dynamic

4015 posts

Uber Geek
+1 received by user: 1851

ID Verified

Trusted

Lifetime subscriber

#2952995 10-Aug-2022 12:47

Have a look at using 365 F1 licenses Licenses available for Microsoft Intune | Microsoft Docs

“Don't believe anything you read on the net. Except this. Well, including this, I suppose.” Douglas Adams

Paul1977

5171 posts

Uber Geek
+1 received by user: 2192

#2953005 10-Aug-2022 13:10

Dynamic:

Have a look at using 365 F1 licenses Licenses available for Microsoft Intune | Microsoft Docs

Thanks. I'm going to ask a dumb question here: 365 F1 is $3.40/month, while an Intune Device License on it's own is $4.00/month.

If 365 F1 offers Intune (which it does) along with other things for a lower price, why would anyone opt for an Intune Device license which would appear to only offer Intune? Am I missing something here?

Andib

1395 posts

Uber Geek
+1 received by user: 974

ID Verified

Trusted

#2953006 10-Aug-2022 13:14

Paul1977:

Thanks. I'm going to ask a dumb question here: 365 F1 is $3.40/month, while an Intune Device License on it's own is $4.00/month.

If 365 F1 offers Intune (which it does) along with other things for a lower price, why would anyone opt for an Intune Device license which would appear to only offer Intune? Am I missing something here?

The main difference is F1 is per user where as the device licence is per device.
If you have a 1 to 1 relationship between device and user then F1 is the right option but if you have shared devices (which require everyone who use it to be individually F1 licenced) a device licence often works out to be cheaper.

<#
.DISCLAIMER
Anything I post is my own and not the views of my past/present/future employer.
#>

nicmair

250 posts

Master Geek
+1 received by user: 40

#2953013 10-Aug-2022 13:26

have used and was impressed with HexNode, (although not the cheapest), but also a plus 1 for Intune, (which we migrated to from Hexnode, (only cause we get a very good deal on Intune as a NfP, thanks Microsoft))

Paul1977

5171 posts

Uber Geek
+1 received by user: 2192

#2953017 10-Aug-2022 13:47

Andib:

The main difference is F1 is per user where as the device licence is per device.
If you have a 1 to 1 relationship between device and user then F1 is the right option but if you have shared devices (which require everyone who use it to be individually F1 licenced) a device licence often works out to be cheaper.

That makes sense, sound like F1 would be the way to go if we want to use Intune.

Paul1977

5171 posts

Uber Geek
+1 received by user: 2192

#2968103 14-Sep-2022 14:20

OK, so we are trialing the 365 F1 plan so we can use Intune to manage Android phones.

Phones are configured as "Corporate-Owned Work Profile".

It's all pretty straight forward, but am having issues with the "Device Restrictions" policy when assigning passcode requirements. Policy is set to require numeric passcode with a minimum 4 digits, so pretty basic. However Intune is reporting errors on most of the policy settings related to the passcode, but isn't given any useful information. Those portions of the policy are not being enforced

I'm relatively new to Intune, so not sure how to dig any deeper than what I'm being presented below: