Copilot Readiness · 6 min read

Is your SharePoint ready for AI agents?

James Wilkinson

By James Wilkinson 15 October 2026

Microsoft has announced that any SharePoint site can now have a knowledge base curated by Copilot and agents. Here is what it is, what it isn't yet and what you can do about your own content now.

TL;DR
  • On 14 October 2026 Microsoft announced a team knowledge base for SharePoint, curated by Copilot and agents. Any SharePoint site can have one.
  • It is in Frontier preview only, needs usage-based billing and doesn't yet work with custom Copilot Studio agents.
  • The most common reason an agent gives weak answers is the content behind it, not the model or the prompt.
  • The groundwork is the same whether or not this feature ships as described. Decide what's authoritative, archive the rest, fix versions and permissions and name an owner for each content area.

Microsoft has announced that any SharePoint site can now have a knowledge base curated by Copilot and agents. It’s in early preview and most firms won’t see it this year, but it points at the problem that decides whether an AI agent is useful or not: the content it reads.

Last week I was connecting a client’s full library of policies to a Copilot agent. Overlapping guidance, older versions sitting next to current ones, the same process written up three different ways. A good share of the work wasn’t building the agent. It was deciding what the agent should and shouldn’t be reading.

This announcement is Microsoft’s attempt to solve that at the platform level. Here’s what it is, what it isn’t yet and what you can do about your own content now.

In plain English

If you’re not technical, this is all you need to know.

An agent is an AI assistant you build to do one job, such as answering staff questions about your firm’s policies. It doesn’t know anything by itself. It reads your documents and answers from them.

The problem is that most firms’ documents are a mess. Old versions, duplicates, three ways of doing the same thing. The agent reads all of it and sometimes picks the wrong one.

Microsoft’s new feature has Copilot read through a team’s documents first and write a clean, organised summary of what the team actually knows, a bit like a well-kept internal wiki. Agents then read that summary instead of the raw files. Cleaner input, better answers.

It’s not available to most firms yet. But the preparation is something you can do today, and it’s at the bottom of this post.

A few terms you’ll see below:

TermWhat it means
GroundingPointing an agent at a set of documents so it answers from those, not from the open internet
Knowledge baseThe organised, curated set of pages the agent reads
MarkdownA simple text format that AI tools read easily. You don’t need to care about it
Copilot StudioMicrosoft’s tool for building custom agents. It’s what I use for client builds
Frontier previewMicrosoft’s early-access programme for experimental Copilot features
Usage-based billingPaying for AI features by how much you use them, rather than a flat licence per person

What Microsoft announced

On 14 October 2026 Microsoft announced a team knowledge base for SharePoint, curated by Copilot and agents. You can add one to any SharePoint site, which means any Microsoft 365 Group or Teams channel can have one too.

The idea is simple. Team members contribute content: emails, messages, meetings and files already on the site. Copilot then compiles that raw content into a library of interlinked markdown pages that both people and agents can read. Microsoft calls the engine behind this Work IQ’s knowledge compilation engine. The pages are kept up to date, and humans stay in the loop to curate them.

A few details from the announcement worth knowing:

  • Agents and Copilot in the new Copilot app, Teams and SharePoint can create, contribute to, curate and reference the knowledge base.
  • Microsoft’s internal testing found agent responses were up to 4x faster and 30% more token-efficient when grounded on the knowledge base rather than the original documents.
  • Microsoft positions this as SharePoint moving from a content store to the context layer for a team.

The examples Microsoft gives are legal teams pulling scattered knowledge together for drafting agreements, engineering teams giving coding agents project context and sales teams organising account history. Swap “legal” for “tax” or “audit” and the accountancy use case writes itself.

Why it matters: your agent is only as good as what it reads

The most common reason an agent gives weak answers isn’t the model or the prompt. It’s the content behind it.

When you point a Copilot Studio agent at a SharePoint library, it searches that library at question time and builds an answer from the chunks it finds. If the library holds three versions of the same engagement letter template, a 2021 technical memo next to the 2025 one and a policy that was superseded but never archived, the agent has no way of knowing which is current. It will sometimes pick the wrong one, and it will do so confidently.

On the policies job I mentioned, the fix was manual. We went through the library, worked out which documents were authoritative, moved the rest out of scope and gave the agent a narrower, cleaner set to read. That works, but it’s slow, it needs someone who knows the firm’s content and it starts to drift the moment someone uploads a new version to the wrong folder.

That’s the gap this knowledge base is designed to close. Rather than searching raw files, the agent navigates a curated, structured map of what the team knows, with the contradictions already resolved by Copilot and the people curating it. Microsoft’s claim of faster, cheaper answers is believable because it’s not doing anything clever. It’s just doing the tidying up front, once, rather than on every question.

The reality check

This is a preview, and a narrow one. Before anyone gets excited, here is where it stands as of 15 October 2026:

  • Frontier preview only. It’s rolling out to tenants in Microsoft’s Frontier programme, the early-access track for experimental Copilot features. If your firm isn’t opted in, you won’t see it.
  • Usage-based billing required. Microsoft says the knowledge base is currently only available to users enabled for usage-based billing, managed through the Microsoft 365 admin centre. A standard Microsoft 365 Copilot licence on its own isn’t enough, and Microsoft has said billing terms may change before general availability.
  • Autopilot is separate. Using the knowledge base from Teams or by email depends on Autopilot, which is rolling out on its own schedule.
  • Copilot Studio agents are on the roadmap, not in the preview. Microsoft lists custom Copilot Studio agents under “coming soon”, alongside Cowork, Copilot in Teams and automated curation through Copilot Studio agent flows. If you build agents in Copilot Studio, as I do for most clients, you can’t ground them on one of these knowledge bases yet.
  • The performance figures are Microsoft’s own. Up to 4x faster and 30% more token-efficient come from internal testing in October 2026. Treat them as a direction of travel, not a guarantee.

My honest read: most firms outside the Frontier programme won’t be using this in 2026. Preview features change, get renamed and occasionally disappear. But the direction is clear enough to act on now, because the preparation is the same whether this particular feature ships as described or not.

What to do now: is your SharePoint ready for agents?

Whether you’re planning your first agent or waiting for this knowledge base to reach general availability, the groundwork is the same. Every one of these is something I end up doing, or asking a client to do, before an agent goes live.

  1. Decide what’s authoritative. For each area an agent will cover, name the single current version of each key document: your engagement letter templates, your technical guidance, your onboarding process. If two documents disagree, one of them needs to go.
  2. Archive, don’t delete. Superseded policies, old year-end checklists and retired templates still have value for audit trails. Move them into a clearly named archive library the agent isn’t pointed at. Out of scope is the goal, not gone.
  3. Fix version control. If people save “Final_v3_JW_edits” alongside “Final”, the agent will read both. Use SharePoint’s built-in versioning on one file rather than copies, and make it the way the team works.
  4. Check permissions. An agent grounded on a site can surface anything a user already has access to on that site. If partner-only remuneration documents sit in the same library as the staff handbook because someone set it up that way in 2019, the agent will find them. Review who can see what before you connect anything.
  5. Give each site a purpose. One site holding everything the firm has ever produced is hard to ground an agent on. Sites that map to how the firm works (Tax, Audit, Practice Management, Client Onboarding) are far easier, and they’re exactly what a per-site knowledge base is built for.
  6. Name an owner for each content area. Microsoft’s knowledge base keeps humans in the loop for curation. That only works if someone is responsible. Pick one person per site to sign off what’s current. This matters more than any technical setting.
  7. Write down what the agent should not answer. Clients often skip this. An agent that confidently answers questions on areas where the firm’s guidance is thin or out of date is worse than one that says “ask a partner”. Decide the boundaries before you build.

None of this needs the new feature. It makes today’s SharePoint agents and Copilot Studio agents built in a Firmwide install work better immediately, and it means that when the curated knowledge base does reach your tenant, you’ll be switching it on rather than starting a clean-up project. For a fuller checklist on files and permissions, see SharePoint Copilot readiness: preparing your files, permissions and knowledge base.

Where this leaves you

SharePoint is becoming the context layer for your agents. Microsoft has said as much, and the knowledge base announcement is the first concrete piece of it. The firms that get their content in order now will be the ones getting real value when it lands, and they’ll get better results from the agents they can build today.

If you’re planning an agent, start with the call. Book a free Copilot Readiness Check. You leave knowing where Copilot can and cannot see your data, the two jobs to automate first and a rough install price.

Accurate as of 15 October 2026. The knowledge base is in preview and the details above, particularly licensing and billing, may change before general availability.

Sources

Related reading

More on Copilot Readiness

Copilot Readiness You've got Copilot licences. Why isn't it paying off? Most firms with Copilot licences get a few good moments and no change to anyone's week. Why that happens, what the licence already does and the five stages from there. Copilot Readiness SharePoint Copilot readiness: preparing your files, permissions and knowledge base SharePoint Copilot readiness is the foundation of safer AI. Fix permissions, content ownership and duplicates in the areas where Copilot will matter most. Copilot Readiness Microsoft Work IQ and Copilot context: why your Microsoft 365 data setup matters Microsoft Work IQ is the context layer behind Copilot and agents. Your Microsoft 365 data, permissions and content ownership now decide how useful AI can be. Copilot Agents Microsoft Copilot Autopilot explained: what Scout became and what a firm should sort first Microsoft has renamed Scout to Autopilot and moved it into the cloud with its own identity in your tenant. What an autopilot is, what it costs and the five things to sort before one arrives. The install Firmwide A fixed-price install, typically six to eight weeks: Copilot made safe and useful in your Microsoft 365, an agent and a skills pack for every department, handed over with training. Then Run keeps it working. Next step Book a Copilot Readiness Check Free, 30 minutes, online: where Copilot can and cannot see your data, the two jobs to automate first and a rough install price.

Common questions

Questions about the SharePoint knowledge base

What is the SharePoint knowledge base curated by Copilot?
A library of interlinked markdown pages that Copilot compiles from the emails, messages, meetings and files on a SharePoint site. People and agents can both read it, it is kept up to date and humans stay in the loop to curate it. Microsoft announced it on 14 October 2026.
Can I use the SharePoint knowledge base today?
Only if your tenant is in Microsoft's Frontier programme and your users are enabled for usage-based billing. A standard Microsoft 365 Copilot licence on its own isn't enough, and billing terms may change before general availability.
Does the knowledge base work with Copilot Studio agents?
Not yet. Microsoft lists custom Copilot Studio agents as coming soon, so you can't ground a Copilot Studio agent on one of these knowledge bases in the preview.