Microsoft

Microsoft Endpoint Manager Intune Feedback

Suggestion box powered by UserVoice

Gabe

My feedback

  1. 549 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google Microsoft Intune
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    25 comments  ·  Ideas » Mobile Device Management (general)  ·  Flag idea as inappropriate…  ·  Admin →
    Gabe supported this idea  · 
    Gabe commented  · 

    I am surprised this Idea has not received any more input, yet, given that it's almost a year old. Yes, it is essential that administrators can set the sequence or order of the policies and applications rolled out. With a user setting up their device in EMS, he would want to have Office 365 Pro (Plus) client installed first so that he can get down to work as soon as possible. Instead, our Intune is pushing nifty small Windows updates first, letting our employees sitting in front of their computers wasting precious time.

    The Intune client has become our single biggest obstacle to the EMS rollout.
    Frankly, I wouldn't recommend Intune to anyone as long as the local client receives some loving or is replaced via MDM completely. Frankly speaking, I'm surprised how poor the client performs.

  2. 22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google Microsoft Intune
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Ideas » Mobile Device Management (general)  ·  Flag idea as inappropriate…  ·  Admin →
    Gabe commented  · 

    Seconding this request for Office 365 Pro Plus software deployment. When deploying said software on Azure AD joined devices, the user needs to manually sign in (when starting Word, PowerPoint, or Excel 2016 first) OR completely configuring his account (when starting Outlook 2016 first).
    It makes no sense because the user credentials are already in the password vault.

    Gabe supported this idea  · 

Feedback and Knowledge Base