Microsoft Graph API: Inconsistent `/me/drive/sharedWithMe` Behavior & Pagination Issue

Emiel 5 Reputation points
2025-11-17T09:24:53.0433333+00:00

During development with our Symfony 6.4 backend, we encountered an issue with the Microsoft Graph API's /me/drive/sharedWithMe endpoint. When querying this endpoint, the response consistently returned an incomplete list of shared items (e.g., only one item) and, critically, omitted the @odata.nextLink property. This prevented proper pagination and retrieval of all shared items.

This behavior was observed despite having sufficient permissions (Files.ReadWrite.All, Sites.ReadWrite.All) and a matching user identity (oid). The same request, when executed via the Microsoft Graph Explorer, yielded the expected complete results with the @odata.nextLink property present. This suggests a potential server-side inconsistency or bug within the Microsoft Graph API when accessed programmatically from our backend.

Backend: PHP 8.1, Symfony 6.4
API Endpoint: https://graph.microsoft.com/v1.0/me/drive/sharedWithMe
Permissions: Files.ReadWrite.All, Sites.ReadWrite.All

We would appreciate any insights or solutions regarding the inconsistent behavior of the /me/drive/sharedWithMe endpoint and the missing pagination link when accessed from a backend application.

Microsoft Security | Microsoft Graph
0 comments No comments
{count} vote

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.