/sharepoint/. Unlike the single-drive OneDrive resource, it exposes the
full enterprise topology: many sites, each with many document libraries. Site
and drive names are resolved to Microsoft Graph ids automatically, so you mount
once and browse everything you have access to. All operations involve network
I/O to Microsoft Graph. Files are served as raw bytes (no Office filetype
conversion). Uses aiohttp for async Graph access.
For credential setup (tokens, app vs delegated auth, permissions), see the
SharePoint Setup guide.
Config
SharePointResource(config) takes a SharePointConfig object with a Microsoft
Graph bearer token. No drive id is required: the resource discovers sites and
drives for you. Both READ and WRITE modes are supported.
Config Reference
| Field | Required | Description |
|---|---|---|
access_token | Yes | Microsoft Graph OAuth2 bearer token (string or callable provider) |
tenant_host | No | Restrict resolution to a single SharePoint host |
site_filter | No | Search term passed to /sites?search= to narrow discovery |
timeout | No | Request timeout in seconds (default 30) |
max_retries | No | Max retries on 429/5xx with backoff (default 5) |
access_token accepts either a static string or a Callable[[], str] provider.
With a callable, the resource refreshes the token on 401, so long-running
mounts survive token expiry.
Filesystem Layout
SharePoint paths follow the structure/{site}/{library}/{path}. The first two
levels are virtual (sites and drives), and everything below is a real Graph
driveItem.
- Level 0 (
/sharepoint/): lists all accessible sites - Level 1 (
/sharepoint/{site}/): lists document libraries (drives) in that site - Level 2+ (
/sharepoint/{site}/{library}/...): lists files and folders
/sharepoint/Engineering/Documents/spec.md resolves the
site Engineering to a site id, the library Documents to a drive id, then
reads the driveItem at /root:/spec.md.
Versioning and Snapshots
SharePoint keeps per-file version history. The resource exposes it the same way the OneDrive and S3 backends do:- Fingerprint is the driveItem
cTag, so normal reads andstatreflect the current content without extra Graph calls. - Snapshots pin each path to a Graph driveItem version id. Replaying a
snapshot reads
/versions/{id}/content, giving time-travel to the exact bytes captured at snapshot time. - Restore writes a previous version back as the current one.
SUPPORTS_SNAPSHOT = True.
Cache
The SharePoint resource caches site, drive, and directory listings viaIndexCacheStore to reduce repeated Graph calls during traversal.
Example
examples/python/sharepoint/sharepoint.py (command
matrix) and examples/python/sharepoint/sharepoint_vfs.py (FUSE mount).
Shell Commands
The SharePoint resource supports the full set of shell commands since it operates on real file content (text, binary, JSON, CSV, etc.). Large files benefit from range reads to avoid downloading entire items.Read Commands
| Command | Notes |
|---|---|
cat | Read file content |
head / tail | First/last N lines |
grep / rg | Pattern search (file or directory level) |
jq | Query JSON fields |
wc | Line/word/byte counts |
stat | File metadata (name, size, type, modified) |
find | Recursive search with -name, -maxdepth |
tree | Directory tree view |
nl | Number lines |
du | Disk usage summary |
file | Detect file type |
strings | Extract printable strings from binary |
xxd | Hex dump |
md5 | MD5 checksum |
sha256sum | SHA-256 checksum |
File Operations
| Command | Notes |
|---|---|
cp | Copy files |
mv | Move/rename files |
rm | Remove files |
mkdir | Create directories |
touch | Create empty file or update timestamp |
tee | Write stdin to file and stdout |
Path Utilities
| Command | Notes |
|---|---|
basename | Strip directory from path |
dirname | Strip filename from path |
realpath | Resolve path |
ls | List directory contents |
Use Cases
- AI agents accessing org documents: Mount enterprise SharePoint for agents to read and process files across many sites
- Multi-site discovery: Browse every accessible site and library from a single mount, no drive ids to manage
- Versioned document workflows: Snapshot and replay exact file states over time
- FUSE mounting: Expose SharePoint through a virtual FUSE mount for external tools
SharePoint vs OneDrive
Both backends talk to Microsoft Graph driveItems and behave identically below the drive level. Choose by topology:- Use OneDrive for a single drive (personal
OneDrive, OneDrive for Business, or one targeted SharePoint library via
drive_id/site_id). - Use SharePoint for enterprise scenarios with many sites and libraries that you want to discover and traverse without knowing drive ids up front.