channel: getAllMessages ignores $top query parameter

According to the official documentation, the $top query parameter is supported on the channel: getAllMessages endpoint to control the number of items per response:

"You can use the $top query parameter to control the number of items per response."

However, in practice $top is being completely ignored by the API. The server returns a fixed page size (appears to be ~10 messages) regardless of the value passed.

Steps to Reproduce

A team has 18 total messages across 3 channels for the date range. I make the following request:

GET https://graph.microsoft.com/v1.0/teams/{team-id}/channels/getAllMessages?$top=50&$filter=lastModifiedDateTime gt 2026-05-01T00:00:00Z and lastModifiedDateTime lt 2026-05-31T00:00:00Z
Authorization: Bearer {token}

Expected

A single response containing all 18 messages (since 18 < $top=50), with no @odata.nextLink.

Actual

The response contains only 10 messages and includes an @odata.nextLink, requiring 3 separate page requests to fetch all 18 messages:

{
  "@odata.count": 10,
  "@odata.nextLink": "https://graph.microsoft.com/v1.0/teams/{team-id}/channels/getAllMessages?$skiptoken=...",
  "value": [ /* 10 messages */ ]
}

Page split observed:

• Page 1: 10 messages
• Page 2: 7 messages
• Page 3: 1 message

Question

Is $top actually supported on this endpoint, or is the documentation incorrect? If it's a known limitation, the docs should be updated to reflect that the page size is server-controlled and $top has no effect.