On 14 October 2026, Microsoft announced the rollout of a team knowledge base in SharePoint to Frontier preview tenants. Copilot can turn selected material into linked Markdown pages for people and agents. For a small team, this is an opportunity to assess how to organise working instructions without accidentally widening their audience.
Who can access it
This is a staged preview rollout. Autopilot integration requires separate access, granted on its own rollout schedule. Continuous automated curation through Copilot Studio agent flows remains on the roadmap. Billing terms may change before general availability.
Microsoft’s documentation distinguishes the tasks: Copilot creation, updates and health checks consume Copilot Credits; Copilot answers based on KB pages require a Microsoft 365 Copilot licence. Manual creation and editing require neither that licence nor credits, but do require appropriate permissions.
Advanced work in Copilot in SharePoint requires enabled usage-based billing. Administrators can control users, services and spending through policies in the Microsoft 365 admin center. Review existing policies too: automatic inclusion of new services may already be enabled.
A copy has its own audience
According to the documentation, KB pages do not inherit source-file permissions or sensitivity labels; file-level labels are not supported on KB pages themselves. Someone with knowledge-base access can read incorporated content even if they cannot open the original. This concerns the new KB content, rather than removing restrictions on the source document.
Try one team instruction first
The following is an editorial evaluation plan, not a Nadali test result.
- Choose one non-confidential process, such as preparing a weekly internal report. Keep client records and personal information outside the pilot
- Check the new content’s audience with the site owner. For each document, record its owner, current version and approval to reuse it for those readers. Our data-boundaries guide can help frame the rules
- Compare each working step in the generated pages with its source. Check exceptions, links and questions the documents cannot answer. Do not let the model invent a missing rule
- Name the person who approves the content and triggers a review when an instruction changes. Separately record credits consumed, review time and corrections
KB pages do not update automatically when sources change. Microsoft warns that removing a source does not remove guidance already taken from it, and a knowledge-base health check does not verify factual accuracy. Review the pages themselves after changes. Automated structural checks do not replace human approval.
Nadali has not tested the preview in a working environment. Product information comes from Microsoft’s announcement and documentation; time savings or accuracy for small businesses have not been established here.
Prepared by the NADALI editorial team using AI
Sources checked on 15 October 2026. Announcement published on 14 October 2026.
