O365 message trace from https://reports.office365.com/ecp is having issue from 12:00 PM 10/12/2025 (EST)

Hi Venkatesan, Radhakrishnan,

Thank you for posting your question in the Microsoft Q&A forum. 

From your description, it appears you’re calling the following endpoint: https://reports.office365.com/ecp/reportingwebservice/reporting.svc/MessageTrace[?ODATA options] to fetch Message Trace data and, since yesterday, you’re no longer receiving logs, could you please confirm if this is correct?

After reviewing your initial details, I performed a quick check. I could not find any recent, publicly reported incidents that match this behavior, nor any newly published change announcements that specifically call out an outage for the Reporting Web Service. In addition, the service health view currently indicates the Reporting service is operating normally.

To help narrow down the issue, could you share a bit more information:

1. When you say “not able to receive logs,” do you mean the API returns an empty result set (HTTP 200 with no data), or are you seeing error status codes (e.g., 401/403/404/429)? If there are errors, please share the code and a redacted sample of the request.
2. What date/time range are you querying? Have you tried running the same query against earlier dates that previously returned data, to confirm whether the issue is limited to recent events?
3. Have you validated the same criteria via the Message Trace cmdlets in PowerShell?

Additional insights that may help:

• According to Microsoft’s documentation on reporting data availability, events may be delayed by up to 24 hours before they appear in reports. If your queries target only very recent events, consider allowing for this delay and reattempting after some time.
  Reference: https://v4.hkg1.meaqua.org/en-us/previous-versions/office/developer/o365-enterprise-developers/jj984335(v=office.15)#data-granularity-persistence-and-availability
• Microsoft has announced that Message Trace support on the Reporting Web Service will deprecate, and customers should migrate to the new Message Trace PowerShell cmdlets by March 2026. Reference: https://techcommunity.microsoft.com/blog/exchange/announcing-general-availability-ga-of-the-new-message-trace-in-exchange-online/4420243

  “For those that are leveraging Reporting Webservice to pull Message Trace data, please migrate to and leverage the new Message Trace PowerShell cmdlets by March 2026. The new Message Trace will not be available on Reporting Webservice and Message Trace support on Reporting Webservice will begin deprecating starting March, 2026.”

  While the deprecation is scheduled for March next year, it’s possible Microsoft is making configuration changes in preparation (or preview) that could lead to intermittent behavior. With that in mind, it’s prudent to plan migration sooner to ensure you’re on the most current, supported path.

I hope the information above is helpful.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.