HEBook a call
Book a callHE
Blog

5 practical steps to secure Microsoft 365 Copilot

8 November 2026 · Shlomi Fanan

Microsoft 365 Copilot doesn't break any permission. It just finds, in seconds, every file a user can already open, including the ones nobody remembers sharing. That's why securing Copilot starts with permissions and data, and only then with Copilot's own settings.

We worked with a large financial organization on its Copilot rollout: we configured the controls and then ran a penetration test to see what was actually blocked. Here are the five steps, in the order we'd do them.

Step 1: Who uses Copilot, and from where

Step 2: Fix oversharing before Copilot finds it

Copilot answers from whatever the user can access. A SharePoint site accidentally shared with "everyone in the organization" becomes an answer any employee can get.

Step 3: Sensitivity labels and DLP for Copilot

Step 4: Close the side doors

Step 5: Retain, review and monitor

You don't have to finish all five steps before you start. Begin with a pilot group and steps 1 and 2, then expand. We do all of this in our Copilot security service, as part of our Microsoft 365 security projects.

Can Copilot see files I don't have access to?

No. It only works with what the user can already open. The problem is that in many organizations users can open far more than anyone thinks.

Does Microsoft use our data to train its models?

According to Microsoft, Microsoft 365 Copilot prompts, responses and data aren't used to train the models. Feedback a user sends is a separate channel, which is why we turn it off.

Should we wait with Copilot until everything is in place?

No. Start with a small group and the access controls, fix oversharing on the sensitive sites, then expand.

Want to roll out Copilot without exposing data? We'll check what Copilot would see in your environment before you roll it out.

Talk to us

Sources