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 the Exchange admin center (EAC) in Exchange Online for our WW customers. We will begin rolling out in mid-June and complete rollout in July. Like in Public Preview, administrators will be able to access the new Message Trace and its capabilities by default when navigating to the Exchange admin center > Mail flow > Message Trace. We received a lot of great feedback on the new message trace design, performance, and feature parity throughout Public Preview and will begin the transition to the new Message Trace experience. If you wish to give us additional feedback, please do so in Exchange admin center > Give Feedback.
Throttling limits
To reduce the risk of misuse and abuse of Exchange Online resources, ensure services availability for all users, and provide a predictable experience for our customers, we will implement a rate-based throttling limit based on the number of requests in a time period. For a tenant, a maximum of 100 query requests will be accepted within a 5-minute running window. Throttling is automatically not applied if the request rate is lower than 100 requests in the past 5 minutes. If your tenant has automation set up to query more frequently than the throttling threshold, please update your automation to fit below the throttling limit.
|
Cmdlet | Tenant level limit |
|
100 requests per 5 min | |
|
100 requests per 5 min |
Old Message Trace interface and cmdlets deprecation timeline
We will continue to maintain the old Message Trace UX in Exchange admin center and cmdlets (Get-MessageTrace and Get-MessageTraceDetail) alongside the new Message Trace interface and cmdlets (Get-MessageTraceV2 and Get-MessageTraceDetailV2) for several months to ease the transition. The old Message Trace interface and cmdlets (Get-MessageTrace and Get-MessageTraceDetail) will begin deprecating for our WW customers starting September 1st, 2025.
Due to the customer feedback we've received, we will be delaying the legacy Message Trace support on Reporting Webservice until February 28th , 2026. Additionally, we will be onboarding the new Message Trace onto Graph API. The tentative timeline for Public Preview of the new Message Trace support on Graph API is November. Further details will be announced closer to the Public Preview release date.
Please note that this timeline applies to our WW environment only and does not affect GCC, GCC-High, DOD, or other sovereign clouds. Timeline for GCC, GCC-High, DoD, and other sovereign clouds will be provided in CY25H2.
What you need to do to prepare
- Please use the new Message Trace user interface in Exchange Admin Center if you are not doing so already. The old Message Trace user interface will be deprecated starting September 1st, 2025.
- If you have automation set up that leverages the old Message Trace cmdlets, then you should migrate to using the new Message Trace cmdlets by latest August-end 2025. Get-MessageTrace and Get-MessageTraceDetail will be deprecated starting September 1st, 2025.
- For those that are leveraging Reporting Webservice to pull Message Trace data, please migrate to and leverage the new Message Trace PowerShell cmdlets by February 2026. The new Message Trace will not be available on Reporting Webservice and Message Trace support on Reporting Webservice will begin deprecating starting March, 2026.
Official cmdlet documentation for the new Message Trace cmdlets will be published by GA. Visit the Public Preview document to see our key changes from the old Message Trace.
Microsoft 365 Messaging Team
