OneDrive automations

Write operations on Microsoft Graph cost 2 Resource Units each, meaning a workflow uploading or organizing 100 files per minute burns 200 RUs per minute — and Microsoft doesn't warn you until you've already consumed 80% of your quota. When throttling hits, you receive an HTTP 429 with a Retry-After header, but the RateLimit headers themselves are returned on a best-efforts basis and may not appear at all. In practice, real-world accounts throttle 10–15% earlier than the documented ceiling, so any automation on Make, Zapier, or Pipedream that doesn't implement exponential backoff will start silently dropping tasks.

OneDrive for Business only allows webhook subscriptions to the root folder — you cannot subscribe to subfolders directly. If you try to monitor multiple folders by creating separate subscriptions, you'll find only one is valid, and all change notifications will reference the root without identifying which file or subfolder changed. Combined with the 30-day subscription expiry and documented renewal failures via HTTP 401 in early 2025, any unattended n8n or Pipedream workflow monitoring a shared team drive will eventually go silent without alerting — meaning file changes are missed, not queued.

OAuth access tokens for Microsoft Graph expire after exactly 3,600 seconds (1 hour), and refresh tokens can be silently revoked by Microsoft at any time due to admin policy or inactivity timeouts. A batch migration or large folder-sync job running on n8n, Power Automate, or Zapier that crosses the 1-hour mark mid-execution will hit an authentication failure mid-stream — and depending on the platform's error handling, partially processed files may not be retried, leaving your sync in an inconsistent state with no clear audit trail of what succeeded.