Share via

Has Microsoft recently enforced a maximum $top limit of 30 for the Places API endpoint /places/{roomList}/microsoft.graph.roomList/rooms?

94179705 5 Reputation points
2026-02-05T10:13:36.96+00:00

Beginning the week of Feb 2–February 5, 2026, calls to the Microsoft Graph Places API endpoint /places/{roomList}/microsoft.graph.roomList/rooms started returning HTTP 400 with the message: ‘The limit of 30 for top query has been exceeded. The value from the incoming request is 1000.’ No code changes were made on our side.

Affected API: GET /v1.0/places/{roomListEmail}/microsoft.graph.roomList/rooms

We are observing a change in behavior for GET /v1.0/places/{roomListEmail}/microsoft.graph.roomList/rooms.

Previously, $top values up to 1000 were accepted. Currently, requests with $top > 30 return HTTP 400.

Can you please confirm if this is an intentional change and whether 30 is now the maximum supported $top value for this endpoint?
Is this a documented service change or a temporary limitation?

Are clients expected to rely on pagination via @odata.nextLink going forward?

Microsoft Security | Microsoft Graph
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-02-05T10:13:46.1466667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The information regarding the maximum $top limit for the Microsoft Graph Places API endpoint /places/{roomList}/microsoft.graph.roomList/rooms is not included in the provided context. Therefore, I cannot confirm whether the limit has been changed to 30 or if it is a temporary limitation. For the most accurate and up-to-date information, I recommend checking the official Microsoft Graph documentation or reaching out to Microsoft support directly.

    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.