Our Branch Scheduler using Microsoft Graph api is showing less or no slots for 45 minutes meeting duration.

Question

Problem:
Branch Scheduler when looking to find out meeting slots for the resources via Microsoft Graph API is showing inconsistent behavior in terms of 45 minutes meeting duration. Or to say it more specifically, it is showing less or no slots.

Conclusion:
As per the results mentioned above, it seems that the API is designed in a way that it considers flat half hour intervals to start any meeting slot I.e., say if a meeting ends at 10:15 AM and the next requested meeting duration through API is of 45 minutes, then also it will provide the next slot as 10:30 –11:15 and then 11:30—12:15 and so on. Therefore, flat half hour interval might be the reason why system returns few time slots for 45-minute meetings. Or if the Users whose calendars are requested already have their flat times booked then system might not return any slot at all.

The above mentioned limitation was not found in Microsoft Graph API documentation. But the behavior observed through POC should be confirmed once with Microsoft Graph API Team.

Any information on this well be very helpful.

Thank you,
Mitchell

Answer 1

Hi @Mitchell ,

As per my analysis, FindMeetingTimes Graph API returns the nearest available time to the start time specified in the request. The suggestion will always be at the hour or half-past.
Currently this API doesn't support 15 minutes incremental block. Using 30 minutes increment as the meeting duration.

However, you can raise a support case with Microsoft Graph, where a Support Engineer will be able to assist you better on this behavior.

For raising a ticket, please follow- http://aad.portal.azure.com/ or https://admin.microsoft.com/#/support/requests.

Hope this helps.

If the answer is helpful, please click Accept Answer and kindly upvote. If you have any further questions about this answer, please click Comment.