Update 8/25/2025: Added more information and updated timeline related to legacy message trace support in Reporting Webservice.
Today, we are excited to announce the GA of the new Message Trace in t...
Updated Aug 25, 2025
Version 5.0
Blog Post
3 MIN READ
Announcing General Availability (GA) of the New Message Trace in Exchange Online
It appears to me that these throttling limits are incredibly low. The only thing that I use Get-MessageTrace for, is to pull an entire day's email activity to find out which messages are not using TLS encryption. Microsoft does not provide any other method determine which messages are not using TLS. When I query this information, it currently takes over a day to pull one day's worth of message trace information, which I believe is due to current throttling limits. The results of my queries are regularly more than 150,000 rows. With your new throttling limits, it appears that this will take more than 15 DAYS, to pull 150,000 rows of data. Why would you put such incredibly low limits in place? This makes it impossible to use.
In addition, the fact that Exchange Online customers have no way to stream message trace logs internally (via an API) makes these throttling limits overly restrictive. In large organizations that are doing automation and have numerous support technicians tracing email for end users, a limit of 100 queries in 5 minutes could be hit fairly frequently.