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.

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.

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.

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).

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).

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.

Developers are looking for the ability to add data to the Graph.

Developers are looking for a single unified M365 dev platform roadmap. There's M365 service roadmap however it only partially covers dev platform needs.

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.

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.

Are there supported microsoft graph APIs for using journalling i.e. create/edit/delete journal rules, adding journal mailbox etc.?

If not, can we consider including the APIs?

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.

It 's slow when I want to post an createUploadSession requests, usually around 2s, most cost at TTFB(time to first byte), so do other endpoints, they are so slow.

Since we can already grab the subscribed skus through the API can we extend the existing endpoint to return cost per license. That would be wonderful.

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

There already exists an endpoint to add domains to Microsoft 365 (https://docs.microsoft.com/en-us/graph/api/domain-update?view=graph-rest-1.0&tabs=http) and you can retrieve some of the DNS records associated with that domain, but you cannot currently add records to a domain hosted by Microsoft.

Example use case: Provide a website hosting offering and let users login with their Microsoft 365 account (with admin privileges) so that I can set the A or CNAME record to point to the corresponding website.

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