There should be some official endpoint created to programmatically check the health status of the Microsoft Graph API.

My application makes queries to the Graph API endpoint as part of the app's login process. I have built a health dashboard to notify me when external API's are having trouble. However, there is no specific Microsoft Graph endpoint that provides any status/health indicator for MS Graph API.

I appreciate your consideration.

Currently, CreateSession method for Excel only support the latest major version of a OneDrive file (Sharepoint file indeed): could it be possible to add support for SharePoint version of a file ?
We can get version of a DriveItem
https://docs.microsoft.com/fr-fr/graph/api/resources/driveitemversion?view=graph-rest-1.0
But not CreateSession on it
https://docs.microsoft.com/fr-fr/graph/api/workbook-createsession?view=graph-rest-1.0&tabs=http

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

If we have the graph API access token for 2 users. Then a feature to move a message(email) from user1's folder to user2's folder should be possible.

This capability is available with ecp mailflow rules.

At the moment, when you try to filter domains by any property (e.g. https://graph.microsoft.com/beta/domains?$filter=isVerified eq true) you will get an error:

{

"error": {

    "code": "Request_UnsupportedQuery",

    "message": "Filtered searches against this resource are not supported.",

    "innerError": {

        "date": "2020-11-17T11:21:44",

        "request-id": "693f8c34-ce3a-4368-83dd-a78a61f042a8",

        "client-request-id": "26f7abe5-563e-f45b-4d68-f19776f3fe0f"

    }

}

}

it would be useful to support filtering on this resource

I would prefer to have one single API for everthing we do with Office 365, so it would be nice to be able to use the PowerBI API with the capabilities the Graph API gives us.

Graph API endpoint for a users Flow Approvals.

Something like this:

List approvals: https://graph.microsoft.com/v1.0/me/approvals?$filter=flowname eq 'my flow'
Action an approval: https://graph.microsoft.com/v1.0/me/approvals/{approval-id}/approve|reject

This would allow users take action on approvals inside an application, lets say a MVC web app or SPFx web part.

Related post in Power Automate: https://powerusers.microsoft.com/t5/Power-Automate-Ideas/Use-Graph-API-to-list-and-take-action-on-approvals/idi-p/62143

Today i brought up this in Monthly community call, I was suggested to post in MS Graph forum as well. This change required MS Graph and Power Automate integration.

Currently the beta version Compliance endpoint targets only Advanced eDiscovery. We need the same support for Core eDiscovery.

The SharePoint online Graph API "https://graph.microsoft.com/v1.0/sites/" discovers all Sharepoint site Collections including personal sites(Onedrive sites). Does the above graph endpoint support filtering so that we can fetch only personal sites and its sub-sites.

Please enable the ability for users other than administrators to receive app request notifications, and also have the ability to approve / reject the request.

Having this ability only assigned to Global Administrators means only a small scope of people can do this. We should be able to assign this task to users with rights to only carry out this action.

Perhaps a the creation of a new Role -'App Request Manager'

Thanks

In advanced eDiscovery is no option to re-use tags / a tag structure in multiple cases. There is no export/import option like for review-set-queries. Adding AED tag management to Graph API would offer IT to help AED users e.g. copy tag structure or automatically create tags from pre-defined templates.

I'd like to get all people with at least one phone number. I've tried

https://graph.microsoft.com/v1.0/me/people?$filter=length(phones) gt 0
https://graph.microsoft.com/v1.0/me/people?$filter=phones/count gt 0
https://graph.microsoft.com/v1.0/me/people?$filter=phones/any(p:p ne 'notanumber')

but they all give "Invalid filter clause" (on beta too).

It seems a bit silly to have to set top=zillions and filter client-side when we have this seemingly advanced filtering language.

We are able to retrieve primary keys from a proprietary system with Schema Extention Values via Graph, but are not able to look up a matching O365 event using the same key. We need to be able to do this using the "$filter" syntax in Graph.

It is great to be able to convert files to PDF. It would be even better if you could specify the things that can be specified in Word (Client) when doing a "Save as PDF" such as PDF/A and tagged PDF (option "document structure tags" that leads to a PDF/A-1a or PDF/A-2a or PDF/A-3a in different versions of Word).

FindMeetingTimes is a delegated permission in app registrations. I understand that for the Me object. The user object should have an Application permission for ISV type of applications. https://graph.microsoft.com/v1.0/users/[user]/findMeetingTimes

Ability to get flows with their existing flow run history. It would be great to be able to add filters to the requests. This would allow us to build dashboards to monitor all the flows in the organisation / solution / etc. Currently we are getting mails of failures days after running but would like to get data to be able to monitor the flows more in-time.

Another useful option will be to get aggregated data for all types of runs (successful, failed, running, cancelled).

Yammer API has not changed since a while and is really bad.
Documentation is old and do not represent all the routes possible to query.
A lot of useful routes to query are not available.
Authentication possibilities are very limited, nothing to do with how it is done for Graph API.
For all these reasons it would be great to have Yammer API rewritten as part of the Graph API.