Seth Hohensee
My feedback
-
452 votesSeth Hohensee
supported this idea
·
-
358 votesSeth Hohensee
supported this idea
·
-
191 votesSeth Hohensee
supported this idea
·
-
34 votesSeth Hohensee
supported this idea
·
-
593 votes23 comments · Office 365 Security & Compliance » Message Trace · Flag idea as inappropriate… · Admin →
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…
An error occurred while saving the comment Seth Hohensee
supported this idea
·
-
233 votes13 comments · Office 365 Security & Compliance » Message Trace · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Seth Hohensee
commented
The small page size and result size for get-messagetrace makes it extremely difficult to use, especially given that it lacks subject filtering to refine the results.
Seth Hohensee
supported this idea
·
We get requests for data over a week old very frequently. Getting a spreadsheet several hours later just isn't responsive enough. Also, given the small result and page sizes, subject filtering is a must.