OneDrive integrations and automation

OneDrive is usually the place where files land rather than where work is tracked: scanned receipts, signed contracts, exported reports, photos from site visits. The automations people want are about what happens next. A new file in a folder should be renamed, copied to an archive, shared with a client, or have its details logged somewhere a team can search. Microsoft exposes all of this through Microsoft Graph, where every file and folder is a drive item with an ID, a parent, a name, size, timestamps and the account that last changed it.

There are two ways to notice changes. The delta query returns everything that changed in a folder or drive since a token you saved on the previous call, which suits a scheduled run: store the token, ask for changes, process them, store the new token. Graph also offers change notifications through subscriptions, but a OneDrive notification only says that something changed, not what, so the receiver still calls delta to find the actual files, and subscriptions expire and must be renewed. Either way, keep the item ID rather than the path, because a renamed or moved file keeps its ID.

Two gotchas catch people out. Personal OneDrive and OneDrive for Business are reached through the same API but with different accounts, and a business tenant's administrator may restrict which apps can be consented to, or block sharing links to people outside the organisation. And uploads above a modest size must go through an upload session that sends the file in pieces rather than in a single request. When sharing, Graph creates view or edit links with a scope such as anonymous or organisation; which scopes are permitted is decided by the tenant's policy, not by the workflow.

Whenever connects to OneDrive with your Microsoft account permission and calls Graph on your behalf. A scheduled delta check starts a run each time even when nothing changed, so pick an interval that matches how fast the files actually matter.