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 creative and aggressive. We’ve rolled out ZAP (which is the automatic version of ‘search and destroy’), and we’ve improved our compliance search capabilities. Hopefully you’ve noticed these investments.
But, we’re not finished. We’re working right now to address some of the complaints and confusion around the Message Trace admin experience itself. Our strategy is to continue adding more events to the Office 365 Graph API, and provide ways for larger customers to get at larger datasets faster. More than just providing you with raw data, we’re working on Security & Compliance features that reduce the effort involved and focus on specific tasks, like identifying which campaigns we’ve protected you from, and what suspicious activity you might want to beware of.
We also hear the feedback about improving subject based search, improving the retention time of Message Trace beyond 7 days, and continuing to improve performance. While we have nothing additional to communicate specifically in these areas at this time, we continue to welcome feedback and scenarios that helps us prioritize — know that we’re listening and we’ll continue working to improve these scenarios.
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…
Message tracking on 15 days for 1 user (about 50 email) not yes completed after 23 hours????
The MS support told me that is normal behaviour, it can take 4 days... are you aware that this tool is totally useless and it waist the time of the IT support and also of the user that need support????
UB
Message tracking on 15 days for 1 user (about 50 email) not yes completed after 23 hours????
The MS support told me that is normal behaviour, it can take 4 days... are you aware that this tool is totally useless and it waist the time of the IT support and also of the user that need support????