Combine multiple Microsoft Graph API calls into one HTTP round trip using JSON batching ($batch), including optional dependsOn ordering.

Documented steps

1. Send a single POST to https://graph.microsoft.com/v1.0/$batch (or the beta equivalent) with headers Accept: application/json and Content-Type: application/json.
2. Body is a JSON object with one required top-level property, "requests": an array of individual request objects — up to 20 individual requests per batch.
3. Each request object requires: id (a string unique within the batch, used to correlate responses; a duplicate id fails the whole batch with 400), method (the HTTP method), and url (the RELATIVE resource path, e.g. "/me/memberOf", not the absolute https://graph.microsoft.com/... URL).
4. Include a headers object whenever a body is supplied — it must then contain Content-Type, e.g. "headers": {"Content-Type": "application/json"}. Include body (JSON object, or base64 URL-encoded value for binary content) for writes.
5. To force ordering, add "dependsOn": ["<other-id>"] to a request — it runs only after that request completes. If a dependency fails, every request depending on it fails with status 424 (Failed Dependency). Design batches as either fully sequential or fully parallel, not mixed.
6. Parse the response {"responses": [...]}: each entry has id, status (the individual HTTP status code), headers, and body. Responses may arrive in a different order than sent — always correlate by id.
7. The outer batch response is typically 200 if the batch payload was parseable (400 if malformed) — a 200 outer status does NOT mean every inner request succeeded; check each inner status (e.g. 200, 403, 405, 424, 429).
8. Docs: https://learn.microsoft.com/en-us/graph/json-batching