Yesterday we covered what's new in Microsoft Copilot after the Ignite announcements — the unified home screen, smarter AI routing, and the always-on Autopilot agent. The common thread through all of it: Copilot works by reading your data. That's the point. That's what makes it useful.
But if your business stores sensitive documents in Microsoft 365 — attorney correspondence, medical records, financial data, HR files — it's worth taking a few minutes to understand exactly what Copilot can see and what that means in practice.
This isn't a warning to avoid Copilot. It's a reminder that a powerful tool that knows your business deserves a little thought before you hand it the keys.
What Copilot Actually Has Access To
Copilot doesn't just answer general knowledge questions. It's connected to your organization's Microsoft 365 environment — which means it can read and reason over:
- Emails in Outlook (yours, and in some cases shared mailboxes)
- Files stored in OneDrive and SharePoint
- Teams messages and meeting transcripts
- Calendar events and meeting notes
- Documents you're working on in Word, Excel, and PowerPoint
The new Work IQ feature announced this week makes this more explicit — it's specifically designed to reason over your organization's actual data to give contextually relevant answers. Ask it "what are the terms of our contract with the Johnson account?" and it will look for and read that contract.
The Scenarios Worth Thinking About
If your firm stores client contracts, settlement agreements, or attorney-client correspondence in SharePoint or OneDrive, Copilot can access those files. Any user with Copilot who also has permission to view those documents can ask Copilot to summarize, reference, or draft based on them. Attorney-client privilege doesn't change how Copilot handles the data — it only knows what it can read.
For healthcare-adjacent businesses — medical offices, billing services, insurers — patient information stored in Microsoft 365 is subject to HIPAA regardless of how it's accessed. Copilot processing that data doesn't create a new HIPAA violation on its own (Microsoft's data handling is covered under BAA agreements), but it does mean that a staff member with Copilot access could inadvertently surface protected health information in a summary or report without realizing the source.
Salary spreadsheets, performance reviews, disciplinary records, and banking information stored in Microsoft 365 are all fair game for Copilot — for any user who has permission to access those files. If a manager has Copilot and your HR files are on a broadly shared SharePoint site, Copilot can pull from them.
What Microsoft Actually Does With the Data
Microsoft is clear that Copilot for Microsoft 365 does not use your organizational data to train its AI models. Your data stays within your Microsoft 365 tenant. When Copilot processes a document, it's doing so within your environment, not sending it somewhere external to be stored or analyzed.
That's the right answer, and it means the cloud-side risk is relatively low for most businesses. The bigger risk is internal.
The Real Issue: Permissions
Copilot respects Microsoft 365 permissions — it can only access files and emails that the user asking the question already has permission to see. This sounds reassuring, but it also means your existing permission structure matters a lot more once Copilot is in the picture.
Many small businesses have never done a serious SharePoint permissions audit. Files get shared broadly for convenience. Folders get inherited permissions that nobody remembers setting. When a human navigates SharePoint, they mostly look at what they're specifically trying to find. When Copilot searches, it can surface connections across files that a person might never have stumbled across manually.
Loose permissions that were harmless before become more visible with an AI assistant actively reasoning over everything it can reach.
What to Do Before Turning It On
- Audit who gets Copilot access first. You don't have to give it to everyone on day one. Start with users whose work doesn't involve the most sensitive data.
- Review SharePoint and OneDrive permissions. Anything broadly shared that shouldn't be — tighten it before Copilot has a reason to find it.
- Know what you're storing in Microsoft 365. If your most sensitive documents live there, factor that into how you deploy Copilot and to whom.
- Check your BAA with Microsoft if you're in a healthcare-adjacent business. It should already cover Microsoft 365 services — confirm it explicitly covers Copilot.
None of this requires stopping or avoiding Copilot. It just requires doing the homework that good IT hygiene already calls for — Copilot just gives you a clearer reason to actually do it.
Questions about Copilot and your business data?
We're happy to take a look at your Microsoft 365 setup and give you a straight answer on where the sensitive stuff lives and what to tighten up before you roll out Copilot. Give us a call — no obligation.