Before You Turn On Microsoft Copilot: Clean Up Who Can See What

If your business runs on Microsoft 365, someone has probably asked whether you should turn on Copilot. It's a fair question. Copilot can draft emails, summarize long threads, pull numbers out of spreadsheets and find the document you vaguely remember from last spring.

There's one thing to understand before you flip it on, and it has nothing to do with the AI itself. It's about your file permissions.

What Copilot can actually see

Microsoft's own documentation is clear on this point. According to Microsoft's data, privacy and security page for Copilot, Copilot "only surfaces organizational data to which individual users have at least view permissions." The same page tells organizations to use the permission models in services such as SharePoint "to help ensure the right users or groups have the right access to the right content."

That's good news and a warning at the same time. The good news is that Copilot doesn't invent new access. It respects the permissions you already have. Microsoft also states that prompts, responses and data accessed through Microsoft Graph aren't used to train the foundation models.

The warning is that most small businesses have years of loose sharing built up. A folder was shared with "everyone" to get a project done fast. A former office manager's OneDrive still has a link that works for anyone in the company. Payroll exports sit in a Teams channel that half the staff joined once and never left.

Before AI, those mistakes were mostly hidden because nobody went digging. With an assistant that can search everything a person is allowed to open, a simple question like "what did we pay our staff last quarter?" might return an answer you never meant that person to see.

Why this matters more for local professional firms

For the kinds of businesses we work with in Jacksonville and Orlando, overshared files aren't just awkward. They can create real obligations.

• Medical and dental offices keep patient information, insurance details and treatment notes. Front desk staff may need schedules, but not every clinical document.
• CPA firms hold tax returns, bank statements and Social Security numbers for every client. Seasonal staff often get broad access in March and keep it all year.
• Law firms need to keep matters separated so that people only see the cases they work on.
• Home service companies store employee records, customer addresses and payment details next to everyday job files.

In every one of these, a permissions cleanup is good security practice whether or not you ever use AI. Copilot just raises the stakes and gives you a good reason to do it now.

A practical cleanup in five steps

You don't need an enterprise data governance program. You need a focused pass through the places where sensitive files actually live. Here's the order we suggest.

1. List where your sensitive information lives

Start with a short inventory. Where are payroll files, client or patient records, contracts, tax documents and HR files stored? Common answers are a handful of SharePoint sites, a few Teams channels and individual OneDrive folders. Write them down. This list is your scope.

2. Find "everyone" and "anyone with the link" sharing

The biggest risks are broad sharing groups and open links. Look for files and folders shared with large groups or with your whole company, and for links that work for anyone who has them. Your Microsoft 365 admin center and SharePoint admin tools include sharing reports and settings that help here. If you have an IT provider, ask them to pull this for you.

3. Remove access that people no longer need

Check team and channel membership, especially for anything finance, HR or client related. Remove former employees and seasonal staff, and make sure departed users' accounts are actually disabled. Then tighten the folders on your list so that only the roles that need them can open them.

4. Label the most sensitive material

For the files that truly can't leak, consider sensitivity labels. Microsoft's documentation notes that when content is protected with Microsoft Purview Information Protection, Copilot honors the usage rights granted to the user. Depending on your licenses, that gives you a second layer of protection on top of folder permissions. Your licensing and setup determine what's available, so confirm the specifics for your plan.

5. Test before you roll out widely

Turn Copilot on for a small pilot group first, ideally a couple of people from different roles. Have each one ask questions they shouldn't be able to answer, such as salaries, other clients' returns or another attorney's matters. If an answer comes back, you found a permission to fix before everyone else gets access.

Start with one workflow and measure it

Cleaning up permissions makes Copilot safe to turn on. It doesn't make it worth paying for. The way to find out is the same approach we recommend for any AI tool: pick one workflow, measure how long it takes today, and compare after a few weeks.

Good first candidates for a small professional office include:

• Summarizing long client or vendor email threads before a call
• Drafting first versions of routine letters and follow-ups that a person then reviews
• Pulling notes and action items out of recorded internal meetings

Measure something simple, like minutes per task or the number of tasks finished per week, for two weeks before and after. Microsoft's documentation itself says generative AI output isn't guaranteed to be factual and that people should review it before sending, so include review time in your measurement. If the numbers don't justify the license cost for that workflow, you've learned that cheaply.

What to tell your team

A short note before rollout prevents most problems. Let people know that Copilot can only see what they can already open, that they should review anything it drafts before it goes to a client or patient, and that if it ever shows them something that looks like it shouldn't be visible, they should report it rather than ignore it. That last habit turns every employee into an early warning system for a permission you missed.

If you haven't written down your team's AI rules yet, a one-page AI use policy pairs well with this cleanup.

FAQ

Does Copilot give employees access to files they couldn't open before?

No. Microsoft states that Copilot only surfaces data that each user already has at least view permission to. The risk is that many users already have more access than you realize, and Copilot makes that access easier to use.

Is our data used to train the AI?

According to Microsoft's documentation, prompts, responses and data accessed through Microsoft Graph aren't used to train the foundation models used by Copilot. Review the current terms for your specific plan, since products and names change.

Do we need to clean up every file before starting?

No. Focus on the places where sensitive information lives: finance, HR, client or patient records, and legal matters. A targeted pass through those areas covers most of the risk.

Can we use Copilot with patient information?

Microsoft lists HIPAA among Copilot's compliance offerings, but whether it fits your practice depends on your agreements, licensing and configuration. Confirm with your compliance advisor before using it with protected health information.

How long does a cleanup take?

It depends on how many sites, channels and shared folders you have and how long sharing has gone unchecked. Starting with an inventory of sensitive locations gives you a realistic scope quickly.

Get a second opinion

If you're weighing Copilot or another AI tool and want to know what to fix first, we can help you find the risks and pick one workflow worth measuring. Take our free assessment at rsoftware.net/assessment or email us at hello@rsoftware.net.

For more practical guides on secure AI, automation, and security for local businesses, follow R Software & Consulting on LinkedIn.

Written with help from our AI assistant.