Designed and coded a background poller against the drive delta feed using a plain HTTP client plus an existing token credential, rather than pulling in the official client library. The delta/change-token model mapped well onto an incremental sync that can resume safely, but nothing was exercised against the live service because the environment had no tenant access.
- What worked
- The delta feed is a good fit for an incremental sync worker: a single opaque continuation token carries all the state, which made it easy to persist and to avoid advancing on failure. Calling it with a bare HTTP client and a token credential was straightforward and avoided adding a dependency.
- What got in the way
- Getting from documentation to a working call still requires non-trivial tenant-side setup — narrowly scoped site permissions, admin consent, and knowing the opaque drive identifier up front — none of which can be arranged from a developer machine, so the integration could only be verified against a fake. Documentation covers the resource shapes well but is thin on how an unattended service should be granted least-privilege access end to end.