Not Pulling in all Shifts when I query

Question

Is there a known issue with the Team's Shift data coming out of Microsoft Graph? When I run the following query;

https://graph.microsoft.com/v1.0/teams/{teamid}/schedule/shifts

I get results, however I noticed that all shifts from 2 scheduling groups are not in the results. I did confirm that the 2 scheduling groups are resulting when I query

https://graph.microsoft.com/v1.0/teams/{teamid}/schedule/schedulingGroups

Is there something else that I should be doing to ensure we are getting all shifts that are present in our Microsofts Team's Schedule?

Answer 1

Hi Oliver, Andrea,

I recreated this scenario in my environment and successfully retrieved all the shifts for both scheduling groups. Please verify if the shifts that are missing in the response from the /schedule/shifts endpoint are open shifts; if so, those shifts are retrieved by a different endpoint, /schedule/openshifts.

Please ensure to provide Schedule.Read.All permission to access this resource.

Please refer attached screenshot for reference:

1. Shifts screenshot showing 1 Open shift and 6 user shifts:
2. Graph API to fetch all user shifts for all scheduling groups:

1.

Graph API call to fetch open shifts

For details, please refer below:

https://learn.microsoft.com/en-us/graph/api/resources/openshift?view=graph-rest-1.0

https://learn.microsoft.com/en-us/graph/api/resources/shift?view=graph-rest-1.0

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

Answer 2

Thank you @Rohit Raghuwanshi - MSFT for taking the time to look into this and providing such a detailed response. We figured out that there is a limit of records the query allows for before there is a @odata.nextLink option. For our query, it seemed to be 2717 records.

Once we clicked that link, it brought us to a new query with additional records. That continued until we got all of our records.

I hope this response helps others that may run into the same issues.