Feedback by UserVoice

Matt M.

My feedback

  1. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Matt M. commented  · 

    I also found this article with details of how long different audit event types take to show up in searches:

    https://support.office.com/en-us/article/Search-the-audit-log-in-the-Office-365-Security-Compliance-Center-0d4d0f35-390b-4518-800e-0c7ec95e946c#PickTab=BYB

    According to this table Microsoft Teams events should appear within 30 minutes. However, in practice this takes 24 hours in a very small tenant that I tested in.

    Matt M. shared this idea  · 
  2. 18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Office 365 Security & Compliance » eDiscovery  ·  Flag idea as inappropriate…  ·  Admin →
    Matt M. shared this idea  · 
  3. 20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Matt M. commented  · 

    This is bad. We've seen many problems with the Sharepoint Online module, and now these are spreading out to the once solid Exchange Online module. MS - don't let these issues keep creeping into your management tools!

  4. 73 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Office 365 Admin » SharePoint Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Matt M. shared this idea  · 
  5. 146 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Matt M. commented  · 

    I agree, we would like to be able to report on the Outlook client version that our users are connecting to Exchange Online with. Thanks!

    Matt M. supported this idea  · 
  6. 34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Matt M. shared this idea  · 
  7. 60 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Matt M. supported this idea  · 
    Matt M. commented  · 

    I'd like to tack on to this idea. Powershell is a great way to automate user licensing, but this is a core administrative action and I believe this should be available directly in the GUI portal.

    It should be simple to set up entitlement plans using conditions based on user attributes. For our own use, we would benefit greatly from being able to set license plans based on UPN domain name and the department attribute. In a way I think this would be similar to setting up dynamic distribution lists in Exchange, but with a simpler to use interface or syntax.

    Even if this is never added to the GUI portal, we should definitely have easier licensing in Powershell. For instance, setting -DisabledPlans in license options is totally wrong. When a new service plan becomes available in our SKUs, which does happen, it will be on by default. Setting enabled plans in the license options would be the preferred way to approach this so that we have to explicitly add new service plans in our automation scripts.

  8. 1,795 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    86 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Matt M. supported this idea  · 
  9. 1,331 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    27 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Matt M. supported this idea  · 
  10. 181 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Matt M. shared this idea  · 
  11. 203 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Matt M. shared this idea  · 
  12. 1,810 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    250 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…

    Matt M. supported this idea  · 

Feedback and Knowledge Base