How to Stop Copilot from Exposing Sensitive Internal Files

Copilot does not create leaks, it exposes them

If a junior employee asks Microsoft Copilot to summarise the company's financial performance from last quarter, what happens?

If your Microsoft 365 environment is configured like most small and medium businesses, Copilot might pull numbers directly from an unencrypted spreadsheet containing executive salaries, director loans, and redundancy plans.

This is not a software bug. Copilot did not hack your system. It simply found a file that someone saved into a SharePoint folder set to "Anyone inside the organisation can view."

Copilot uses the Microsoft Graph to search across everything a specific user has permission to read. In theory, this is secure: a user cannot see files they do not have access to. In practice, almost every business with 10 to 250 staff has an permissions mess behind the scenes. Folders are shared loosely, old project sites remain open, and links sent three years ago still grant tenant-wide access to confidential documents.

Before Copilot, this was manageable because human beings rarely went hunting through thousands of obscure SharePoint folders. The risk was hidden by obscurity. Copilot eliminates obscurity. It indexes everything, surfaces answers in seconds, and does not pause to consider whether an employee ought to be reading the source material.

If you want to adopt Copilot safely, you must fix your underlying file access. Here is the concrete process for doing that.

The three permission traps common to growing businesses

Most permission issues in Microsoft 365 do not stem from complex IT failures. They stem from convenience. When staff need to collaborate quickly, they take the path of least resistance. Over several years, this creates three predictable weak spots.

• "Anyone with the link" internal sharing. When an employee shares a document in OneDrive or SharePoint, the default option in many tenants is "People in your organisation with the link". Over time, staff generate hundreds of these links. Every file shared this way becomes visible to Copilot searches across your entire workforce.
• Orphaned and abandoned SharePoint sites. When a company runs a project, merges an entity, or conducts an internal review, someone often spins up a dedicated SharePoint site or Microsoft Team. When the project finishes, the site is forgotten. If that site was created as "Public" inside the business, every document inside it remains indexed and searchable.
• Payroll and HR files in standard shared drives. It is remarkably common to find HR folders, disciplinary records, or board packs sitting in general document libraries where permissions were manually adjusted years ago. Inherited permissions often break during folder reorganisations, quietly opening restricted folders back up to the wider team.

If you roll out Copilot across your business without addressing these three areas, confidential data will eventually appear in a chat prompt.

Immediate containment: Restricted SharePoint Search

If you are rolling out Copilot immediately or have already purchased licenses, you need a way to reduce risk while you audit your files. Microsoft recently introduced a feature specifically for this dilemma: Restricted SharePoint Search.

Restricted SharePoint Search allows administrators to turn off tenant-wide indexing for Copilot. Instead of scanning every single SharePoint site across your business, Copilot is restricted to searching only an approved list of up to 100 SharePoint sites, plus each user's personal OneDrive and recent interactions.

This gives business leaders breathing room. You can exclude sites that contain sensitive historical data, financial archives, or general clutter, and point Copilot exclusively to clean, vetted sites (such as your staff handbook, marketing collateral, and active operational libraries).

Restricted SharePoint Search is not a permanent substitute for proper data governance, but it is an effective safety brake. It allows you to deliver Copilot to staff without worrying that a loose file from 2021 will suddenly surface in an all-staff meeting.

A pragmatic approach to sensitivity labels

Once the immediate risk is contained, the real work is classification. Large enterprises spend months building complex governance models. A business with 50 or 150 staff does not need that level of bureaucracy; it needs a simple, enforceable policy using Microsoft Purview sensitivity labels.

Do not create ten different labels. Your team will not use them, and your IT provider will struggle to manage them. Instead, establish four clear tiers:

• Public: Information intended for the public domain (marketing sheets, published white papers).
• General: Everyday internal work that carries no commercial risk if seen by any staff member (templates, office guides, public company announcements).
• Confidential: Business information that should be limited to internal staff only, with no external sharing allowed (project workflows, operational metrics, client proposals).
• Restricted: Sensitive files that must be locked down to specific groups or named individuals (payroll, executive compensation, M&A activity, disciplinary records, legal correspondence).

The critical step for Copilot governance is the "Restricted" label. In Microsoft Purview, you can configure this label to apply encryption. When a file is encrypted and limited strictly to the management team or HR, Copilot cannot read, index, or summarise that file for anyone outside that specific group. Even if a user asks directly about the document by name, Copilot will return nothing.

Conduct an over-sharing audit before giving out licenses

Do not delegate Copilot security entirely to your external managed service provider (MSP) and assume it is handled. Your MSP understands technical configuration, but they do not know which contracts, clients, or internal matters are sensitive. That judgment belongs to business leadership.

Run a targeted audit using the following steps:

• Review your SharePoint tenant sharing defaults. Change the default sharing link from "People in your organisation" to "Specific people". This forces staff to consciously choose who gets access to a file rather than defaulting to company-wide visibility.
• Audit your public Microsoft 365 Groups. Run a report showing every Team and SharePoint site configured as "Public". Any site that touches finance, client billing, senior management discussions, or strategy should be converted to "Private" immediately.
• Run an access review on critical libraries. Identify the five folders in your business where the most sensitive data lives: HR, Finance, Executive, Legal, and Strategic Projects. Have the relevant department heads look at the active permissions list and remove any groups labelled "Everyone", "All Users", or legacy distribution lists.

Next steps

Copilot is an exceptional productivity tool, but it rewards tidy systems and punishes sloppy ones. Turning off Copilot out of fear is a mistake that leaves productivity gains on the table. Rolling it out blindly is an unforced operational risk.

Start by running a permissions audit on your top five most sensitive folders this week. If you have already deployed Copilot licenses, consider enabling Restricted SharePoint Search while you get your file permissions and sensitivity labels in order. A few days of clean-up now will save your business from an embarrassing, and entirely avoidable, internal leak.