Copilot Is Now Part of Microsoft 365. Do You Know What It Can See?
On July 1, 2026, Microsoft raised commercial Microsoft 365 prices by 5% to 43% and, in the same move, folded Copilot Chat into the base plans instead of selling it as a standalone add-on. Microsoft 365 Business Standard and Business Premium now ship as permanent plans with Copilot included, and the price of the old standalone Copilot license went up on top of that.
Most small and midsize businesses experienced this as a line-item change on a renewal invoice. Few experienced it as what it actually is: an AI system with access to your Exchange mailboxes, your Teams chats, your OneDrive files, and every SharePoint site your users can already see, now switched on by default instead of gated behind a purchase decision.
Copilot didn't get new access. It got a bigger audience.
It's worth being precise about what changed and what didn't. Microsoft's own documentation on data, privacy, and security for Microsoft 365 Copilot is direct on this point: Copilot "only surfaces organizational data to which individual users have at least view permissions." It uses the same underlying access controls as SharePoint, OneDrive, and Exchange. It doesn't have a backdoor, and it doesn't elevate anyone's privileges.
That's the reassuring half of the story. The uncomfortable half is what Peafowl IT Solutions flagged in their own analysis of Copilot readiness: Copilot doesn't bypass your permissions model, it exposes it. Overshared files, old SharePoint sites nobody remembers creating, public Teams, broad security-group grants, and years of "just give everyone access, it's easier" decisions have been sitting there quietly for years. A human being had to know a site existed and go looking to find that exposure. Copilot just has to be asked a question in plain English, and it will retrieve and summarize whatever the signed-in user can technically reach, without the user ever knowing they'd overstepped anything.
Put plainly: the attacker in this scenario is not an outsider. It's your own employee, asking a perfectly reasonable question, who now gets an AI-generated summary of the HR site they were never supposed to browse into, the finance folder that was shared "temporarily" three years ago, or the executive OneDrive that someone accidentally set to "Anyone with the link." No exploit required. Just a prompt.
Before this rolled into your tenant, Microsoft told you what to check
Microsoft doesn't leave this as an abstract warning. Its own Copilot readiness guidance lays out a specific sequence, built around tools in SharePoint Advanced Management, most of which are already included in your tenant if you're licensed for Copilot:
- Run a Content Management Assessment. One click in the SharePoint admin center surfaces overshared content, ownerless sites, and inactive sites, and gives you a Copilot-readiness score. Microsoft recommends rerunning it every 30 days.
- Pull the site permissions baseline report to see your organization's overall access exposure, and the "Everyone Except External Users" (EEEU) report to find the sites shared with your entire company in the last 28 days.
- Check sharing-link activity. The sharing links report shows you which sites have the most "Anyone" links, not just "specific people" links, which is where accidental oversharing usually lives.
- Use Restricted Access Control on sites that should only be visible to a defined group, and Restricted Content Discovery on sites that need to stay accessible to a few people but have no business showing up in a Copilot answer or a tenant-wide search.
- Confirm sensitivity labels are actually applied, not just configured. Copilot honors Microsoft Purview Information Protection labels and Information Rights Management restrictions, but only on content that's actually labeled. Unlabeled sensitive files get no protection at all.
- Verify your DLP policies are in enforce mode, not just audit mode. A data loss prevention policy sitting in "report only" catches nothing. It's easy to leave a policy in that state during rollout and forget to flip it.
None of this is exotic. It's the SharePoint and Purview hygiene that should have happened years ago, and now has a hard deadline because the tool that makes the gap visible is already in your tenant.
This is a permissions problem, not a Copilot problem
It's tempting to treat this as an AI risk story. It isn't, really. Copilot didn't create overshared SharePoint sites or forgotten "Anyone" links. Those existed before Copilot ever showed up. What Copilot does is remove the last bit of friction between "technically accessible" and "easily discovered." A permissions model that was sloppy but survivable in 2023 becomes a live exposure the day an AI assistant with a natural-language interface sits on top of it, whether you asked for that assistant or it arrived bundled into your next renewal.
This is exactly the kind of conversation the team at C Spire Business navigates with customers before a new feature becomes a new exposure: audit first, then adopt, not the other way around.
If Copilot is now part of your Microsoft 365 subscription whether you asked for it or not, the question worth answering this week isn't whether the AI is any good. It's whether you actually know what it can reach on day one, and whether you're comfortable with the answer.