A team and its agents will read from the same knowledge base, and Copilot keeps it current. On 14 October 2026, Microsoft introduced a team knowledge base on the SharePoint blog that Microsoft Copilot and agents build, extend and maintain in a SharePoint site. It is available now in the Frontier preview.
What Microsoft announced
Every team knows the starting point: knowledge sits in emails, chats, meeting notes and files, and much of it is half out of date. An agent that has to answer from this finds the right version one time and the wrong one the next.
The new knowledge base addresses exactly that. Team members deliberately add content, such as an email, a chat thread, a meeting or files from the sites they work with. Copilot condenses this into a continuously updated knowledge base that people can read and agents use to ground their answers.
Technically, the knowledge base is a dedicated library in a SharePoint site with interlinked Markdown files. Copilot creates it with Work IQ's knowledge processing. In its own tests, Microsoft measured answers up to four times faster and around 30 percent fewer tokens when an agent reads from the knowledge base. These figures come from Microsoft's internal testing in October 2026 and are no guarantee for your tenant.
Microsoft gives three examples from its work with frontier teams:
- Legal: knowledge from emails, files and personal notes comes together so agents have the right context when drafting agreements.
- Engineering: specifications, user feedback, market research and product history give coding agents project context and help new team members get started.
- Sales: knowledge and history for each account sit ready, so a sales agent can suggest next steps or deliver an account snapshot in seconds.
What is available today
- Frontier preview: a knowledge base can be added to any SharePoint site, including the sites behind Teams channels and Microsoft 365 groups.
- Building and curating: with Copilot in SharePoint, now generally available, and with Autopilot in the new Copilot app. Through Autopilot, the knowledge base can also be used from Teams or by email. Autopilot itself rolls out on its own schedule.
- Billing: for now, the knowledge base is only open to people enabled for usage-based billing. Admins manage access and spending in the Microsoft 365 admin center. Because this is a preview, terms may change before general availability.
What comes next
Microsoft's roadmap includes knowledge bases in more places of work, including Cowork, Copilot in Teams and custom agents from Copilot Studio. It also lists easier bootstrapping from the existing channels and emails of a Microsoft 365 group, ongoing curation with Copilot Studio agent flows, larger content volumes and connecting CLIs and coding agents through Work IQ.
In the same post, Microsoft sums up new tools for well-governed content: the SharePoint Admin Agent, which analyses permissions, lifecycle and storage in natural language, catalog management for large tenants, a file-level report on sharing with "Everyone except external users" and an overview of which agents access SharePoint and OneDrive.
Our view: knowledge built for agents
We have been building Company Brains for some time: a curated knowledge layer from which agents and people get the same answers. In our projects, agents answer far more reliably from prepared, verified knowledge than from a pile of files. Microsoft's knowledge base brings exactly this principle into the platform, and we welcome it.
For us, this fits AI-native work. We design workflows so that agents take part from the start, and we expect that over time one capable agent per person or team will win. That agent needs a knowledge base the team maintains itself, one that gets better with every meeting.
A knowledge base is only as good as what flows into it, though. If sites are shared too widely or three versions of the same policy sit side by side, Copilot condenses that disorder too. That is why data preparation for AI and governance belong before the first productive use.
What you can prepare now
- Pick a team with recurring questions: for example sales, support or a specialist department whose knowledge lives in emails and heads today.
- Define sources and ownership: which sites, channels and documents belong in it, and who decides what is valid?
- Clean up sharing: remove broad sharing and outdated versions before Copilot condenses them. Restricted Content Discovery keeps sensitive sites out of Copilot.
- Settle personal data: emails and meetings often contain personal data. Decide under the Swiss data protection act what may go into a knowledge base.
- Check preview and billing: is your tenant in the Frontier preview, and is there a usage-based billing policy with a budget?
We help you choose a first team, put the sources in order and set up the knowledge base so your agents answer from verified knowledge from day one.
