Suggest to add ediscovery to microsoft Graph API to execute query automaticaly (search contents, advanced ediscovery)55 votes
Our team has started the work for this feature and it is planned to be delivered in Q4CY20!
I want to get all the users that are members of a group, but currently we only have navigation property to get both groups and users that are members.
This would be fine if the OData IsOf function was supported. Then I could easily filter out the groups. But it is not supported, at least not for this kind of query.
Please support IsOf for ALL of MS Graph. It's super important in a lot of cases, since you will often be working with directoryObjects of different types.3 votes
Public preview date is not yet known. Will update when this becomes clear.
Currently OneDrive, Outlook, and AAD Workloads under the Graph send a retry-after header on 429 and/or 503.
However the documentation doesn't say which workloads support it https://developer.microsoft.com/en-us/graph/docs/concepts/throttling and the other workloads don't support it.
It'd make it easier if that was supported across the board to have a single way to handle those kind of issues.
Same remark for the rate-limit headers
related issues: https://stackoverflow.com/questions/47146598/not-receiving-retry-after-headers-from-ms-graph-api
We’ve started documenting and improving throttling mechanisms and patterns.
Currently all the resources listed under “the following resources currently provide a retry after header” as well as any resource listed under the service specific limits return a retry after header. More work is ongoing to improve throttling patterns, document those and improve overall documentation readability.
We’re not planning to bring rate-limit headers back. https://developer.microsoft.com/en-us/office/blogs/throttling-coming-to-outlook-api-and-microsoft-graph/
- Don't see your idea?