Summary

Enable OpenClaw to connect with Microsoft SharePoint as a document source, allowing agents to retrieve, search, and reference internal SharePoint files and libraries during conversations.

Problem to solve

Teams using OpenClaw for internal workflows cannot access documents stored in SharePoint. This forces users to manually copy content into conversations, breaking the automation pipeline. Agents lack access to internal knowledge bases, policies, and reports that live in Microsoft 365 — making them less useful for enterprise use cases where SharePoint is the primary document store.

Proposed solution

Add a SharePoint connector/tool that authenticates via Microsoft OAuth (Azure AD), allowing OpenClaw agents to browse SharePoint sites, fetch document contents, and use them as context. This would follow a similar pattern to existing integrations like Google Drive.

Alternatives considered

Manually copying SharePoint documents into the agent's context was explored, but this is inconsistent, error-prone, and not scalable for teams managing large document libraries. Hardcoding document content into system prompts is also impractical as files change frequently. A native SharePoint connector is the only sustainable solution.

Impact

Affected users/systems/channels: All enterprise users relying on Microsoft 365 and SharePoint as their primary document store, particularly finance, HR, and operations teams
Severity: Blocks workflow — agents cannot access internal knowledge without manual intervention
Frequency: Daily — every agent interaction that requires internal document context is affected
Consequence: Users are forced to manually paste document content, increasing time spent per query, introducing human error, and defeating the purpose of AI automation

Evidence/examples

Tools like LangChain and Microsoft Copilot already demonstrate SharePoint document retrieval as a viable pattern. A sample OAuth config for Sites.Read.All and Files.Read.All permissions can be provided. Screenshots of the current limitation — where the agent returns no results for internally stored policy documents — are available upon request.

Additional information

The integration must remain backward-compatible with existing OpenClaw connector configurations. It should support both delegated (user-based) and application-level permissions to accommodate different deployment scenarios. Ideally, site/drive scoping should be configurable per agent to limit data exposure.