Feedback by UserVoice

Michael McNally

My feedback

  1. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Michael McNally shared this idea  · 
  2. 224 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    32 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Michael McNally commented  · 

    The current setting is appropriate as is. Many if not most companies do not want the IT guy reading all their email at will. Adding yourself as a delegate when needed provides some transparency, and is not an onerous task. Separation of powers is sometimes a good thing.

    Oh, and it is possible to set this ability with Role management, but Role customization is definitely for experts only. Perhaps a built in Role that can be assigned would be appropriate, as suggested by Carsten Due?

  3. 1,426 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    28 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Michael McNally supported this idea  · 
    An error occurred while saving the comment
    Michael McNally commented  · 

    In case anyone is thinking this is too hard to do, Netware servers had a remote console that ran in a browser almost 15 years ago.

    I can see where there would be limitations, but for basic tasks I think this should be done.

  4. 1,820 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    251 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your responses. We appreciate that you’ve taken the time to provide us with feedback to help make our products better.

    We’re actively working on significant improvements to the end user experience with the feature across Outlook clients. This includes improvements to the UX, the classification algorithms, and controls.

    Today, admins have a Power-Shell cmdlet that allows them to control the Clutter feature on a per mailbox level. Details of this can be found here: https://technet.microsoft.com/en-us/library/mt586787%28v=exchg.160%29.aspx?f=255&MSPPError=-2147217396

    Our decision to provide the cmdlet based control for Clutter was based on early feedback we received on the Clutter feature.

    We will continue to improve the admin controls based on the continued feedback. Considering the responses on this forum, it would be helpful to better understand the gaps in the current admin control story. Do you believe the gap here is in not having a tenant level control or not having…

    Michael McNally supported this idea  · 
    An error occurred while saving the comment
    Michael McNally commented  · 

    Set-Clutter -Enable $false sounds like a solution you can run on all mailboxes. (How to run this on all mailboxes is left as an exercise for the reader.)

    But here is the problem. There is no way for me to tell which users in my tenant disabled it themselves or if the setting just hasn't been turned on for them yet by Microsoft. And I'm going to guess that Microsoft can't tell this either.

    I had turned the setting off on my own mailbox in OWA several weeks ago, after getting the clutter email notification that is sent when the Clutter folder becomes enabled. Then yesterday, the clutter folder was back, with a new "What is clutter?" email in the folder. So apparently, setting this to enabled = $false won't stop Microsoft from turning it back on at some point when they make a pass through your tenants.

    Admin policy to disable for all or for select users really is needed. And really should have existed before this was rolled out. This practice of forcing features on customers before rolling out the admin tool for them really must stop.

    An error occurred while saving the comment
    Michael McNally commented  · 

    It's fine to add features. It's fine to have them turned on by default. It's understandable but annoying that some older features have no admin interface and are settable on a per PC or per user basis (example: AutoReply rules)...

    It's inexcusable to roll out new features without an admin interface to control the setting globally.

Feedback and Knowledge Base