Microsoft Intune Feedback

Suggestion box powered by UserVoice

How can we improve Microsoft Intune

MAM Without Enrolment: Android - Remove Requirement for Company Portal

In MAM without Enrolment, on Android devices the Company Portal is required to be installed, but for iOS it is not.
Can the dependency be removed as it is not required as the Android device does not need to be enrolled.

387 votes
Sign in
Sign in with: Facebook Google Microsoft Intune
Signed in as (Sign out)
You have left! (?) (thinking…)
Mike shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: Facebook Google Microsoft Intune
Signed in as (Sign out)
  • Matt Lavieri commented  ·   ·  Flag as inappropriate

    I believe this request is for Android to mirror iOS capabilities not the other way around.

    In Android, the user is forced to install the Company Portal App and in doing so is asked to set up the device a managed device. The user has 2 options, to Postpone the enrollment (making the device MAM) or Continue (To go down the MDM route).

    I'd hate to see all these votes be mis-interpreted. Attached is the screenshot of the enrollment screen for Android that I believe is sat the heart of this ask.

  • T commented  ·   ·  Flag as inappropriate

    Would be awesome to just have Intune Company Portal with a splash page that says its MDM Enrolled or MAM Without Enrolment.

    If the Intune app is required on Android to perform certain actions/functions, a consistent user experience with significantly improve user adoption. Very confusing to users when we say use MS Authenticator on IOS but not on Android.

  • Josef Maung commented  ·   ·  Flag as inappropriate

    Piling on with everyone else on this. I don't mind the company portal requirement on Android, it's just the end user and admin experience of an "accidental" enrollment that bugs me. In our case we're going to implement enrollment restrictions for Android, but that's not really ideal either as it just throws the user an error when they try to do exactly what the app is asking them to do.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Definitely should be the same on both mobile platforms (iOS & Android). Company Portal App can be confusing since we are only requiring MAM-WE.

  • Scott Arndt commented  ·   ·  Flag as inappropriate

    Alternatively, if the Company Portal will continue to be required, the prompt for enrollment should be removed and moved to an "Opt-In" enrollment model where apps that only require MAM-WE just work, and apps that exist in the Company Portal that require enrollment are notated with "Enrollment Required".

  • Doug commented  ·   ·  Flag as inappropriate

    I agree it would be better to match up the iOS experience by using MS Authenticator app, which most of our users already have for MFA. Guiding users to the Company Portal app raises questions, and it shows them things that are confusing such as that their device is not compliant/managed.

  • Frank Bastone commented  ·   ·  Flag as inappropriate

    It seems the Authenticator app is no longer required on iOS (just confirmed this last week). If it can be done for iOS, surely something can be done for Android as well?

  • Francis Gocinski III commented  ·   ·  Flag as inappropriate

    Apparently this is the only way to send policy to the managed apps if not enrolled in MDM... Android needs the company portal, iOS needs the MS Authenticator app.

  • Bill Wood commented  ·   ·  Flag as inappropriate

    The requirement for Company Portal without enrollment is preventing Chromebook users from using O365, because Intune Company Portal is not available on the Chromebook. Please remove requirement for the Company Portal in that case.

  • Arnaud Seigle-Goujon commented  ·   ·  Flag as inappropriate

    We are not making the MAM available to 8 000 employees just because this requirement is confusing for BYOD users (They associate Intune to a managed device)

  • Miguel Duarte commented  ·   ·  Flag as inappropriate

    There could at least be an MDM and MAM option on the splash screen of the Company Portal - We know 100% that when MAM controlled users download the Company Portal they'll instinctively press the "Sign-In" button and enroll their devices, and that is definitely not something we want.

  • D commented  ·   ·  Flag as inappropriate

    The Android experience is a little clunky requiring the Company Portal app to be used with Outlook, appreciate it's required as the app uses components from the Company Portal to function. Not sure why this functionality can't be coded into the Outlook app itself instead or even have it as a seperate app like an "Outlook for Business". Just makes the end user experience a little more seamless.

  • Paolo commented  ·   ·  Flag as inappropriate

    I agree with Alex

    "the iOS requirement is better - Users are much happier to have the authenticator app on their device (which they need for MFA anyway) than the Company Portal app."

    and let's be honest.. please uniform the rules! MAM requiremente should be the same on "all" platforms

    The closer that Android and iOS management can be, the better.

  • Joel Porterfield commented  ·   ·  Flag as inappropriate

    Android requires an agent on the device to execute many of the policy settings that are configured in a MAM-WE policy, this is an Android limitation.

  • Alex Macaronis commented  ·   ·  Flag as inappropriate

    I like the iOS system better - Users are much happier to have the authenticator app on their device (which they need for MFA anyway) than the Company Portal app (which implies greater management by IT)

    The closer that Android and iOS management can be, the better.

  • Nils van Woensel commented  ·   ·  Flag as inappropriate

    That actually has good reasons. For Android the Company portal is used for many things. Also for token sharing between Office apps/corporate apps. For IOS the Authenticator app is used. So The company portal for Android and the Authenticator app for IOS are in my opinion always good to be installed.

Feedback and Knowledge Base