Feedback by UserVoice

Brian Seaman

My feedback

  1. 226 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    15 comments  ·  Office 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →
    Brian Seaman commented  · 

    REMEMBER O365 GROUPS ARE THE FUTURE ACCORDING TO POWERSHELL "create-distributiongroup" COMMANDS AND THE EAC... except that they are lacking 70% of the functionality of security groups and DL's.

    Glad I didn't blindly convert everything over.

    Brian Seaman supported this idea  · 
  2. 72 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Brian Seaman commented  · 

    How is this coming along? O365 groups are NOT the same as distribution lists or security groups, and I shouldn't have to see this message EVERY SINGLE TIME that I or one of the techs that I write these scripts for creates one.

    Brian Seaman supported this idea  · 
  3. 703 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thank you for your feedback. We have a clarifying question that would help us to prioritize this better: If you need notices 3 (or more) times per day, why use quarantine at all? Why not send the mails to a junk folder which the user can check on demand? If you want a notice each time any message gets quarantined, again, what prevents just sending the mails to a junk folder instead?

    Brian Seaman commented  · 

    I would also like to see this, and in addition a configurable notification to admins for the system quarantine. We've been seeing increasing false positives on the "anti-phishing" quarantine file, and many of these messages have been time-sensitive court notifications or summons.

    Having messages simply vanish on the way in, and then be delivered the morning after the court date, is causing users to become distrustful of the entire O365 mail and messaging system.

    Brian Seaman supported this idea  · 
  4. 523 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thank you for taking the time to submit this feedback. Since there are multiple pieces and layers of feedback in this single post, it makes it more difficult than many to address. First, let us share a little about what we’ve been doing. Since this post was made, we have prioritized performance and reliability improvements for both Message Trace (inside 7 days) and Historical Search (typically outside of 7 days). We’ve added details to Message Trace that weren’t there before, decreasing the need to run Historical Searches inside of 7 days. For Historical Search, we have improved the results to be more clear for those who are not familiar with the Exchange Message Tracking log format. Additionally, while we get the total value of Message Trace, we’ve also prioritized reducing the constant need to search & destroy. We’ve made tremendous strides in effectiveness, even as the bad guys got more…

    Brian Seaman supported this idea  · 
  5. 581 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    ATP does not consider mails from other Office 365 tenants, or even mailboxes inside of your tenant, as safe. The best way to put a stop to this is to follow the recommendations in SecureScore for your tenant; and report phishing mails to us promptly. Also, make sure that the sender is not allowed either by the tenant configuration or the user safelist.

    Brian Seaman supported this idea  · 

Feedback and Knowledge Base