check before: 2025-08-31
Product:
Exchange, Microsoft 365 admin center, Microsoft Graph
Platform:
Developer, Online, Web, World tenant
Status:
Launched
Change type:
Admin impact, New feature, Retirement, Updated message, User impact
Links:
Details:
Summary:
The new Message Trace in Exchange Online is generally available, replacing legacy cmdlets and UI starting September 1, 2025. The legacy tools will be supported in parallel for months, with full deprecation by March 18, 2026. Admins should update scripts and begin using the new experience.
Details:
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.
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
General Availability, Preview
Created:
2025-06-12
updated:
2025-12-20
Public Preview Start Date
XXXXXXX ... free basic plan only
Task Type
XXXXXXX ... free basic plan only
Docu to Check
XXXXXXX ... free basic plan only
MS How does it affect me
XXXXXXX ... free basic plan only
MS Preperations
XXXXXXX ... free basic plan only
MS Urgency
XXXXXXX ... free basic plan only
MS workload name
XXXXXXX ... free basic plan only
linked item details
XXXXXXX ... free basic plan only
summary for non-techies**
XXXXXXX ... free basic plan only
Direct effects for Operations**
Deprecation of Legacy Message Trace
Admins will lose access to legacy Message Trace cmdlets and UI, leading to potential disruptions in message tracking and reporting capabilities.
- roles: Exchange Administrators, IT Support Staff
- references: https://techcommunity.microsoft.com/blog/exchange/announcing-general-availability-ga-of-the-new-message-trace-in-exchange-online/4420243
Increased Training Needs
Users may require additional training to adapt to the new Message Trace interface and functionalities, impacting productivity during the transition period.
- roles: Exchange Administrators, End Users
- references: https://techcommunity.microsoft.com/blog/exchange/announcing-general-availability-ga-of-the-new-message-trace-in-exchange-online/4420243
Script Failures
Existing automation scripts using legacy cmdlets will fail, causing interruptions in automated reporting and monitoring processes.
- roles: Exchange Administrators, DevOps Engineers
- references: https://techcommunity.microsoft.com/blog/exchange/announcing-general-availability-ga-of-the-new-message-trace-in-exchange-online/4420243
Data Migration Issues
If organizations rely on Reporting Web Service for Message Trace data, failure to migrate to new cmdlets may result in data loss or reporting gaps.
- roles: Exchange Administrators, Data Analysts
- references: https://techcommunity.microsoft.com/blog/exchange/announcing-general-availability-ga-of-the-new-message-trace-in-exchange-online/4420243
User Experience Disruption
Users accustomed to the legacy interface may experience confusion and frustration with the new Message Trace UI, affecting their workflow.
- roles: End Users, IT Support Staff
- references: https://techcommunity.microsoft.com/blog/exchange/announcing-general-availability-ga-of-the-new-message-trace-in-exchange-online/4420243
Configutation Options**
XXXXXXX ... paid membership only
Potentional Risks**
XXXXXXX ... paid membership only
IT Security**
XXXXXXX ... paid membership only
explanation for non-techies**
Microsoft is updating the way email tracking works in Exchange Online, similar to how a city might upgrade its public transportation system. Imagine the old system as a network of buses that have been running for years. These buses (or tools) are reliable but might not be the fastest or most efficient. Now, Microsoft is introducing a new fleet of high-speed trains (the new Message Trace) that can carry more passengers (data) faster and with more comfort (features).
Starting September 1, 2025, the old buses (legacy Message Trace tools) will start to be phased out, but they will still run alongside the new trains for a while to help everyone transition smoothly. By March 18, 2026, the old buses will be completely retired, and only the new trains will be in service.
For those managing these changes, it's like preparing your team for a new commute. You’ll need to familiarize yourself with the new train schedules and routes (the new Message Trace features and cmdlets) and update any travel plans (scripts and automations) that relied on the old buses. This ensures that your daily operations continue without a hitch.
The new system promises better performance and additional features, such as the ability to look back at 90 days of email history, much like how the new trains might offer faster travel times and more frequent service. You can start using the new trains now, and it's recommended to update any old travel plans by August 31, 2025, to ensure a seamless transition.
If you have feedback about the new system, you can share it directly through the Exchange admin center, much like how passengers might provide feedback on their new commute experience. This helps Microsoft make further improvements to the service.
Overall, this change is about moving to a more modern, efficient way of handling email tracking, ensuring that your organization can keep up with the pace of communication needs.
** AI generated content. This information must be reviewed before use.
a free basic plan is required to see more details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
change history
| Date | Property | old | new |
| 2025-12-20 | MC Messages | Updated November 21, 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 is 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) 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. | 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. |
| 2025-12-20 | MC Last Updated | 11/21/2025 23:46:58 | 2025-12-19T18:52:52Z |
| 2025-12-20 | MC Summary | The new Message Trace in Exchange Online is generally available, replacing the legacy version. Legacy cmdlets retire September 1, 2025; Reporting Web Service support ends March 18, 2026. The new trace offers improved features and PowerShell cmdlets. Transition and update scripts by August 31, 2025. | The new Message Trace in Exchange Online is generally available, replacing legacy cmdlets and UI starting September 1, 2025. The legacy tools will be supported in parallel for months, with full deprecation by March 18, 2026. Admins should update scripts and begin using the new experience. |
| 2025-11-22 | MC Messages | 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. | Updated November 21, 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 is 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) 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. |
| 2025-11-22 | MC How Affect | 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. | 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. |
| 2025-11-22 | MC Last Updated | 08/28/2025 22:41:30 | 2025-11-21T23:46:58Z |
| 2025-11-22 | MC 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) https://techcommunity.microsoft.com/blog/exchange/announcing-general-availability-ga-of-the-new-message-trace-in-exchange-online/4420243 https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=495489 | 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) https://techcommunity.microsoft.com/blog/exchange/announcing-general-availability-ga-of-the-new-message-trace-in-exchange-online/4420243 https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=495489 |
| 2025-11-22 | MC Summary | The new Message Trace in Exchange Online is generally available, replacing the legacy version. Legacy cmdlets retire September 1, 2025; Reporting Web Service support ends February 28, 2026. The new trace offers improved features and PowerShell cmdlets. Transition and update scripts by August 31, 2025. | The new Message Trace in Exchange Online is generally available, replacing the legacy version. Legacy cmdlets retire September 1, 2025; Reporting Web Service support ends March 18, 2026. The new trace offers improved features and PowerShell cmdlets. Transition and update scripts by August 31, 2025. |
| 2025-08-29 | MC 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 August 31, 2025. 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) https://techcommunity.microsoft.com/blog/exchange/announcing-general-availability-ga-of-the-new-message-trace-in-exchange-online/4420243 https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=495489 | 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) https://techcommunity.microsoft.com/blog/exchange/announcing-general-availability-ga-of-the-new-message-trace-in-exchange-online/4420243 https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=495489 |
| 2025-08-29 | MC MessageTagNames | New feature, User impact, Admin impact, Retirement | Updated message, New feature, User impact, Admin impact, Retirement |
| 2025-08-29 | MC Summary | The new Message Trace in Microsoft Exchange Online will be generally available from mid-June to late July 2025, with the legacy Message Trace retiring on September 1, 2025. Admins should transition to the new experience and update scripts using new cmdlets by August 31, 2025. No immediate admin action is required. | The new Message Trace in Exchange Online is generally available, replacing the legacy version. Legacy cmdlets retire September 1, 2025; Reporting Web Service support ends February 28, 2026. The new trace offers improved features and PowerShell cmdlets. Transition and update scripts by August 31, 2025. |
| 2025-08-29 | MC Last Updated | 06/12/2025 01:29:29 | 2025-08-28T22:41:30Z |
| 2025-08-29 | MC Messages | 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:] 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. | 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. |
| 2025-08-29 | MC How Affect | 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). Reporting Web Service support for Message Trace data | 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. |
| 2025-08-29 | MC Title | Microsoft Exchange Online: New Message Trace will be GA; legacy Message Trace will retire | (Updated) Microsoft Exchange Online: New Message Trace will be GA; legacy Message Trace will retire |
| 2025-08-29 | MC End Time | 09/30/2025 09:00:00 | 2026-06-01T09:00:00Z |
Last updated 2 months ago ago