What can Microsoft Copilot really see? Permissions, oversharing and a practical SME check

An employee asks Copilot for the key terms of a supplier agreement. Seconds later, an old contract note appears from a forgotten Teams channel. Copilot did not bypass a security control. The employee already had access; she simply did not know it.

This is the central misunderstanding around Microsoft Copilot. AI does not automatically gain access to the entire tenant. It operates in the signed-in person's context and honours existing permissions. At the same time, it makes scattered information easier to find, summarise and connect. An access right that was historically too broad is not newly created, but suddenly becomes much easier to use.

For Swiss SMEs, this is not an argument against Copilot. It is an argument for treating permissions as a business issue. Before buying licences, organisations should understand which Teams, SharePoint sites and files are actually visible to whom.

Microsoft describes the boundary clearly. Through Microsoft Graph, Copilot can use emails, chats, calendars and documents for which the signed-in person has at least view permission. It has no blanket tenant-wide view. Existing security, compliance and privacy policies continue to apply, including Conditional Access and MFA.

That is a strong foundation, but it does not guarantee that your permissions are sensible. If a site includes “Everyone except external users”, a former project team was never cleaned up, or a file was directly shared with many people, those people are already authorised. Copilot cannot recognise a technically valid permission as an organisational mistake.

Copilot is not a master key. It is a very fast assistant for every door for which a person already holds a key.

Microsoft also states that prompts, responses and Microsoft Graph data are not used to train the underlying foundation models. Interactions are stored in Copilot activity history and can be subject to the organisation's retention and discovery controls in Microsoft Purview.

Microsoft: Data, Privacy, and Security for Microsoft Copilot · Microsoft: Copilot architecture and how it works

Security, privacy, permissions and data quality are often mixed together. Separating them produces better decisions.

A file can be well protected but outdated. It can be current but exposed to too broad a group. It can be absent from search while a user can still open it through a direct link. No single switch answers all four questions.

Oversharing does not always mean a document is public on the internet. More often it is an internal site open to the whole organisation, a project team with former members, inherited folder permissions or a link that outlives the collaboration.

Before Copilot, some of this remained unnoticed because nobody knew what to search for. Natural-language questions can be broader: “Which margins did we discuss last year?” or “Summarise the risks in our contract drafts.” If the underlying content is accessible, the answer can connect information spread across several locations.

The risk is not that Copilot invents access. It comes from combining existing access with easier discovery and a readable summary. A technical feature test is therefore not enough preparation for a rollout.

Select a test user from sales, project management or administration and ask three business-relevant questions about price lists, HR templates or contract conditions. Inspect every cited source. Does it belong in this person's working context? Is it current? Was access granted through team membership, a SharePoint group, a direct link or an organisation-wide group?

Do not use deliberately sensitive live data. The purpose is not to provoke Copilot into crossing a boundary. It is to see whether everyday access reflects business reality.

When an unexpected file appears, do not blindly remove the first visible link. Determine the effective access path. Otherwise, group membership may continue to provide access. Record the owner, purpose and next review date. A finding then improves a rule rather than creating a one-off cleanup.

Microsoft points to Data Access Governance in SharePoint Advanced Management for analysing broad exposure. Reports can identify sites with many users, external guests or “Everyone except external users” access. Activity reports cover recently created sharing links over the previous 28 days. Availability and detail depend on licensing; owning a Microsoft 365 subscription does not include every capability automatically.

Sensitivity labels and Microsoft Purview can add protection and governance. They do not decide which information is confidential, who needs it or which version is authoritative. Technology cannot reliably repair unclear ownership.

Restricted SharePoint Search was intended as a temporary constraint. Microsoft blocked new enablement from 31 July 2026 and now points customers to Restricted Content Discovery and broader controls. Crucially, the retired feature was never a security boundary and did not change permissions.

Microsoft: Data access governance reports · Microsoft: Restricted SharePoint Search

Week 1: create visibility. Choose ten important sites covering management, finance, HR, sales and two active projects. Record owners, member groups, external guests and broad sharing. Prioritise by information value and reach.

Week 2: make business decisions. Ask accountable owners who genuinely needs the content. Separate internal working material from customer or partner versions. Give every site a named owner for changes and future reviews.

Week 3: correct and test. Remove obsolete memberships and direct sharing. Test with suitable accounts that intended access still works and unintended access has ended. Review Copilot answers and citations as well as the SharePoint interface.

Week 4: define operations. Make onboarding, role changes, project closure and departure explicit triggers. Agree a manageable review rhythm. Sensitive or broadly accessible areas deserve more frequent checks.

This is a ZUMENTIQ recommendation, not a Microsoft product standard. A small organisation can begin with a good list and clear owners, then automate where scale and risk justify it.

The first is blocking Copilot without improving underlying permissions. The same files remain reachable through search, links and direct navigation.

The second is testing only with IT. Administrators understand systems but may not know the business meaning of every document. Business owners must judge whether information is intended, current and appropriate.

The third is a rushed mass cleanup. Removing broad groups without assessing consequences can break important processes. Understand reach and dependencies, correct access with an accountable owner, and verify the result.

Microsoft Copilot respects the signed-in user's permissions. That is the key technical fact. The organisational consequence matters more for implementation: existing access becomes easier to use, connections become visible, and outdated content can be summarised convincingly.

Do not begin with “Is Copilot secure?” Ask whether employee access is correct, understandable and still necessary. Review ten relevant sites, establish ownership and test real work questions. That produces more confidence than a blanket approval or prohibition.