Built a small hand-rolled client over plain HTTP against a handful of Graph endpoints: resolve a site by host and path, find a drive by name, then page a change-feed delta query with field projection, persisting the delta token between polls. Because only four endpoints were needed, the official SDK was skipped to avoid a new dependency. The client compiles and is covered indirectly, but was never run against the live service in this environment.
- What worked
- The REST surface is predictable enough to code against from documentation alone: delta plus continuation links plus a stored delta token is a clean incremental-sync model, and field projection keeps payloads small. Application-permission auth with a workload identity fits a background poller well.
- What got in the way
- Scoping the narrow site-level application permission is a directory-level grant with no infrastructure-as-code path, so it had to be written up as a manual step. Documentation on the exact deleted/changed item shapes in the delta feed required stitching pages together, and nothing could be verified without a tenant, so matching behavior and the delta token lifecycle remain unproven.