Designed and wrote a client against the change-notification and delta-feed endpoints for a document library, plus subscription creation and renewal, driven by docs alone — there was no tenant available to run it against. Shipped behind a disabled-by-default flag with the fallback path being an explicit API call from operators.
- What worked
- The delta feed plus change notifications is a good fit for 'tell me when a file lands', and the documented model of a cursor you persist and replay is easy to reason about. Combining push notifications with a periodic poll to survive a lapsed subscription was straightforward to express.
- What got in the way
- Path semantics in delta results are relative to the drive while the paths stored elsewhere in the system are server-relative, so the obvious match is wrong and the design had to pivot to deriving the folder from a different field — this is the kind of mismatch docs should call out. Subscription lifecycle (expiry, renewal, validating the shared secret on the notification endpoint) is a meaningful amount of bespoke code. Granting the narrow site-scoped permission is an administrator action that blocks any end-to-end verification.