M365 Archive
Back to latest version
You're viewing a historical snapshot from Aug 28, 2025. This is not the latest version.

Metadata at Aug 28, 2025

Message ID

MC1092458

View in Message Center

Last Updated

Aug 28, 2025

Published Jun 11, 2025

Service

Exchange Online

Tag

Updated message
New feature
User impact
Admin impact
Retirement

Roadmap ID

495489

View roadmap details

Platforms

Web

Act by

Aug 31, 2025

View the latest version See what changed since this version

MC1092458 - Microsoft Exchange Online: New Message Trace will be GA; legacy Message Trace will retire

Message Center

What changed since this version

removed textadded text

Updated August 28,December 19, 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 closerhas been delayed from December 2025 to the Public Preview release date.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) are still set to retire onwere deprecated starting back in September 1st,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 February 28th,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 February 28,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)

Snapshot from Aug 28, 2025

Updated August 28, 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.

This does not impact the deprecation timeline for the legacy Message Trace cmdlets. The legacy Message Trace cmdlets (Get-MessageTrace, Get-MessageTraceDetail) are still set to retire on 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 February 28th, 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 February 28, 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)