Microsoft Graph API: Transition from $skip to $skiptoken – Unresolved Interaction with $filter and $orderby

Goal

Retrieve a large collection (e.g., /me/messages) while applying a filter and sorting, using the new $skiptoken pagination mechanism.

Constraints

The API has deprecated $skip in favor of $skiptoken. Current documentation does not clarify whether $filter or $orderby are preserved across pages when a $skiptoken is used, and preliminary tests suggest inconsistent behavior.

Unresolved Questions

• Does $skiptoken maintain the $filter applied on the initial request across all subsequent pages?
• When $orderby is combined with $skiptoken, is the sorting order guaranteed to be consistent across paginated results?
• Is there an official recommendation or documented limitation for using $skiptoken with complex filters or ordering on collection endpoints?