ChangeIntelIT change radar
Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 21:53 UTC Customize Public modeDiscuss ChangeIntel on Discord
MC1092458 Plan for changeUpdated messageNew featureUser impactAdmin impactRetirement

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

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.
Exchange Online
Microsoft 365 admin center

Action date

31 Aug 2025 421d ago Act by , as Microsoft's metadata states

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions this installation saw
  • Seen 19 Dec 2025 February 28th, 2026 → January 2026
  • Seen 21 Nov 2025 September 1st, 2025, February 28, 2026 → March 18th, 2026, December 2025, September 1st 2025, March 18, 2026
  • Seen 28 Aug 2025 mid-June 2025, late July 2025 → February 28th, 2026, September 1st, 2025, February 28, 2026

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, with source markup removed
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)

What changed

Between archive captures, newest first

  1. Updated November 21,December 19, 2025: The deprecation of the legacy Message Trace support on Reporting Webservice will be slightly delayed by two weeks from the original deprecation date of February 28th, 2026 to March 18th, 2026. The tentative timeline for Public Preview of the new Message Trace support on Graph API ishas been delayed from December 2025 to now December 2025.January 2026. This does not impact the deprecation timeline for the legacy Message Trace …

  2. Updated November 25,21, 2025: The deprecation of the legacy Message Trace support on Reporting Webservice …

  3. Updated August 28,November 25, 2025: Due to the customer feedback we've received, we will be delaying The deprecation of the legacy Message Trace support on Reporting Webservice until February 28th, 2026. Additionally, we will be onboarding the new Message Trace onto Graph API.will be slightly delayed by two weeks from the original deprecation date of February 28th, 2026 to March 18th, 2026. 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. now December 2025. 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 were deprecated starting back in September 1st,1st 2025. We are excited to announce the General Availability of the new … 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. … 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 …

    • Tags New feature, User impact, Admin impact, Retirement → Updated message, New feature, User impact, Admin impact, Retirement

    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 … 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 2025 and expect to complete by late July 2025. Retirement of legacy Message Trace begins September 1, 2025. July. How this will affect your organization: Like in Public Preview, the new … 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 … Service for Message Trace data, migrate to the new PowerShell cmdlets by August 31, 2025.February 28, 2026. To provide feedback on the new Message Trace, use Exchange admin center …

  5. · first version seen

Linked documentation

Microsoft pages the notice links to

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • 1 linked page has not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 26 Oct 21:53 UTC · 272 of 272 readable · 271 fully read · documentation 469/469 current

No accounts or analytics; your preferences stay in your browser. Information, not advice. ChangeIntel is an independent tool and is not affiliated with or endorsed by Microsoft, Apple, Google, Broadcom (VMware), Jamf, Oracle, Mozilla, or any other vendor it covers. Product names are trademarks of their owners. Built by Evotec.