Hi there, We’re seeing consistent ingestion failures with the Message Trace (MT) input in the Splunk Add-on for Microsoft Office 365. - Authentication to Microsoft 365 succeeds. - However, every request to the Message Trace endpoint returns HTTP 500, regardless of how small the query window is. - To rule out an overly large time range, i cloned the MT input and tested with a very small window (e.g., 15 minutes for today’s data). The request still fails with repeated 500 responses. - Other inputs are OK. 2026-03-05 13:12:36,078 level=ERROR logger=splunk_ta_o365.modinputs.message_trace datainput="MT_test1" start_time=1772712742 message="HTTP Request error: HTTPSConnectionPool(host='reports.office365.com', port=443): Max retries exceeded with url: /ecp/reportingwebservice/reporting.svc/MessageTrace?$filter=StartDate eq datetime'2026-03-05T00:00:00Z' and EndDate eq datetime'2026-03-05T00:15:00Z' (Caused by ResponseError('too many 500 error responses'))" ... (stack trace omitted)  Q1: Have you seen this behavior (persistent HTTP 500) from the Message Trace Reporting Webservice endpoint? Q2: Are there known service-side limitations or tenant-specific issues that can cause this? Q3: What are the recommended next troubleshooting steps and/or mitigations? Q4: I know its a legacy MT endpoint as of march 2026 but there is no update from o365 addon and im not feeling to make an input for MT from scratch. Any info when the new update is planned? Thanks in advance.   ... View more