Message Trace support on Graph API is now in Public Preview

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