M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions→ m365con.net

Blog · Mirko Peters

How to explain Copilot data risk to executives in plain words

By · · Updated

How to explain Copilot data risk to executives: one clear message, a four-step briefing, a real example and the decision to ask for, in Microsoft's wording.

To explain Copilot data risk to executives, you need one honest sentence and a few facts they can check: Copilot shows people what they can already open, so the danger is access that was left too wide. This guide is for IT managers who have to brief a CIO, a CISO or a board without a technical lecture. You will see the message to lead with, a four-step briefing, what Microsoft states about data and permissions, the questions a security chief will ask, and what to ask for. A worked example with made-up numbers shows a one-page summary.

Key points

  • The core message for executives is that Microsoft 365 Copilot works within the access a person already has, so the risk is the access your organization has left too wide.
  • Microsoft says Copilot only surfaces organizational data to which a user has at least view permissions, and that overshared or poorly governed content can increase risk.
  • A good briefing has four steps: the question leaders already have, one concrete example, a number from your own tenant and a decision to ask for.
  • Avoid jargon such as semantic index or grounding, and use plain words like who can open this file today.
  • Separate what Microsoft promises, such as no training of foundation models on your data, from what your own settings must still fix.

What executives need to hear first

Leaders do not need to know how retrieval works. They need to know whether Copilot can leak something, and what you are asking them to do about it. The honest answer has two parts.

The first part is reassuring. The Microsoft Learn page on Microsoft 365 Copilot security says that Copilot operates within existing permissions and access controls and only accesses data that users are authorized to access. Microsoft's data, privacy and security page adds that Copilot only surfaces organizational data to which individual users have at least view permissions, and that prompts, responses and data accessed through Microsoft Graph are not used to train the foundation language models.

The second part is the uncomfortable one. The same security page says that overshared or poorly governed content can affect Copilot results and increase risk. In plain words: Copilot does not break your permissions, but it does make the consequences of loose permissions easier to see. A file that was technically open to everyone but practically hidden in a deep folder is now one question away. This is what oversharing means for a leader: not a new hole, but an old one with a bright light on it.

Generative AI also depends on the quality of the content it finds. Outdated drafts and duplicate files can weaken answers, so data governance matters for the quality of what the AI assistant says as well as for data security. For a leader, that turns a security worry into a business case: cleaner content means safer and better answers from Microsoft Copilot.

How to explain Copilot data risk to executives in four steps

Use four steps and keep the whole presentation to one page.

  1. Start with the question they already have. Most leaders ask some version of "could Copilot show our payroll to the wrong person?" Say it back to them, and answer it directly: it can show a person only what that person can already open. Then say the real risks sit where access is too broad.
  2. Give one concrete example. A single story beats a list of risks. Use an invented but realistic one, such as a salary spreadsheet in a team site that every employee can open, or a project folder shared with "everyone in the company" years ago.
  3. Give a number from your own tenant. Abstract warnings fade. Count something simple, such as sites shared with everyone, sites without a current owner, or files with company-wide links. Label the number as a first estimate if it is.
  4. Ask for one decision. Executives act on a request, not on a risk list. Ask for a sponsor, a budget for a cleanup, or a rule such as "no Copilot licenses for departments with unreviewed sites."

Keep the tone steady. Fear invites a ban, and a ban pushes people toward unapproved AI tools. A clear request for a bounded cleanup is easier to approve.

Words to use and words to avoid

Plain words keep the conversation on the decision. A few swaps help:

  • Say "who can open this file today" instead of "access control list."
  • Say "shared too widely" instead of "overly permissive sharing configuration."
  • Say "company-wide links" instead of "anyone-in-the-organization sharing links."
  • Say "AI assistant" the first time, and use the product name after that, because AI means different things to different listeners.
  • Say "sensitive data" for payroll, contracts, customer data and confidential plans, and give two examples from your own business.

Avoid terms such as grounding, semantic index and tenant boundary on the first page. If someone asks, answer in one sentence and offer a follow-up.

What Microsoft promises, and what stays with you

Executives often want a clean split between the vendor's job and their own. Microsoft's pages support this split, though you should read them yourself because details change.

What Microsoft states.

  • Copilot works within existing permissions and honors your organization's security and data protection controls.
  • Prompts and responses are processed and stored in line with contractual commitments for your other Microsoft 365 content, and stored data is encrypted.
  • When content is encrypted with Microsoft Purview Information Protection, Copilot honors the usage rights granted to the user.
  • Admins decide which agents are allowed.
  • Microsoft describes these contractual and technical commitments as enterprise data protection.
  • The privacy page describes processing locations in detail. For example, it says EU traffic stays within the EU Data Boundary while worldwide traffic can be sent to other regions for processing.

What stays with your organization. Microsoft Copilot sits on top of your own data security work, so access management and clear owners decide how much confidential data is exposed.

  • Who has access to which sites and files today.
  • Which content has a data classification, a label or encryption.
  • Whether site owners still exist and keep their membership current.
  • Which departments get the tool first.

The goal is a lower risk of data exposure and of data leakage, not a perfect tenant. Name the security risks you accept for now, so that sensitive information with the highest risk gets fixed first.

The blueprint for oversharing, published as the Copilot oversharing blueprint, lists four admin steps: identify high-risk sites and files, apply interim access restrictions if needed, fix access issues, and keep enforcing guardrails. It names Microsoft Purview and SharePoint Advanced Management as tools. That makes a useful outline for your ask, because it shows executives a path with an end.

What a CISO will ask

A security chief will go deeper, so prepare short answers to these questions. The role of a chief information security officer is to look for gaps, so welcome the questions.

  1. Which data could be exposed first? Point to your count of widely shared sites and files, and say how you ranked them.
  2. How will we know if something goes wrong? Name the monitoring you have, such as audit logs and the Copilot security dashboard Microsoft describes in the admin center.
  3. What about data leaks and data leaving the company? Cover the data privacy points on training, storage and regions, and your data loss prevention policies.
  4. Who owns the cleanup? Name the owners and the person accountable.
  5. What is the plan for deploying Copilot? Describe a pilot with a small group and clear exit rules.

Frame this as part of your wider Copilot governance and AI governance work, so the briefing is not a one-off. Executives should hear that this is a routine with owners and dates.

Example: a one-page summary

The numbers are made up.

An IT manager has a month before a Copilot pilot for 200 people. She spends two days counting. Her first estimates show 410 of 1,300 sites with company-wide sharing links, 120 sites with no active owner, and one team site holding salary data that all employees can open.

Her page has four blocks. The question: "Could Copilot show payroll data to the wrong person?" The answer: "It shows only what a person can already open, and today at least one salary file is open to everyone." The numbers: the three counts above, marked as first estimates. The ask: approve a six-week cleanup of the 120 ownerless sites and the top 50 company-wide sites before the pilot, with a named sponsor.

The CIO approves the cleanup and moves the pilot back by six weeks. The CISO asks for the same counts every month. The manager now has a standing report and a sponsor.

Common mistakes

  • Promising that Copilot is safe. Say it respects permissions, and say what is still your job.
  • Hiding behind jargon. Executives decide faster when they understand the risk.
  • Opening with fear. A scare invites a ban, not a plan.
  • Bringing no numbers. Counts from your own tenant make the case.
  • Listing ten risks and asking for nothing. Lead with one decision.
  • Skipping the follow-up. Report progress monthly, or the topic disappears.

How software can help

Start with what Microsoft offers: the Copilot security dashboard in the admin center, Microsoft Purview, and SharePoint Advanced Management, which Microsoft's blueprint describes as part of a Copilot license. Use the SharePoint admin center and your own reports for the counts. A spreadsheet is enough for the first briefing. If your tenant is large, a third-party reporting tool can save time, but compare it with these native options first.

Next step

Count three things in your own tenant this week: sites with company-wide links, sites without an owner, and the places where sensitive data lives. Then write the one-sentence answer and the one decision you need, and use them to explain Copilot data risk to executives at your next leadership meeting.

Entities in this article

Copilot governance Oversharing AI governance Chief information security officer (CISO)

Related articles

RSS