Graph API findmeetingtimes caps the result at 50 records

The behavior you're experiencing with the findMeetingTimes endpoint in the Graph API, where it caps the result at 50 records despite setting the maxCandidates to 600, may be due to changes in the API or its underlying logic. It's important to note that the API can have limitations on the number of suggestions it returns based on various factors, including the availability of attendees and the constraints set in the request.

If you are consistently receiving only 50 records, it may be worth checking the following:

1. API Changes: Review the changelog for any recent updates or changes to the API that might affect the response.
2. Parameters: Ensure that all parameters are correctly set and that there are no other constraints limiting the results.
3. Testing Environment: If you are in a testing environment, the results may differ due to static calendar data.

If the issue persists, consider reaching out to Microsoft support or checking community forums for any similar reports from other users.

References:

• Find-MgUserMeetingTime
• Find-MgBetaUserMeetingTime

MS Support confirmed the findmeetingTimes API is now limited to max 50 records in the result payload. The purpose is to improve the performance.

In the past, we did one API call and retrieved the availability of users for the entire week. Now we have to break it up to 7 different calls. Surprisingly, the performance didn't get much hit. It may actually be faster.