Microsoft Graph Feature Requests

Welcome to the Microsoft Graph UserVoice! Do you have an idea or feature suggestion based on your experience with Microsoft Graph? Please share these with us by submitting your idea below or voting up ideas submitted by other users. This forum will be directly monitored by the Microsoft Graph engineering teams who are working on new features every day.

If you have feedback on a specific API service, please choose the corresponding category. Please submit any broad ideas related to Microsoft Graph or ideas across more than one service to the “General” category.

This site is only for feature suggestions and ideas! If you need technical help, please go to the Microsoft Graph StackOverflow or if you have a Premier support contract raise a support ticket.

For more information on Microsoft Graph, please checkout https://graph.microsoft.com.


  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. add ediscovery on Microsoft Graph API

    Suggest to add ediscovery to microsoft Graph API to execute query automaticaly (search contents, advanced ediscovery)

    55 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  2. Support isof OData function for MS Graph

    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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  3. consistent retry-after information accross different workloads

    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
    https://github.com/microsoftgraph/msgraph-sdk-javascript/issues/42

    22 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    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.
    https://docs.microsoft.com/en-us/graph/throttling

    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?

Feedback and Knowledge Base