Microsoft 365 Copilot readiness: fix oversharing before you turn it on.

The first week of a Copilot pilot often goes like this. Someone asks Copilot for "last year's budget." It answers with a spreadsheet that turns out to include every staff member's salary. Copilot didn't break in to get it. The file sat in a team site shared with the whole organization in 2021, and nobody remembered it was there.

That is the central fact of a Microsoft 365 Copilot readiness assessment. Microsoft states plainly that Copilot uses the access rights of the person asking: it only shows content that person is already allowed to open. Copilot follows your permissions exactly. The trouble is that, in most tenants, the permissions were never meant to be read this literally. Before Copilot, a forgotten file was protected by being hard to find. Copilot takes that protection away.

What Copilot can actually see

"Copilot" now covers several products, and they don't all reach into your data the same way:

• Copilot Chat (included with eligible Microsoft 365 plans). Primarily grounded in the web, plus whatever a user pastes or uploads. In Outlook it can also reason over that user's own mail, calendar, meetings and chats.
• The paid Copilot license. Searches across everything the user can reach in Microsoft 365: SharePoint, OneDrive, Teams, mail and meetings. Organizations under 300 users buy it as the Microsoft Copilot Business add-on to their Business Basic, Standard or Premium plans.
• Agents. An agent pointed at a SharePoint site answers questions from that site's content, limited to what each person can open. If your organization turns on metered agents, staff without the paid license can use them too.

Every one of these respects permissions. None of them fixes permissions that are wrong. That's why readiness work belongs before the license purchase, not after the first awkward answer.

Where oversharing hides in a small organization

SharePoint and Teams are built to make sharing easy, and few small organizations ever revisit their sharing settings. Years of "just share it with everyone so it works" leave predictable residue:

• "Everyone except external users" permissions. One click grants every account in the tenant access to a site, library or folder. It's the most common source of surprise answers.
• "Anyone" links. Links that work for whoever has them, often created for one vendor or board member years ago and never expired.
• Old Teams and sites with no owner. The 2020 event-planning team, a departed director's project site. Nobody reviews them because nobody owns them.
• Sensitive files in general-purpose places. HR exports, payroll, donor or client lists, and board executive-session notes saved to the all-staff site because it was convenient.
• Broken inheritance. A folder whose permissions were changed once, by hand, so it no longer follows the site's rules and doesn't show up when someone reviews the site.

The question isn't "is Copilot secure?" It's "if every employee could search every file they technically have access to, would we be comfortable?"

A readiness assessment in six steps

This is the order we work in during AI Foundations engagements when Copilot is the first pilot. It follows Microsoft's published deployment blueprint (remediate oversharing, set up guardrails, meet regulations), scaled down for organizations without a full-time security team.

1. Run the reports you already have

SharePoint Advanced Management is now included with the Copilot license, and its data access governance reports are the fastest way to see your exposure. Start with the site permissions baseline, the "Everyone except external users" report and the sharing links report. Together they show which sites are open to the whole organization and which have live "Anyone" links.

2. Triage by sensitivity, not by size

A widely shared site full of newsletters is fine. A small site with three salary spreadsheets and an "Everyone" permission is the emergency. Rank sites by what's in them, and pay particular attention to HR, finance, fundraising, client records and anything legal or board-related.

3. Apply a temporary guardrail to the worst sites

Restricted Content Discovery keeps a site out of Copilot and organization-wide search without changing anyone's permissions, which buys time while the real fix happens. Two caveats from Microsoft's documentation: it doesn't stop Copilot from summarizing a document a user already has open, and on very large sites it can take more than a week to take full effect. The older stopgap, Restricted SharePoint Search, is being retired, and new enablement has been blocked since July 31, 2026, so plans that still list it need updating.

4. Fix the access itself

Remove "Everyone" permissions where they aren't needed, expire stale "Anyone" links, assign an owner to every site that will stay, and archive or delete the ones that won't. Site access reviews let you hand each owner a list of what to confirm rather than doing it all centrally. For a handful of truly sensitive sites, Restricted Access Control limits access to a named security group no matter what links exist. Then tighten the tenant-wide sharing defaults so the problem doesn't grow back.

5. Use labels and DLP where your licensing allows

Microsoft Purview can prevent Copilot from processing files that carry a sensitivity label such as "Highly Confidential." Check your licensing before you plan around it: Microsoft's service description lists this control for E5-level plans but not for Microsoft 365 Business Premium. Most small organizations are on Business Premium, so for them permissions and Restricted Content Discovery do the real work, and labels serve mainly to tell staff what's sensitive. (Data loss prevention that blocks sensitive data typed into Copilot prompts is available to all Copilot users.)

6. Pilot small, then try to break it

License a pilot group of five to fifteen people from different teams. Before they start, have someone deliberately ask the questions you hope Copilot can't answer: "What does each person on staff earn?" "Summarize the last board executive session." "List our largest donors and their giving history." Every answer that comes back is a permission to fix. Purview audit logs let you confirm what Copilot touched during the pilot.

What "ready" looks like

You don't need a perfect tenant before turning Copilot on. You need four things: no organization-wide access to sensitive content, an owner for every active site, a short list of high-risk sites restricted from discovery while cleanup finishes, and a pilot group that has tried to surface sensitive information and failed. Combine that with a shadow AI review of the tools staff already use and the plain data boundaries in our AI Acceptable Use Policy template, and the license becomes a productivity decision rather than a security gamble.

Sources

Product details in this article were checked against Microsoft's documentation on October 28, 2026. Microsoft changes licensing and feature names often, so confirm current terms before purchasing.

• Secure and govern Microsoft Copilot: foundational deployment guidance
• SharePoint Advanced Management features in Microsoft Copilot licenses
• Data access governance reports for SharePoint sites
• Restrict discovery of SharePoint sites and content
• Restricted SharePoint Search (retirement notice)
• License options for Microsoft Copilot
• Overview of Microsoft Copilot Chat
• Microsoft Purview service description (DLP for Copilot licensing)