EDIT 2/6/2026: this feature is now GA (Generally Available). Full onboarding instructions are in the documentation.
We are excited to announce that Message Trace support using Graph API is now GA. ...
Updated Feb 25, 2026
Version 5.0
Blog Post
The_Exchange_Team and Nino_Bilic
We are currently working with multiple enterprise customers to migrate from the Reporting Web Service (RWS) Message Trace API to the new Microsoft Graph-based Message Trace APIs.
While we appreciate the direction and the improvements with Graph, we are running into practical challenges meeting the April 8th deadline—primarily due to downstream dependencies on existing schemas and ingestion pipelines and the deployment and upgrade schedules we have with various customers. Given these dependencies, the migration is not a simple endpoint swap and requires careful rollout and validation across multiple systems.
Could the team share:
- Whether there is any consideration to extend the April 8th deadline?
- Any recommended migration strategies for customers with downstream SIEM integrations and schema-dependent pipelines?
Additional clarity here would significantly help teams plan and execute a safe transition without impacting detection coverage.
Appreciate the guidance.
Regards,
Mani.