I am currently working on the integration of the Message Trace API and wanted to clarify some details regarding the rate limit. The REST API I am currently using for O365 Message Trace for my integration is: https://reports.office365.com/ecp/reportingwebservice/reporting.svc/MessageTrace[?ODATA options]  

As mentioned previously,

The rate limits for the O365 Message Trace API are generally aligned with the Microsoft Graph API limits:

Per-Minute Limit: Up to 60 requests per minute

However, during testing the integration, I’ve noticed that my data is not being ingested within that specified timeframe and not aligning to the specified rate limit.

Can someone please confirm if there are any additional limitations or conditions that might cause the rate limit to vary? Are there any other factors, such as throttling or specific request patterns, that could affect the rate limit during data ingestion?
Your guidance on this would be greatly appreciated as it would help me optimize the integration process.

​I am currently working on the integration of the Message Trace API and wanted to clarify some details regarding the rate limit. The REST API I am currently using for O365 Message Trace for my integration is: https://reports.office365.com/ecp/reportingwebservice/reporting.svc/MessageTrace[?ODATA options]  As mentioned previously,The rate limits for the O365 Message Trace API are generally aligned with the Microsoft Graph API limits:Per-Minute Limit: Up to 60 requests per minuteHowever, during testing the integration, I’ve noticed that my data is not being ingested within that specified timeframe and not aligning to the specified rate limit.Can someone please confirm if there are any additional limitations or conditions that might cause the rate limit to vary? Are there any other factors, such as throttling or specific request patterns, that could affect the rate limit during data ingestion?Your guidance on this would be greatly appreciated as it would help me optimize the integration process.  Read More

​