Microsoft Copilot AI Governance Microsoft 365 SharePoint Security SMB Cybersecurity Data Loss Prevention

Copilot Is Coming to Your Tenant. Your Permissions Aren't Ready.

Microsoft is rolling Copilot into mainstream 365 tiers. Here are the SMB permissions and SharePoint gaps that turn AI into a data exposure problem.

centrexIT
8 min read

Picture this. It’s a Tuesday morning. Your operations manager opens Microsoft 365, sees a new Copilot icon she didn’t have last week, and types a perfectly reasonable question: “Summarize what we know about the Henderson account.”

Thirty seconds later she’s reading a tidy executive summary that includes the contract terms, the renewal price, an internal email where someone called the client “a headache,” and — because somebody once dropped a file in the wrong folder three years ago — the salary of the account executive who manages the relationship.

None of that was supposed to be visible to her. All of it technically was.

Microsoft is in the middle of pushing Copilot down into mainstream 365 tiers. Copilot Chat is already available across most Microsoft 365 business plans, and Microsoft has been steadily expanding which licenses include AI features by default. According to Microsoft’s own announcements, Copilot is now bundled into Microsoft 365 Personal and Family plans, with broader business availability continuing to expand through 2026. For a lot of SMBs, that means AI features are quietly switching on inside tenants whose permissions structure was never built for an assistant that can read every file the user can technically access.

This is the part that doesn’t make headlines. Copilot doesn’t break permissions. It honors them exactly. The problem is that most SMB tenants have permissions that were never honored carefully in the first place.

What Copilot Actually Sees

Microsoft’s documentation is clear on this. Copilot for Microsoft 365 surfaces content the signed-in user already has permission to access — through SharePoint, OneDrive, Teams, Exchange, and the broader Microsoft Graph. It doesn’t elevate privileges. It doesn’t bypass security boundaries. It does, however, make every file a user can technically reach instantly searchable in plain English.

That’s the shift. For twenty years, the unofficial security model in most SMBs has been “yes, technically the intern can open that folder, but they’d never think to look.” Copilot is what thinks to look. Microsoft has acknowledged this dynamic directly — their guidance to admins explicitly warns that “oversharing” inside a tenant becomes materially more visible once Copilot is deployed.

When our team audits a Microsoft 365 tenant before a Copilot rollout, we almost always find the same five gaps. None of them are exotic. All of them are the kind of thing that accumulates quietly over years of normal business activity.

The Five Readiness Gaps We See Most Often

1. SharePoint sites with broken inheritance and forgotten guest access.

Someone shared a folder externally in 2022 for a one-time project. The external user never got removed. The folder’s parent site has “Everyone except external users” baked into a default permission group somewhere. Now Copilot, asked about a related topic, pulls a document from that folder and surfaces it to an internal user who shouldn’t see it. The file was never private. It just wasn’t easy to find.

2. The “Shared with Everyone” OneDrive problem.

Microsoft 365 has a default behavior where files saved to certain OneDrive locations end up tenant-wide discoverable. Executives save sensitive documents to OneDrive thinking it’s personal storage. It often isn’t. Copilot indexes it.

3. Email archives that nobody scoped.

Shared mailboxes accumulate. Delegated access gets granted and rarely revoked. When Copilot summarizes “recent communications about Project X,” it reaches into every mailbox the user has any form of access to — including the shared sales mailbox the user was given read access to in 2019 and forgot existed.

4. Teams channels with permissions that don’t match the channel name.

A Teams channel called “Leadership” sounds restricted. The underlying SharePoint site backing it often isn’t. Files dropped in Leadership channels end up in a SharePoint document library whose permissions were set by whoever created the team — which is often the user, not IT.

5. No data classification, no sensitivity labels, no DLP.

Microsoft Purview’s sensitivity labels and DLP policies are the mechanism Microsoft designed to keep Copilot from surfacing the wrong material. In most SMB tenants, those features are either unlicensed, unconfigured, or configured for one specific data type and ignored for everything else.

Why This Matters For Your Business

For a 50-person business, the worst-case scenarios aren’t theoretical. They look like:

  • An employee asking Copilot a routine question and getting back salary information from an HR file that was never properly secured.
  • A new hire on day three running a Copilot query about clients and accidentally surfacing pricing details that were supposed to be account-team-only.
  • A compliance audit where an investigator asks how AI is governed in your environment and the answer is “we turned it on, we figured it’d be fine.”

The legal and regulatory environment is moving toward AI accountability fast. The EU AI Act is in force. Several U.S. states have introduced AI governance requirements. For businesses in regulated segments — healthcare, life sciences, financial services — the question of “who saw what, and how” is going to get asked, and “Copilot summarized it” is not going to be a satisfying answer.

What To Do Now

Before Copilot is fully active in your tenant — or right now, if it already is — there are five concrete moves worth making.

Audit SharePoint sharing before you audit anything else. Run Microsoft’s SharePoint sharing reports. Find every site with “Everyone” or “Everyone except external users” in its permissions. Find every site with active external sharing links. That’s your starting list.

Identify your overshared OneDrive accounts. Microsoft provides reports showing which OneDrive accounts have the most files shared internally and externally. Executive accounts and long-tenured employee accounts are usually the worst offenders, not by malice but by accumulation.

Review shared mailbox access and delegation. Pull a report of every shared mailbox and every user with Full Access or Send As permissions. Anything that doesn’t map to a current business reason gets revoked.

Turn on sensitivity labels for at least three categories. Confidential. Internal Only. Public. You don’t have to classify everything. You do need the labels available and applied to your highest-sensitivity material — HR records, financial data, client contracts, board materials.

Set a Copilot governance policy before Copilot is used widely. Who can use it. For what. What questions are out of bounds. What gets logged. This doesn’t have to be a fifty-page document. It has to exist.

Common Questions

Does Copilot send our data to OpenAI or train on our content?

No. Microsoft’s commercial Copilot offerings explicitly do not use your tenant’s data to train the underlying foundation models, and your data stays within your Microsoft 365 service boundary. The risk we’re describing isn’t external data exposure — it’s internal data exposure to users who already have a Microsoft 365 license in your tenant.

Can we just turn Copilot off until we’re ready?

For most license tiers, yes — admins can control Copilot availability at the user or group level through the Microsoft 365 admin center. That’s a reasonable interim step while permissions cleanup is in progress.

Do we need Microsoft Purview to govern Copilot?

Purview is the most direct tool Microsoft offers for sensitivity labeling, DLP, and Copilot-specific governance. For SMBs without Purview licensing, the work is still doable — it just relies on manual SharePoint permission reviews and the controls included in your existing Microsoft 365 subscription.

What about Copilot Chat (the free version)?

Copilot Chat with work data protection is included in many Microsoft 365 business plans. It uses a different scope than full Microsoft 365 Copilot — it doesn’t access your tenant’s Graph data the same way. But it’s still worth understanding which version your users are on and what each one touches.

How long does a Copilot readiness audit actually take?

For a typical 25-100 person Microsoft 365 tenant, the permissions and sharing audit takes about a week of focused work. Remediation depends on what’s found. Most SMBs are between two and six weeks of work away from being genuinely Copilot-ready.

centrexIT has been the IT and cybersecurity partner for businesses across the western U.S. since 2002. If you’re rolling out Copilot — or it’s already rolled itself out — and you want to know where your tenant actually stands, that’s exactly the kind of question we audit for every week. Take the 2-Minute Cybersecurity Assessment and see where your tenant stands.

Want to talk it through? Book a free 30-minute consultation and we’ll map where your Copilot readiness actually stands.

Sources

Found this helpful? Share it with your network.
Twitter LinkedIn
Written by
centrexIT

The centrexIT team brings decades of combined IT expertise, helping San Diego businesses thrive with secure, reliable technology solutions.

Meet Our Team