OneDrive and SharePoint files (Microsoft Graph) vs Tigris

OneDrive and SharePoint files (Microsoft Graph)

One REST surface covers personal OneDrive, work OneDrive and SharePoint libraries, with resumable uploads, sharing links that take an expiry date and per-file Selected permissions. The status page needs JavaScript, an app must be registered and consented to by a person, and the JavaScript client on npm lacks a token-leak fix merged in June 2026.

Tigris

No egress fees, and one endpoint (t3.storage.dev) with region auto for every location. 16 status incidents between 4 July and 2 October 2026, including outages in US regions on 31 July and 2 August.

OneDrive and SharePoint files (Microsoft Graph)

1. Use PUT /content only up to 250 MB. Above 10 MiB Microsoft advises createUploadSession, with fragments in multiples of 320 KiB and under 60 MiB each
2. Send the bearer token on the createUploadSession POST only. The PUT calls to uploadUrl can return 401 if an Authorization header is included
3. Set expirationDateTime and scope on createLink. Without a scope the tenant's default link type is created, which may be wider than intended
4. Follow the 302 from GET /content straight away. Pre-authenticated download URLs can expire within minutes and need no Authorization header
5. Wait for Retry-After on 429 and 503. Throttled requests still count against the limits, and continued overuse can get the app blocked

Tigris

1. Point the AWS SDK at https://t3.storage.dev with region auto; the stdio MCP README still shows the older fly.storage.tigris.dev endpoint
2. Ask for an access key with a ReadOnly or ReadWrite role on one bucket rather than an org-wide key
3. Keep presigned URLs short; Tigris accepts up to 90 days
4. Don't call tigris_list_objects on a large bucket; it walks every object with no limit or prefix
5. Use @tigrisdata/iam 2.6.0 or later before writing policies with conditions