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

Add SignIn logs to Graph Rest API v1.0 -

"APIs under the /beta version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported."

We use Graph explorer to test Graph APIs, but it uses user+app authentication policy
But in order to check app-only authentication policies, we have to rely on PNP PS or POSTMAN Or other tool. It would be good if the Graph explorer has the capability to test all three auth methods(Deligate, Client-Cred, Certificate)?

Microsoft Graph abstracts out different services into the single set of APIs, but in practice some services may or may not be available for particular user or tenant.

For example, Azure AD accounts without Office 365 do not have access to /me/people API (Outlook REST API), this API returns 404.

Currently there's no way to determine what capabilities or APIs are available without trying to call the API and handling the error.

Knowing such information in advance would make it possible to build user experiences adaptive to what's available.

when running keyword searches, you sometimes also need to collect files that are not indexed in O365 to make sure you don't miss any potentially relevant files

or a minimum support searches allowed in Security and compliance center

Graph API allows for batch requests. I would like to have the option for requests that depend on each other. which means, request A provides input for request B. For example, get recent documents and get the embed link for them. This can only be done in more than one request because you need the ID of the items

Exchange RBAC and mailbox folder permission modification is not supported at the moment in Graph API.

However, adjusting these permissions is frequently used / required in many automation applications.

Also, they are one of the basic features in exchange.

I would suggest to build it as a part of Graph API.

When asking Graph to create objects the response should always be a 202 Accepted type response with an expected creation time or the object that is created. This way endpoints wouldn't have to be polled until the expected creation time is reached.

Organizational Contacts make it possible to share contacts via Tenant to Tenant. The only decent way to key off source tenant is via adding ExternalDirectoryObjectId to a custom attribute. Please consider adding this to the Graph API. Graph is phenomenal, however, the details really matter when collaborating T2T.

orgcontact #orgcontacts

You advertise that support is available on Stack Overflow, if the "microsoft-graph" keyword is used. But nobody answers questions posted there. If you want us to pay for support, fine, but do something!

I have two schema extensions with status "InDevelopment" changed to "Available" by mistake, so how can i delete them knowing that the maximum number of schema extensions per app is 5?

My preferred language of PowerShell is not listed on the tutorials page:
https://docs.microsoft.com/en-us/graph/tutorials.

Please add a tutorial for accessing Microsoft Graph via PowerShell.

In the current to-do tasks beta api there is the option to create new outlook tasks (https://docs.microsoft.com/en-us/graph/api/outlookuser-post-tasks?view=graph-rest-beta&tabs=cs) , but in order to delegate that task to someone else you need to go into outlook.

Please add the ability to delegate outlook tasks directly from the API. Having users go into outlook afterwards to delegate tasks crated through the API is not very user friendly.

add a python sdk, publish it on pypi and support it

Some Graph API requests can be quite large (e.g. sending mail with attachments). It would be great if the Graph API supported POST HTTP requests that are compressed (i.e. "Content-Encoding: gzip”).

The Gmail API currently supports this.

Please add IPv6 support for graph.microsoft.com

Calling the API from IPv6 only connections fails.