MC1221939 – (Updated) Message Trace support on Graph API is now in Public Preview

Microsoft Exchange Logo

check before: 2026-04-05

Product:

Exchange, Microsoft 365 suite, Microsoft Graph

Platform:

Developer, Online, Web, World tenant

Status:

Change type:

New feature, User impact, Admin impact

Links:

Details:

Summary:
Message Trace support on Microsoft Graph API is now in Public Preview, replacing legacy Reporting Web Service endpoints starting April 8, 2026. Admins and developers should migrate scripts and automation to the new RESTful API before retirement begins. General Availability rollout starts late January 2026.

Details:
Updated February 25, 2026: We have updated the content. Thank you for your patience.
[Introduction]
We're introducing Message Trace support on Microsoft Graph to provide a modern, REST‑based API experience for tracing email across your Exchange Online organization. This update aligns with our ongoing effort to move message trace support from the legacy Reporting Web Service to Microsoft Graph. Public Preview is now available, and General Availability roll-out begins January-end.
[When this will happen]
Public preview (worldwide): Available now.
General availability (worldwide): Rollout begins in late January 2026 and is expected to complete by early February 2026.

Change Category:
XXXXXXX ... free basic plan only

Scope:
XXXXXXX ... free basic plan only

Release Phase:

Created:
2026-01-24

updated:
2026-02-26

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

summary for non-techies**

Microsoft is transitioning its message trace support from the Reporting Web Service to the Microsoft Graph API, offering a more advanced and flexible RESTful experience for accessing and managing email trace data in Exchange Online, with the full rollout expected by early 2026 and the old system retiring in April 2026.

Direct effects for Operations**

Migration to Microsoft Graph API
Failure to migrate scripts and automation to the new Microsoft Graph API may lead to disruptions in message trace functionalities, affecting the ability to track email communications effectively.
   - roles: Admins, Developers
   - references: https://techcommunity.microsoft.com/blog/exchange/message-trace-support-using-graph-api-is-now-in-public-preview/4488587

Retirement of Legacy Reporting Web Service
If the legacy Reporting Web Service is not phased out properly, it may result in loss of access to critical message trace data, impacting operational reporting and monitoring.
   - roles: Admins, Developers
   - references: https://techcommunity.microsoft.com/blog/exchange/message-trace-support-using-graph-api-is-now-in-public-preview/4488587

Internal Documentation Updates
Neglecting to update internal documentation regarding message trace automation may lead to confusion and errors in operations, as teams may rely on outdated processes.
   - roles: Admins, Developers
   - references: https://techcommunity.microsoft.com/blog/exchange/message-trace-support-using-graph-api-is-now-in-public-preview/4488587

Communication with Dev/Ops Teams
Failure to communicate the changes to dev/ops teams may result in unpreparedness for the transition, leading to potential operational issues during the migration period.
   - roles: Admins, Dev/Ops Teams
   - references: https://techcommunity.microsoft.com/blog/exchange/message-trace-support-using-graph-api-is-now-in-public-preview/4488587

Impact on Automated Processes
Automated processes relying on the legacy Reporting Web Service may fail, causing delays in email tracking and reporting, which can affect decision-making.
   - roles: Admins, Developers
   - references: https://techcommunity.microsoft.com/blog/exchange/message-trace-support-using-graph-api-is-now-in-public-preview/4488587

Configutation Options**

XXXXXXX ... paid membership only

Opportunities**

XXXXXXX ... free basic plan only

Potentional Risks**

XXXXXXX ... paid membership only

IT Security**

XXXXXXX ... paid membership only

explanation for non-techies**

XXXXXXX ... free basic plan only

** 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

DatePropertyoldnew
2026-02-26MC prepareReview any scripts, automation, or integrations that use the Reporting Web Service for message trace.
Plan your migration to the Microsoft Graph message trace API before April 6, 2026, when retirement begins.
Update internal documentation where message trace automation or reporting is referenced.
Share this update with your dev/ops teams or helpdesk if they rely on trace automation.
For API details and migration guidance, refer to Message Trace support using Graph API is now in Public Preview | Exchange team blog | Exchange | Microsoft Community Hub.
[Compliance considerations]
No compliance considerations identified. Review as appropriate for your organization.
https://techcommunity.microsoft.com/blog/exchange/message-trace-support-using-graph-api-is-now-in-public-preview/4488587
Review any scripts, automation, or integrations that use the Reporting Web Service for message trace.
Plan your migration to the Microsoft Graph message trace API before April 8, 2026, when retirement begins.
Update internal documentation where message trace automation or reporting is referenced.
Share this update with your dev/ops teams or helpdesk if they rely on trace automation.
For API details and migration guidance, refer to Message Trace support using Graph API is now in Public Preview | Exchange team blog | Exchange | Microsoft Community Hub.
[Compliance considerations]
No compliance considerations identified. Review as appropriate for your organization.
https://techcommunity.microsoft.com/blog/exchange/message-trace-support-using-graph-api-is-now-in-public-preview/4488587
2026-02-26MC SummaryMessage Trace support on Microsoft Graph API is now in Public Preview, offering a modern REST-based experience for Exchange Online email tracing. It replaces legacy Reporting Web Service endpoints, which will retire starting April 6, 2026. Admins and developers should plan migration before then; no user impact expected.Message Trace support on Microsoft Graph API is now in Public Preview, replacing legacy Reporting Web Service endpoints starting April 8, 2026. Admins and developers should migrate scripts and automation to the new RESTful API before retirement begins. General Availability rollout starts late January 2026.
2026-02-26MC Last Updated01/24/2026 01:02:382026-02-25T22:31:38Z
2026-02-26MC Messages[Introduction]
We're introducing Message Trace support on Microsoft Graph to provide a modern, REST‑based API experience for tracing email across your Exchange Online organization. This update aligns with our ongoing effort to move message trace support from the legacy Reporting Web Service to Microsoft Graph. Public Preview is now available, and General Availability roll-out begins January-end.
[When this will happen]
Public preview (worldwide): Available now.
General availability (worldwide): Rollout begins in late January 2026 and is expected to complete by early February 2026.
Updated February 25, 2026: We have updated the content. Thank you for your patience.
[Introduction]
We're introducing Message Trace support on Microsoft Graph to provide a modern, REST‑based API experience for tracing email across your Exchange Online organization. This update aligns with our ongoing effort to move message trace support from the legacy Reporting Web Service to Microsoft Graph. Public Preview is now available, and General Availability roll-out begins January-end.
[When this will happen]
Public preview (worldwide): Available now.
General availability (worldwide): Rollout begins in late January 2026 and is expected to complete by early February 2026.
2026-02-26MC TitleMessage Trace support on Graph API is now in Public Preview(Updated) Message Trace support on Graph API is now in Public Preview
2026-02-26MC How AffectWho is affected: Admins and developers who use automated or programmatic message trace capabilities in Exchange Online. Admins and developers who use Reporting Web Service for message trace.
What will happen:
Message trace and message trace detail functionality is now available through Microsoft Graph API.
The API provides a modern, RESTful experience for querying message trace data.
This feature will replace the message trace and message trace detail endpoints in the legacy Reporting Web Service.
Retirement of the Reporting Web Service message trace endpoints begins April 6, 2026.
New Exchange Online organizations already do not have access to message trace support via the Reporting Web Service.
No user impact: this change affects admin and developer tooling only.
Who is affected: Admins and developers who use automated or programmatic message trace capabilities in Exchange Online. Admins and developers who use Reporting Web Service for message trace.
What will happen:
Message trace and message trace detail functionality is now available through Microsoft Graph API.
The API provides a modern, RESTful experience for querying message trace data.
This feature will replace the message trace and message trace detail endpoints in the legacy Reporting Web Service.
Retirement of the Reporting Web Service message trace endpoints begins April 8, 2026.
New Exchange Online organizations already do not have access to message trace support via the Reporting Web Service.
No user impact: this change affects admin and developer tooling only.

Last updated 2 weeks ago ago

Leave a Reply

Share to MS Teams

Login to your account

Welcome Back, We Missed You!