Andrew Chandler

My feedback

  1. 1,048 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    210 comments  ·  Distribution, Upgrades & Servicing  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Andrew Chandler commented  · 
    An error occurred while saving the comment
    Andrew Chandler commented  · 

    Terrible idea; Offering options to block via GPO/SCCM/Intune or at the time of configuration/install via ODT is simply not enough. O365 ProPlus goes on thousands of unmanaged personal devices for incidental use, so we have no way to block it there. Now if there was a tenant-wide option to block this, or a cloud-based configuration policy we can push, then that'd be fine, but neither of these things exist. This push should never happen in the first place. Microsoft, stay in your lane and focus on Microsoft Search's integration in Edge chromium, not other company's browsers.

    Andrew Chandler supported this idea  · 
  2. 26 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Andrew Chandler supported this idea  · 
    An error occurred while saving the comment
    Andrew Chandler commented  · 

    I think a smarter idea would be to do exactly the same behavior that Lync and Skype for Business did... Install it, but DO NOT auto-start until the user opens the application for the first time.

    Lets Microsoft deploy the software easily without users needing to install it after the fact, but also does not inundate users and orgs with Teams client popups if they are not ready for it yet. Doing this would suffice for portal downloads where app selection is not granular... for managed devices, admins can always simply exclude Teams in their XMLs when deploying via the ODT.

Feedback and Knowledge Base