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

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Graph Webhooks - include the changed data in the response

    Trying out Webhooks on the Graph beta enpoint for /users and I am missing
    information about what data was changed

    Nowhere to be found is what attributes of the user were changed (i my case "Last name"). This makes the triggers totally unusable for "/users" and I cant really think of anyone who could use this function as is? Sure I know the object was changed but I have no idea WHAT happened and if the change was relevant to my function
    Please tell me there are plans to include the actual changes i the trigger response

    7 votes
    Sign in
    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. Expose Office API via Swagger.

    OK this is a radical idea from listening to @mkristensen talk about VS.NET tooling and how they are looking at supporting Swagger 2.0 to provide code generation for RESTful APIs in VSNET.

    I looked up Swagger and their online documentation editor, and browser and here's an example!/pet/updatePet

    Which is surprisingly similar to Office 365's

    I think Office 365 documentation on MSDN should still be the primary resource. Any future tie in to API-Sandbox would be awesome.

    But if VSNET starts to support auto-codegen (like the old days with WSDL/Soap Services) from Swagger documentation, then I can also…

    19 votes
    Sign in
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base