💡 Our Technical Review in summary
Summary
- Microsoft is transitioning Exchange Online Message Trace from the legacy platform to a modernized experience with improved performance and feature parity.
- The new Message Trace experience is now Generally Available (GA) within the modern Exchange admin center (EAC) and via updated PowerShell cmdlets.
- Legacy Message Trace interfaces and cmdlets began their deprecation phase on September 1, 2025.
- The release of Graph API support for Message Trace has been rescheduled to January 2026.
Impact
- Exchange Admin Center: The legacy Message Trace UI is being retired. Admins should now use the modern interface located under Mail flow > Message Trace.
- PowerShell Automation: The legacy cmdlets
Get-MessageTraceandGet-MessageTraceDetailare deprecated. Scripts still using these commands will eventually fail and must be updated to the V2 versions. - Command Changes: Admins must transition to
Get-MessageTraceV2andGet-MessageTraceDetailV2for continued support and better performance. - Reporting Web Service: Organizations relying on the Reporting Web Service for message data will lose support starting March 18, 2026.
- API Access: While Graph API support is delayed until January 2026, the deprecation of legacy methods remains on the original schedule.
Action Required
- Audit Scripts: Identify all PowerShell scripts and automation tools that utilize
Get-MessageTraceorGet-MessageTraceDetail. - Update Cmdlets: Replace legacy cmdlets with
Get-MessageTraceV2andGet-MessageTraceDetailV2immediately to avoid service interruption. - Migrate Reporting: If your organization uses the Reporting Web Service for message data, begin planning a migration to the V2 PowerShell cmdlets or the upcoming Graph API endpoints before March 18, 2026.
- Documentation: Update internal IT SOPs, helpdesk manuals, and administrative documentation to reflect the new EAC navigation path and cmdlet syntax.
- Monitor Timeline: Stay alert for the January 2026 release of the Message Trace Graph API for more robust integration options.
Microsoft Official Update
Service: N/A
Category: planForChange
Severity: normal
Updated December 19, 2025: The tentative timeline for Public Preview of the new Message Trace support on Graph API has been delayed from December 2025 to now January 2026.
This does not impact the deprecation timeline for the legacy Message Trace cmdlets. The legacy Message Trace cmdlets (Get-MessageTrace, Get-MessageTraceDetail) were deprecated starting back in September 1st 2025.
We are excited to announce the General Availability of the new Message Trace in the Microsoft Exchange admin center (EAC) in Microsoft Exchange Online. This new experience, previously in Public Preview, offers improved performance, modern design, and enhanced feature parity. Admins can access it via Exchange admin center > Mail flow > Message Trace.
The GA release is associated with Microsoft 365 Roadmap ID 495489.
[When this will happen:]
- Retirement of legacy Message Trace begins September 1, 2025.
- General Availability (Worldwide): We will begin rolling out mid-June and expect to complete by late July.
[How this will affect your organization:]
- Like in Public Preview, the new Message Trace UX in EAC will be available by default and Microsoft PowerShell cmdlets (
Get-MessageTraceV2,Get-MessageTraceDetailV2) will be available. - The legacy Message Trace experience and cmdlets (
Get-MessageTrace,Get-MessageTraceDetail) will remain available in parallel for several months to support the transition. - Starting September 1, 2025, the following will begin deprecating:
- Legacy Message Trace UI in EAC.
- Legacy cmdlets (
Get-MessageTrace,Get-MessageTraceDetail).
- Starting March 18th, 2026, Reporting Web Service support for Message Trace data will begin deprecating.
[What you need to do to prepare:]
This GA rollout and retirement will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your admins and/or users about this change and update internal documentation.
- Begin using the new Message Trace experience in the Exchange admin center.
- Update any automation or scripts using legacy cmdlets to use the new versions by August 31, 2025.
- If you rely on the Reporting Web Service for Message Trace data, migrate to the new PowerShell cmdlets by March 18, 2026.
- To provide feedback on the new Message Trace, use Exchange admin center > Give Feedback.
Learn more about the GA rollout: Announcing General Availability (GA) of the New Message Trace in Exchange Online | Microsoft Community Hub (documentation will be linked to this blog before rollout)
