Update 5/6/2025: We added information about new cmdlet throttling limit.
Today, we are excited to announce that the Public Preview of the new Message Trace in the Exchange admin center (EAC) in Exc...
Updated Aug 27, 2025
Version 13.0
Blog Post
I'm finding even while "New Message Trace" is showing in the initial flyout after clicking "Start a trace", it's still limited to 10 days back in time, rather than just 10 days' worth in total. I've gone back less than 20 days and 4 days' worth starting from the 20 days ago mark, still must queue up an enhanced summary, no instant results.
Would be nice if somehow there was just another table like EmailEvents that was just MessageTrackingLogs. And then we could use KQL in either some new interface, or the Defender portal > Hunting.
Qingjun_Chen
Microsoft
MicrosoftThanks JeremyTBradshaw for the comments.
Are you still experiencing this issue on EAC?
Could you please specify the events and properties you need in MessageTrackingLogs?
Thanks,
Qingjun
M365 Messaging Team
Hi Qingjun_Chen,
No, thanks, I am no longer having that issue, the New Message Trace has been fixed and seems to behave as advertised now. In hindsight, when I posted that comment, the only new thing about it was the title at the top that stated "New Message Trace", everything else was still "old" message trace. Now both the title and the rest are the "new" variation. It's pretty good. Nonetheless, the KQL stuff would be nice still and from having looked around message tracking logs just now, these are the fields I feel would be required or essential/nice to have:
Timestamp
SourceContext
ConnectorId (assuming we'd see our Inbound/Outbound connectors there, when applicable)
Source
EventId
MessageId
NetworkMessageId
Recipients
RecipientStatus
TotalBytes
RecipientCount
MessageSubject
Sender
ReturnPath
Directionality
OriginalClientIp
MessageInfoWill be great if this actually comes along. Thanks!