Microsoft Graph -admin -exchange

A 200 response whose JSON ends prematurely is not a valid message-delta result, and reproducing it in Postman makes an application parser defect unlikely. Preserve the last complete delta state instead of advancing it. Capture the response headers and body, especially request-id, Date, and client-request-id. Retry the same failing request with Prefer: odata.maxpagesize=1 and a minimal $select such as id; if it succeeds, increase the page size or selected fields until the failure returns. Follow every returned @odata.nextLink or @odata.deltaLink exactly without editing its token. Test one affected and one unaffected folder and record the mailbox, folder ID, UTC time, and whether v1.0 and Graph Explorer reproduce the truncation. Check Microsoft 365 service health. There is no safe client-side way to parse incomplete JSON, so use bounded retries without advancing state, then open Microsoft support with the captured request identifiers and minimal reproduction if it persists.