Why most Microsoft Graph features are limited only by user access

Question

Authentication of a service or daemon for Microsoft Graph provides access to a limited number of functions.

For example, to be able to work with the Scheduler and tasks, you must log in as a user. In another case, we cannot access most user information, we cannot access user files, etc.

Why should a service or daemon have more permissions now? In our case, the service should automatically create Scheduler tasks and calendar events for specific users or groups in accordance with automatically registered events. Sometimes he also needs to create or add or read files on this user's OneDrive. Also automatically, of course. Due to the limitations of Microsoft Graph, it’s easier to use an additional third-party service to track tasks or even to write your own. The same situation with files.

Microsoft Graph looks like a powerful API, but due to access restrictions it becomes unusable when you need to do something automatically, without any user action.

What is the reason for most of these restrictions? Are there any passages?

Answer 1

Office 365 works great with deamon apps, but not in your use case. This works great for changing a user's calendar, for example. See here https://docs.microsoft.com/en-us/graph/api/user-post-events?view=graph-graph-1.0&tabs=cs

Also, if you want to change something in the API chart. The best way to tell Microsoft this is to create an item on UserVoice. This allows users to influence what features they need, perhaps you can express your wishes there. https://microsoftgraph.uservoice.com/forums/920506-microsoft-graph-feature-requests