Microsoft Copilot readiness: permissions and oversharing

Copilot doesn't change who can see what, but it makes overshared files easy to find. Seven oversharing mistakes to fix before rollout, how to find each one, and Microsoft's tools for the job.

On this page
  1. What can Copilot actually see?
  2. Is anything still shared with "Everyone except external users"?
  3. Are old sharing links still open?
  4. Were Teams set up as public by accident?
  5. Did migrated file-server folders keep the permissions you expected?
  6. Who can still see former staff's OneDrive files?
  7. Is a site that's meant to be open full of the wrong content?
  8. Are you holding back rollout until every site is perfect?
  9. Frequently asked questions

Microsoft Copilot only shows people data they already have permission to see, so the risk before rollout isn't Copilot breaking permissions. It's years of loose sharing becoming easy to find by asking a question. Fix the oversharing mistakes below first, starting with the sites that hold HR, payroll, contracts and client data.

This is for small and mid-size businesses planning to turn on Copilot in Microsoft 365. Each section is one mistake, how to find it, and how to fix it.

What can Copilot actually see?

Copilot can see what each person can already open, and nothing more. Microsoft's Copilot privacy page (checked 16 November 2026) says it only surfaces organisational data to which each user has at least view permission, and that it honours sensitivity labels and encryption.

So if a salary spreadsheet sits in a site everyone can open, a person who never knew it existed can ask Copilot about salaries and get an answer. Nothing was hacked. The permission was always there; it was just hard to stumble on.

Which Microsoft tools help find oversharing?

Microsoft's Copilot deployment blueprint says SharePoint Advanced Management is included with a Microsoft Copilot licence. Its help pages describe the tools used in the fixes below: data access governance reports (a site permissions baseline, plus reports on sharing links and sites shared with everyone), Restricted Content Discovery, Restricted Access Control, and Restricted SharePoint Search.

Cloudgramam sells Copilot readiness reviews, so read this knowing we have an interest. Copilot and Microsoft 365 licences are paid to Microsoft or your partner; we charge only for our work. Tool names and features were checked on Microsoft's pages on 16 November 2026.

Is anything still shared with "Everyone except external users"?

In a small tenant this is often the widest-open setting: chosen once for convenience and never narrowed.

To find it, run the data access governance report for sites shared with everyone. In a small tenant you can also open each site's permissions and look for that group. To fix it, replace "Everyone except external users" with the Microsoft 365 group for the team that actually uses the site. When I review a tenant, this is the first report I open, because it's one of the quickest fixes with the biggest effect.

Links made for one person often work for many. "Anyone with the link" and "people in your organisation" links keep working long after the email that carried them is forgotten.

Find them with the sharing links report in data access governance. Remove links on sensitive files, and change the default link type to "specific people" so new links start narrow. Decide external sharing at the same time, on purpose, rather than inheriting whatever was set when the tenant was created.

Were Teams set up as public by accident?

A public team lets anyone in the company join and see its files. Teams created in a hurry are often public because nobody changed the option.

Go through the list of teams and check each one's privacy setting. Make a team private when its files are meant for its members only. Public teams for company-wide topics, like a social channel or IT announcements, are fine as they are.

Did migrated file-server folders keep the permissions you expected?

Often not. Folder-by-folder permissions from an old server rarely land in SharePoint the way anyone planned, and an HR folder that was locked on the S: drive can end up open.

Check with a test account that has an ordinary user's access: sign in and try to open the folders that should be closed. Fix it by moving sensitive folders into their own private sites with group access, rather than patching permissions folder by folder. The SharePoint guide for small companies covers how to structure that move.

Who can still see former staff's OneDrive files?

Anyone they shared files with, until someone reviews it. Files a leaver shared widely from OneDrive tend to stay shared because nobody owns the review.

Add a OneDrive sharing check to your leaver process, and look at the sharing links report for leavers' files during your readiness review. Move anything the business still needs into the right team site, then remove the old links.

Is a site that's meant to be open full of the wrong content?

This one hides from permission reports, because the permissions are correct. The content isn't.

Here's an illustrative example. A 50-person consultancy shares a "Templates" site with everyone, which is right. Over the years, consultants saved finished client proposals there as examples, including fee rates, client names and one client's confidential restructuring plan. Every report says the site is fine.

Finding it needs a content check: for each wide-open site, look at what's in it as well as who can see it. Sort by "modified by" and scan for client names. Move client material to the right client or project site and replace it with cleaned examples. Agree a rule for the shared site, templates only, with someone checking it each quarter. Then apply a sensitivity label from Microsoft Purview to confidential client documents, so their protection travels with the file whichever site it ends up in.

Are you holding back rollout until every site is perfect?

You don't need to. Microsoft provides tools to keep sensitive sites out of Copilot while you finish the clean-up.

Restricted Content Discovery keeps chosen sites out of Copilot and organisation-wide search without changing their permissions. Restricted Access Control limits a site to a named group, even for people who had access before. Restricted SharePoint Search is a temporary measure that limits organisation-wide search and Copilot to a list of sites you choose. I'd use Restricted Content Discovery on anything sensitive you can't fix before the start date, then start Copilot with a pilot group and ask them to report anything surprising it shows them. Their reports become your next clean-up list.

Frequently asked questions

Is our data used to train Copilot's models?

Microsoft's privacy page says prompts, responses and data accessed through Microsoft Graph aren't used to train foundation models.

How long does Copilot readiness take for a small business?

A few days to a few weeks, depending on how much sharing needs fixing.

If you're still moving to Microsoft 365, sort sharing out during the move, using the Microsoft 365 migration checklist. For a review of an existing tenant, see our Microsoft 365 services.

microsoft 365microsoft copilot readinesscopilot oversharingsharepoint permissionsdata governance

Gowtham D

Full Stack Digital Marketer and Full Stack Developer

Gowtham D is a full stack digital marketer and full stack developer, a Microsoft Power Platform developer, content writer and data analyst with 15 years of experience.

Gowtham D on LinkedIn

Websites and systems that work for you

Custom websites, apps, integrations and Microsoft 365, built and looked after.