Is Graph Api getStaffAvailability endpoint supposed to be this slow?

Question

Hey there! I have a registered app in my Azure Ad with its API permissions set to allow read and write to Microsoft Bookings. I use "bookingsBusiness: getStaffAvailability" in order to build a time table with slot times for a booking module. When testing this in my private Azure Ad portal, where I had set up 2-3 staff members, the response from Graph Api was almost instant.

Now, when setting this up in a larger organization with hundreds of employess registered in their AD, the response from "bookingsBusiness: getStaffAvailability" is 21 seconds. This seems like an awful long time to get a response.

Is this really performing the way it should? Can having more employees in an organizations AD have this much of an impact on the "bookingsBusiness: getStaffAvailability"-request?

Answer 1

Hello @Robin Hansson

How many staff ids are you passing to the request? In general more staff ID's would equal a longer time. If still only passing 2/3 at a time their could be issue. In which case I would recommend you raise a support case with Microsoft Graph, a Support Engineer will be able to assist you better. You can raise support ticket from http://aad.portal.azure.com/ or https://admin.microsoft.com/#/support/requests.

Other thing to take into account is if doing lots of requests one after another you could be getting throttling in this case looking at the following best practices might help.

Russell

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