Microsoft
MicrosoftGlad to see improvements coming to this area, can't recall when it was last time!
90 days and subject filtering is something which will surely add value from OnPrem times.
We do understand sometimes MS might run into performance issues due to pagination, however the solution needs to be simple and workable. Instead of making it more difficult to get the dump.
The current options like commented by alexandruliviunita are confusing and doesn't appear to be able to provide the same results.
Get-MessageTrace -SenderAddress <emailaddress> -PageSize 5000 -Page 1000 | measure
"The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000."
MicrosoftThank you, Satyajit321for your thoughtful comments and feedback. This is Qingjun from Microsoft 365 Messaging Team. We're pleased to hear that you're glad about the improvements coming to the Message Trace feature. We'd like to address each of your points to provide clarity:
StartingRecipientAddress - Unclear how it continues without causing duplications
We will update the blog post to provide a more detailed explanation of how this parameter works and how it helps in retrieving subsequent records while minimizing duplication.
"For messages with over 1000 recipients, admins must include the MessageTraceId in both the EAC and PowerShell cmdlet queries to avoid partial results." - While running a bulk query, how a admin is suppose to keep track or be aware, if there are 1000+ recipients or not. Is EXO going to warn that the data is partial before of xzy reason. Pagination never had such issues, just give the sender and it kept going on.
You raised a valid concern about how admins can be aware of messages with over 1000 recipients to avoid partial results. We plan to implement a warning notification in such cases. This warning will inform admins when a message has more than 1000 recipients, so they can query that specific message using the MessageTraceId to retrieve all recipient data.
We could even jump and get total counts without having to traverse one by one. How do we get this done using the new PS. I can count upto a 5M emails in few seconds for a query.
We appreciate your feedback on this matter. Could you please clarify why it is necessary to count up to 5M directly without knowing the results of previous pages? In the new message trace, we recommend narrowing down the query duration and specifying filters to achieve the expected results more efficiently. For data dumping, narrowing down the query duration will also enhance query performance. We will update the blog with more details.
"Enhanced summary report: Available only as a downloadable CSV file. The report returns up to 100,000 results." - What's with Historical data exports where we can download bulk results, any changes to them or they just stay the same, supports more filters as above.
No plan for enhanced summary report.
"Result size parameter: The new Message Trace will support a default value of 1000 results and a maximum of 5000 results (set via the -ResultSize parameter), which is a significant increase." - What's the significant increase here, appears to be just same as what PageSize supported.
Thanks for pointing it out. We initially planned to support a larger result size but encountered issues that prevented this. We will update the blog post to accurately reflect this information and avoid any confusion.
We truly appreciate your feedback, as it helps us improve both our communication and the features we offer. Your input is valuable in ensuring that the new Message Trace meets the needs of admins. Please feel free to share any additional thoughts or questions you might have.
Qingjun_Chenthank you for your detailed response and planned actions. Please find the addtional information as requested and few more questions.
