How to organize SharePoint and OneDrive so Claude can actually find your documents

Every organization I talk to about Claude deployment hits the same wall around week three.

The initial setup goes smoothly. IT enables the M365 Connector, somebody with Global Admin rights approves the permissions in Entra ID, and the team starts asking Claude questions about their documents. Then the complaints start. “It cannot find the Q3 report.” “It gave me last year’s version.” “It says it does not have access to the file I am looking at right now.”

The problem is not Claude. The problem is not the connector. The problem is that your SharePoint site was built for humans who know which folder to click, and AI does not click folders.

How the M365 Connector actually works

The M365 Connector for Claude is available on Team and Enterprise plans. It connects through Microsoft Graph API with delegated permissions, meaning Claude sees exactly what each user can see. Nothing more. No admin backdoor, no special access. Read-only across SharePoint, OneDrive, Outlook, and Teams.

A Global Admin in your Entra ID tenant needs to approve the connection once. After that, individual users authorize their own access. The permissions are scoped to the user, not the organization. This is important because it means your existing SharePoint permissions structure determines what Claude can and cannot retrieve.

Here is where the architecture matters. When Claude searches for a document through the connector, it is not opening folders and browsing file lists the way you do. It is querying Microsoft Graph, which returns results based on metadata, search indexing, and content signals. If your documents have no metadata, inconsistent naming, and live eight folders deep in a hierarchy that only makes sense to the person who created it, the query returns noise. Or nothing.

Metadata-first document architecture

The single most impactful change you can make is shifting from folder-based organization to metadata-based organization. Microsoft’s own SharePoint best practices documentation recommends this anyway, but most organizations never make the switch because folders feel familiar.

Flat document libraries with rich metadata columns outperform deep folder structures for both human and AI access. The practical ceiling is roughly ten columns per library before management overhead exceeds the benefit. Start with these five:

Department is the column that replaces your top-level folder structure. Instead of Finance/Reports/Q3/2025/, you have a single Reports library with a Department column set to Finance.

Document Type replaces the second level of folders. Report, Policy, Template, SOP, Contract, Proposal. Pick categories that match how people actually ask for documents, not how your filing system evolved over the years.

Status matters more than most teams realize. Draft, Active, Archived, Superseded. Without this column, Claude has no way to distinguish your current operating procedures from the version you abandoned two years ago. It will happily surface the old one if it matches the query better.

Last Verified Date is the column nobody thinks to add until they realize their AI assistant is citing a compliance document from 2019. Set a review cadence. Update this field when someone confirms the document is still current.

AI-Ready is a yes/no flag you set after confirming a document meets the formatting requirements for AI consumption. More on those requirements below.

SharePoint autofill columns can handle some of this automatically. The feature uses AI to extract metadata from document content and populate columns without manual tagging. It works well for straightforward document types. For anything requiring judgment, human review still matters.

Preparing documents Claude can actually read

Not every document format works equally well for AI processing. A 200-page scanned PDF with no OCR layer is effectively invisible. An image-heavy PowerPoint with no alt text is mostly blank to an AI reading it.

Keep files under 65 pages. This is not a hard technical limit, but processing quality drops noticeably beyond that length. If you have longer documents, split them into logical sections. Your 150-page employee handbook becomes five focused documents that Claude can actually work with.

Naming conventions matter because they affect search ranking. A file called Final_v3_FINAL_updated_NEW.docx tells Claude nothing about its content. A file called Finance-Quarterly-Report-Q3.docx tells it everything. Adopt a consistent pattern across your organization and enforce it through library validation rules.

Clean formatting helps significantly. Documents with clear headings, consistent styles, and structured content process better than documents with ad-hoc formatting. Tables with headers parse better than tables without. Lists with consistent structure are more retrievable than freeform prose.

Scanned PDFs need an OCR layer. SharePoint’s built-in search already handles this for indexing purposes, but the quality varies. For critical documents, run them through a dedicated OCR tool before uploading. The extra step pays for itself every time Claude correctly retrieves a finding from a scanned contract instead of missing it entirely.

Setting up OneDrive sync for Cowork

Claude Cowork operates differently from the M365 Connector. Where the connector queries your cloud documents through Graph API, Cowork runs autonomous multi-step tasks that can search the web, execute code, and work with files. It is available on Pro, Max, Team, and Enterprise plans, and currently runs on macOS and Windows x64.

For Cowork to work with your organizational documents, those documents need to be accessible on the local machine. This is where OneDrive sync becomes critical infrastructure rather than a convenience feature.

Create a centralized folder structure that gets synced to every relevant user’s machine through OneDrive:

A shared Templates folder contains your standard document templates, report formats, and reusable frameworks. When someone asks Cowork to draft a quarterly report, it pulls the current template automatically.

A Reference Docs folder holds your organizational knowledge base. SOPs, product specs, competitive analysis, anything that informs ongoing work. Keep this curated. A reference folder with 500 unorganized files is worse than no reference folder at all.

A Prompts folder stores your tested, validated prompts for common tasks. This is the piece most organizations skip. Building a shared prompt library that your team actually uses turns tribal knowledge into organizational capability.

A Team Outputs folder is where Cowork deposits its work product. Having a consistent location makes it easy to review, share, and build on AI-generated work.

The OneDrive sync client keeps these folders current across machines without manual effort. Set up the shared library sync once, and every user on the team has the same reference material available locally for Cowork to access.

MCP connectors for deeper integration

The M365 Connector handles the common case. For organizations that need deeper or more customized integration with SharePoint, MCP (Model Context Protocol) servers provide a more flexible path.

Anthropic ships several built-in connectors for enterprise environments, and the open-source community has produced additional MCP servers specifically for SharePoint and OneDrive access. These can query SharePoint list data, pull document metadata, and provide structured access to content that the standard connector does not surface.

Enterprise deployment of MCP servers uses .mcpb bundle distribution through your MDM platform. Three control tiers govern what runs on managed endpoints: admin-pushed servers via managed-mcp.json, allowlist and denylist policies for user-installed servers, and desktop extension controls. This layered approach lets IT provide useful integrations while maintaining security boundaries.

The practical use case for custom MCP beyond the standard connector is usually one of two things. Either you need access to SharePoint list data (not just documents), or you need to enforce specific retrieval patterns that match your organization’s information architecture. A custom MCP server can query your metadata columns directly, filter by your AI-Ready flag, and return only current, verified documents.

If your team is already thinking about data privacy implementation for AI tools, MCP governance fits neatly into that framework. Same approval process, same security review, same audit trail expectations.

The Microsoft Copilot Cowork convergence

Microsoft recently announced their E7 Frontier Worker Suite at roughly a hundred dollars per user per month, launching in May. The product is called Copilot Cowork, and it uses Anthropic Claude for reasoning within the Microsoft 365 environment.

This is significant for document organization because it means the structure decisions you make now will serve double duty. Organizations that get their SharePoint metadata, naming conventions, and document formatting right for Claude’s M365 Connector are simultaneously preparing for Copilot Cowork’s cloud-based document access. The underlying retrieval mechanics are similar: metadata-driven queries through Microsoft Graph, not folder browsing.

Copilot Cowork runs entirely in your M365 tenant, handles multi-step long-running tasks, and can access your organizational data natively. Unlike Claude’s Cowork which operates on local files, Microsoft’s implementation is cloud-first. Both benefit from the same document preparation: clean metadata, consistent naming, manageable file sizes, and structured content.

Organizations that restructure their SharePoint now, before the May launch, will be positioned to use both tools effectively from day one. Organizations that wait will hit the same wall twice.

Worth discussing for your situation? Reach out.