05 September 2026

OneDrive agents: personal knowledge, shared risk

Agents in OneDrive (469503) and OneDrive files as agent knowledge sources (480728) — launched. Learn limits, labels, and Steady controls before you scale.

microsoftcopilotonedriveagentsroadmap

DIGITAL SKILL WORKS LTD / 12 PANES

OneDrive agents: personal knowledge, shared risk

Editorial illustration: nested OneDrive folders with a red agent node

Illustration: Paper/Ink header (AI-assisted). DIGITAL SKILL WORKS LTD / 12 PANES.

Personal files become agent grounding. That is useful — and it is where Steady either holds or breaks. Two launched roadmap items make the pattern explicit.

What shipped / what’s on the roadmap

OneDrive: Agents in OneDrive (MRC 469503) — status Launched. Build, use, and share agents using files and content in OneDrive (Web). Requires a Microsoft Copilot for Microsoft 365 licence. MRC lists preview September 2025 and GA November 2025 — confirm live.

OneDrive files as knowledge sources for agents (MRC 480728) — status Launched. Allow OneDrive files as grounding sources in the Sources tab when creating a custom agent, including agents created from OneDrive and SharePoint. GA listed October 2025 on the item.

What Learn says

Add knowledge sources to your declarative agent documents SharePoint and OneDrive limits: up to 100 SharePoint files, one SharePoint list, and up to 50 OneDrive files per agent. Agents respect existing permissions and sensitivity labels on content already in SharePoint or OneDrive. Restricted SharePoint Search blocks SharePoint as a knowledge source. File readiness can lag uploads by minutes. Sharing an agent does not automatically grant SharePoint site access — site administrators still grant site permissions.

Why you should care (12 Panes)

Board. Personal agent sprawl without owners is a governance failure waiting for an audit.

CISO. Same Graph permissions model — no new magic access — but shared agents amplify mistakes in who can open which file.

CFO. Licence and pay-as-you-go paths for agents need budgets before “everyone builds one”.

Adoption. Teach Sources hygiene: curated folders, not whole drives; label before share.

Panes. 04 Security · 05 GRC · 06 Cost & Value · 09 Work & Skills · 12 Frontier (for early personal agents).

Diagram

Diagram: OneDrive files to build/share agent to Sources tab to permissions and labels

Diagram: 12 Panes / tldraw — board “12 Panes — Blog Diagrams”.

Suggested action

  1. Add OneDrive agents to the AI/agent register with a named owner per shared agent.
  2. Publish a Sources standard: prefer labelled libraries; cap personal OD grounding to known folders.
  3. Align with SharePoint restricted content discovery for sites that must not ground agents.
  4. Pilot sharing only inside a Steady cohort; measure support tickets and overshare findings.

Communication needed

Security + GRC: register and DPIA triggers. Adoption: how to build a bounded agent. FinOps: licence vs pay-as-you-go. Comms: personal agents are still organisational risk when shared.

Benefits and risks

Benefits. Faster personal workflows grounded in files people already own. Reusable Sources pattern across OneDrive and SharePoint.

Risks. Sharing agents without fixing file ACLs. Embedding sensitive personal stores. Exceeding practical grounding quality with noisy folders.

Sources

Back to blog