Last updated: 18 November 2026
Copilot works with files a person can already open, so a folder that was shared too widely can be surfaced to people who should not see it. Review SharePoint permissions before you roll Copilot out. That is the core of Copilot readiness.
What does that look like in practice?
Picture a client contracts folder that was shared with the whole company years ago. Once Copilot is switched on, a new starter could ask it about those contracts and get an answer. Copilot did not break the rules. The permissions were already too loose.
What should we check before rollout?
- Sharing settings: sites and folders shared with everyone in the company, or with broad “anyone” links.
- Sensitive areas: HR, finance, client contracts and board papers should have named owners and tight access.
- Labels: use sensitivity labels where you can, and clear out old content nobody needs.
What did Microsoft announce?
Microsoft says Purview protections that stop Copilot referencing unlabelled sensitive files are in preview. These are still in preview, so they do not replace fixing permissions.
Where does this come from?
Microsoft’s Purview announcement is in the Microsoft Ignite 2026 Book of News. The permissions advice is ABCOM’s own. Our wider guide to the announcements is in What Microsoft Ignite 2026 means for Sussex businesses.
Questions about this? Book a free 20-minute call with the Burgess Hill team. We can work alongside your existing IT provider. Or call 01444 871 200.
Related questions
Want this sorted for you?
Talk to our Burgess Hill team about Microsoft 365 support. Free, friendly and no obligation.