💡 Our Technical Review in summary
- Microsoft is transitioning Message Trace capabilities from the legacy Reporting Web Service (RWS) to the Microsoft Graph API.
- This update provides a modern, REST-based API experience for programmatically tracing emails across Exchange Online organizations.
- Public Preview is currently available, with General Availability (GA) expected to roll out between late January 2026 and early February 2026.
- The legacy Reporting Web Service endpoints for message trace are scheduled for retirement starting April 6, 2026.
Impact
- Administrative/Developer Tools: Admins and developers who rely on automated scripts, custom applications, or third-party integrations to perform message traces will be affected.
- Legacy Retirement: Any automation currently using the Reporting Web Service for message trace data will stop functioning after April 6, 2026.
- New Organizations: Newer Exchange Online tenants already lack access to the legacy Reporting Web Service and must use the Graph API for these functions.
- End Users: There is no direct impact on end users; this change is strictly limited to administrative and developer tooling.
Action Required
- Audit Existing Scripts: Identify all PowerShell scripts, automation workflows, and internal tools that utilize the legacy Reporting Web Service for message tracing.
- Plan Migration: Begin transitioning programmatic calls to the Microsoft Graph API. Public Preview is available now for testing and development.
- Update Documentation: Ensure internal technical documentation and helpdesk SOPs are updated to reflect the move to Microsoft Graph.
- Deadline: Complete all migrations before the April 6, 2026 retirement date to avoid service disruptions in reporting and email auditing.
- Consult Documentation: Review the Exchange Team Blog and official Microsoft Graph API documentation for specific implementation details and migration guidance.
Microsoft Official Update
Service: N/A
Category: planForChange
Severity: normal
[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.
[How this affects your organization]
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 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.
[What you can do to prepare]
- 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 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.
