Office 365 API - Subscription
Hi, We have been using the Office 365 API to send events to our SIEM for a number of months. Since Monday we have received the following error: AF20023","message":"The subscription was disabled I've looked at "https://learn.microsoft.com/en-us/office/office-365-management-api/troubleshooting-the-office-365-management-activity-api#enable-unified-audit-logging-in-office-365" but even if I try and start a subscription, it will still return that it is disabled? Not entirely sure what else I can check.
Which APIs are the best for my outlook software
Hey community, I want to build a software that would automatically process incoming emails (using an LLM) from an outlook inbox and perform tasks, like forwarding the email to another inbox, or enriching the email body text with data from a CRM. The software should be easy to integrate into new organisations, so I was looking at building an outlook extensions.But i could not find any triggers that would work on any incoming email. I've looked at the Microsoft documentation for autolaunch add-ins: https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/autolaunch But I have seen that I could create a email subscription with the microsoft REST API https://learn.microsoft.com/en-us/graph/api/subscription-post-subscriptions?view=graph-rest-1.0&tabs=http#request I also discovered this blog post that revolved around a similar problem https://techcommunity.microsoft.com/discussions/microsoft-365/trigger-api-from-received-email/3906340 The suggested solution includes using microsoft power automate, but I would like my solution to work without any additional subscriptions. So my question is, what are the best API's to develop my software. It should be easy to install it on every machine of employees of a client company (like installing the outlook add-on) and analyse the content of the email automatically to then perform some actions, like adding text to the body of an email. Thanks for any advice in advance :)
'$skiptoken' limit error for Microsoft Exchange online Reporting web service API
I was working on integrating MessageTrace report API as a part of my SIEM integration: https://reports.office365.com/ecp/reportingwebservice/reporting.svc/MessageTrace[?ODATA options] I have noticed that, whenever my $skiptoken reaches the limit 999999 , it throws the following error with 500 status code: { "odata.error": { "code": "UnknownError", "message": { "lang": "", "value": "An error has occurred on the server." } } } It was working fine for the 999998 value, but wasn't for the $skiptoken value 999999. Is there any limitations on $skiptoken value from the API itself? Also, need information, if $skiptoken value 999999 exists, for example, "odata.nextLink": "../../reportingwebservice/reporting.svc/MessageTrace?$filter=StartDate%20eq%20DateTime'2024-12-02T00%3A00%3A00Z'%20and%20EndDate%20eq%20DateTime'2024-12-02T23%3A59%3A59Z'&$skiptoken=999999" then how can we request the data from next set of events? Can someone let me know, is there any max limit from Microsoft API side or for the $skiptoken?Is Warehouse management APIs are available in business central?
Hi Team, I have use case like to enter goods item level and need to store it in business central.Like i need to do like to create purchase order from invoice document and do inventory put Away through API .Create PO API is there.Please guide me to get inventory put-away API? Thanks, ArdraOutlook imap issue
While configuring IMAP, We are getting below errors attached in the screenshots. The PHP INI file has "IMAP" enabled. Our passwords are correct. Error Message: (E_WARNINGJ Authentication failed for user imap_open(): Couldn't open stream {outlook.office365.com/imap/551/nova1idate-cert}Clarification on Rate Limit for Message Trace API Integration
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.Data Retention information for Microsoft O365 Message Trace
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] While exploring the API, I found that the API is returning the data from past 10days to the max. Exceeding this, it is giving me server error with 500 response code. Is there is any possible way to obtain the data more than this range, as mentioned that the data retention is 30 days according to: https://learn.microsoft.com/en-us/previous-versions/office/developer/o365-enterprise-developers/jj984335(v=office.15)#data-granularity-persistence-and-availabilityNeed Information on Rate Limits and Data Retention for Microsoft O365 Message Trace
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] Can someone help me in knowing the rate limit of this API? Is the rate limit is different for account level and user level? Please let me know those limits if anyone is aware of it. While exploring the API, I found that the API is returning the data from past 10days to the max. Exceeding this, it is giving me server error with 500 response code. Is there is any possible way to obtain the data more than this range, as mentioned that the data retention is 30 days according to: https://learn.microsoft.com/en-us/previous-versions/office/developer/o365-enterprise-developers/jj984335(v=office.15)#data-granularity-persistence-and-availabilityRequest for Information on Rate Limits, Pagination, and Data Generation for Microsoft Message Trace
I am implementing an Integration with Microsoft O365 Reporting API and wanted some support regarding the Microsoft Message Trace API, specifically concerning the following aspects: Rate Limits: Can someone please provide detailed information on the current rate limits applicable to the Message Trace API? Understanding these limits is crucial for optimizing our API usage and ensuring we stay within the allowed thresholds. Pagination Approach: I would appreciate guidance on the recommended pagination approach when querying the API. Specifically, we'd like to know how to handle large datasets efficiently and whether there are best practices or built-in mechanisms for managing pagination in API responses. I am able to hit the API and hence, getting some response but unable to retrieve the Next page or any similar parameter which will allow me navigate to the next page. Generating Additional Data for Reporting: Lastly, I am exploring ways to generate more comprehensive data through the API for reporting purposes. Could anyone advise on any available options or techniques to retrieve a broader range of data points or more detailed logs from the API? Retention Policy: would like to know about the Retention policy of this API. Let me know if it varies from account level permissions/access? Someone's assistance is greatly appreciated, as it will help me ensure that the integration with Message Trace API is both efficient and compliant with best practices. Reference links: https://learn.microsoft.com/en-us/previous-versions/office/developer/o365-enterprise-developers/jj984335%28v%3doffice.15%29 API Link: https://reports.office365.com/ecp/reportingwebservice/reporting.svc/MessageTrace[?ODATA%20options] Thank you in advance for your support.
