SharePoint Team Knowledge Base: What to Do Before November 1

TL;DR: Microsoft has introduced a team knowledge base in SharePoint: a library of interlinked pages that Copilot builds from the emails, meetings, chats and files a team chooses, so people and agents work from the same context. It is rolling out now in Frontier preview, only for users enabled for usage-based billing, and it spends Copilot Credits. Two governance details matter most. Anyone who can read a knowledge base can see what was added to it, even if they cannot open the original source, and pages only change when someone asks Copilot to update them. Separately, the preview PowerShell controls that decide where Copilot in SharePoint runs stop being honored on November 1, 2026. Settle your site controls and spending policies first, then pilot with one team.

Every team has the same quiet problem. The decision was made in a meeting, the reasoning lives in an email thread, and the latest version of the plan sits in someone's OneDrive. People who have been around for a while can connect those pieces. New hires cannot, and neither can agents.

Microsoft's answer, announced on October 14, 2026, is a team knowledge base that Copilot curates inside SharePoint. It is a useful step, and it arrives with a date attached: November 1, 2026, about two weeks away. That is when Microsoft stops honoring the preview PowerShell settings that many tenants used to keep Copilot in SharePoint on or off for specific sites. Copilot in SharePoint is the main place people create knowledge bases, so the site controls you set before then decide where your teams can start building one.

What is the SharePoint team knowledge base?

A team knowledge base is a special library you add to an existing SharePoint site, including sites behind Teams channels and Microsoft 365 Groups. It holds interlinked, agent-friendly markdown pages that Copilot creates with Work IQ's knowledge compilation engine. Team members choose what goes in (email, messages, meetings and files on their SharePoint sites), and Copilot organizes it by topic. People read the pages, and agents working with the team use them as a starting point instead of digging through raw files.

Microsoft's examples are practical: a legal team gathering knowledge from emails, files and notes to support contract work, an engineering team giving coding agents project history, and a sales team keeping account history in one place. For the bigger picture on why shared context matters, read The New Role of the Knowledge Base in SharePoint.

What is changing with the SharePoint knowledge base?

The details below come from Microsoft's announcement, Introducing a team knowledge base, curated by Copilot and agents, on the Microsoft SharePoint Blog, along with Microsoft's current product guidance.

The knowledge base also builds on Work IQ, the layer that gives Copilot and agents context from across Microsoft 365. If that term is new to your leadership team, Work IQ Is Redefining How We Work in 2026 is a good primer.

Why does the SharePoint knowledge base matter for IT leaders?

• It changes who can see what. Microsoft's guidance is clear that anyone with access to a knowledge base can see content added to it, including people who cannot open the source. A citation or link does not grant access to the source either. A summary of a confidential email thread, added to a site the whole department can read, is now readable by the whole department.
• It adds a new line of AI spend. The knowledge base is advanced work in SharePoint, so it consumes Copilot Credits through usage-based billing. Copilot asks people to approve credit use before it starts, and typing /cost shows what a task used. In enterprise tenants, nothing runs until an admin creates a spending policy, and spending policies can pick up new services automatically unless you turn that setting off.
• Trust has to be maintained. Pages update only when someone asks. Source changes do not flow through on their own, removing a source does not remove what was taken from it, and during preview a Copilot update can reverse edits people made. Microsoft's health check finds broken links and missing references, but it does not verify accuracy. Every knowledge base needs a named owner.
• Agents get faster and cheaper to run. In Microsoft's early internal testing, agent responses were up to 4x faster and 30% more token-efficient when they worked from a knowledge base. Treat that as a direction, not a forecast for your content, and measure your own results.
• Where Copilot runs is about to change. After November 1, 2026, availability of Copilot in SharePoint is managed with Site AI settings and Restricted Content Discovery instead of the preview PowerShell lists. If you relied on those lists to keep Copilot off sensitive sites, you need a replacement now. Our guide to the Restricted SharePoint Search retirement explains how Restricted Content Discovery works.

Some sectors have extra decisions to make:

• Nonprofits often give staff and volunteers broad access to program, donor and client sites so work moves quickly. Because a knowledge base exposes what is added to everyone who can read it, start with a low-risk area such as grant writing or volunteer onboarding, and keep donor and client case details out until site access is tightened.
• Education institutions hold student records, accommodations and staff files across many departmental sites, and student workers often have site access. Pilot with a service desk or admissions FAQ team, and agree up front that student-identifiable information does not go into a knowledge base.
• Government tenants in GCC, GCC High and DoD do not currently support Copilot in SharePoint, so the knowledge base is not available there yet. Use the time to define ownership and content rules. Public sector organizations on commercial cloud should treat knowledge base pages as new records that may fall under records management and access-to-information obligations.

What should IT leaders do before November 1, 2026?

1. Replace the preview PowerShell controls. Check whether your tenant uses KnowledgeAgentScope and a selected sites list. Map every site you excluded to Restricted Content Discovery or to Site AI settings before November 1, so sensitive sites stay out of Copilot in SharePoint on your terms.
2. Decide who gets usage-based billing. In the Microsoft 365 admin center, go to Copilot, then Cost management. Scope a spending policy for Advanced work in SharePoint to a security group of pilot users, set monthly limits and alerts, and review whether existing policies automatically include new services. Microsoft recommends prioritizing content managers and site managers, not every user.
3. Pick one team and one set of questions. Choose a team with a recurring context problem, such as onboarding, a key account or a service desk. Write down the five to ten questions the knowledge base should answer. A small, trusted knowledge base beats a large one full of conflicting guidance.
4. Clean up the site before you add a knowledge base to it. Confirm the site has an active owner, remove access for "Everyone except external users" where it is not needed, and check sensitivity labels. Mitigate Oversharing and Govern Microsoft 365 Copilot walks through the controls to use.
5. Set content rules and a named owner. Agree what can be added, what must stay in the source system, who approves Copilot's proposed changes and how often pages are reviewed. Remember that each update is a request, so put a review rhythm on the calendar.
6. Decide which agents read and which contribute. Microsoft is adding knowledge bases to Cowork, Copilot in Teams and custom agents built in Copilot Studio. Before that happens, agree which agents may only read a knowledge base and which may add to it. If your teams are unsure which Copilot experience to use for what, start with Copilot Chat vs Cowork vs Code vs Autopilot.
7. Measure before you scale. Capture a baseline now for time to answer common questions, onboarding time and agent answer quality, then compare after 30 and 60 days. Expand to a second team only when the first one shows results.

A knowledge base also works well alongside repeatable AI tasks in SharePoint. SharePoint Skills Explained shows how teams turn recurring work into reusable workflows that can draw on the same curated context.

How do you tie knowledge base spend to measurable value?

The knowledge base is one of the first SharePoint capabilities where cost depends on use. That is a good thing if you can see the value side clearly. Microsoft's own billing terms may change before general availability, so build the habit of measuring now, while the pilot is small.

A simple monthly view is enough to start:

• Cost: Copilot Credits used by the pilot group, from Cost management in the admin center and /cost in Copilot
• Time: minutes to answer the five to ten questions the knowledge base was built for, before and after
• Quality: agent answers checked against approved guidance, and the number of corrections owners make each month
• Onboarding: days until a new team member can work without asking for background
• Decision: expand limits where value clearly exceeds cost, fix content where quality lags and retire knowledge bases nobody uses

For example, if a 12-person team saves 45 minutes each per week because decisions, context and current guidance are in one reviewed place, that is about 39 hours a month. Set that against the credits the team spent and the decision to expand, adjust or stop becomes straightforward. Beyond 'Active Users': The Copilot Adoption Metrics That Actually Prove Value covers how to capture the value side, and Microsoft 365 Copilot Licensing Changes: December 2026 Guide explains how usage-based billing fits into your wider Copilot budget.

What do IT leaders ask about the SharePoint knowledge base?

Who can use the SharePoint team knowledge base today?

It is rolling out to Frontier preview tenants. Users need a Microsoft 365 Copilot license and must be enabled for usage-based billing through a spending policy in the Microsoft 365 admin center. Microsoft notes that billing terms may change before general availability.

Does the knowledge base respect SharePoint permissions?

Copilot only uses sources the contributor can access, but the pages it creates are visible to everyone who can read the knowledge base. Content added from a restricted source can be seen by people who cannot open that source, so check who can read the site before adding anything sensitive.

Does the knowledge base update itself when files change?

Not today. Pages update only when someone asks Copilot to update them. Microsoft lists automated, ongoing curation with Copilot Studio agent flows as a roadmap item.

What changes on November 1, 2026?

Microsoft stops honoring the preview PowerShell settings used to switch Copilot in SharePoint on or off for tenants and sites. From then on, use Site AI settings and Restricted Content Discovery to manage where Copilot in SharePoint, and so the knowledge base experience, appears.

How can 2toLead help?

2toLead works with small and mid-market organizations across healthcare, nonprofit, education, financial services, professional services, government and manufacturing on Copilot readiness, SharePoint governance and adoption. For the SharePoint knowledge base, we can help you:

• Move off the preview PowerShell controls and set Site AI settings and Restricted Content Discovery before November 1
• Configure Copilot Credit spending policies, limits and a monthly review routine
• Choose a pilot team, clean up its site permissions and set content rules and ownership
• Build a scorecard that ties credit spend to time saved, onboarding speed and agent quality

For more on Copilot, SharePoint and governance, browse the 2toLead Insights hub. When you are ready, book a knowledge base readiness review with our team and start your pilot on solid ground.

No hype. Just practical, governed AI that actually gets adopted.