Allow daemons using Graph API client credential flow to create/edit/delete calendars/events/membership associated with a Group
The Microsoft Graph API is supposed to allow programmatic access to Office 365 features. We'd like to use it populate staff and student timetables, where each module being taught would appear as a separate Office 365 Group. To do this, we'd need a batch process (probably nightly) that could take information from our existing timetabling database and then use this to update the calendar associated with each group. As this would be done in the wee hours by a daemon process for all users in the University, it needs to use the client credentials OAuth2 flow (ie its allowed by the admins to access resources, rather than individual users granting rights).
Unfortunately, whilst the Graph API does have client credientials flow support, and I've got Perl code that uses it, it does not appear to support this OAuth2 flow when dealing with Office 365 Group calendars. The response to the query raised on Stack Overflow was that it is "on the roadmap" (http://stackoverflow.com/questions/34041517/create-groups-calendar-events-fails).
Without the ability for daemon processes to access Office 365 Groups without an individual user explicitly authorising them, we're sunk in our idea of using Office 365 Groups for timetables, which is a bit of a stumbling block from moving from Google Apps for Education for students where the calendaring APIs work fine. It also stops other backend scripts leveraging Office 365 Groups in similar ways, making Groups less attractive to us.