Reliable Networks | Managed IT and Cyber Security Experts

Copilot Sees What Your Users Can See: Fix Permissions Before Rollout

Microsoft 365 Copilot doesn’t break your permissions. It just shows you what they really look like.

Copilot works within your existing security model, so it can only access information the signed-in user is already allowed to see. That sounds reassuring, and in many ways it is. But it also means that any oversharing already lurking in your environment suddenly becomes much easier to find.

A folder shared with everyone years ago. A site where permissions were changed for one project and never put back. A library belonging to a team that no longer exists. Before Copilot, these were hidden in plain sight. After Copilot, one well-phrased question can bring them to the surface in seconds.

In our recent post, Microsoft Copilot: Why Most AI Projects Fail Before Users Even Open the App, we highlighted poor data foundations as one of the biggest reasons deployments go wrong. This time, we’re focusing on the most important technical step of all: getting permissions right before rollout.

Here are seven steps we recommend:

1. Understand where your data lives

Start with an inventory of where your information sits: SharePoint sites, Teams, OneDrive, and shared mailboxes. Then identify which locations hold sensitive material, such as client files, HR records, finance data and board papers. You don’t need to fix everything at once. You just need to know where the biggest risks are.

2. Look for the common oversharing patterns

Most permission problems follow familiar patterns. Look for sites or folders shared with “Everyone” or “Everyone except external users”, permissions granted directly to individuals rather than groups, broken inheritance, “Anyone” links and broad organisation-wide sharing links, sites with no active owner, and old inactive sites full of unreviewed content. Microsoft’s own reporting tools, along with assessments aligned to the CIS Microsoft 365 Foundations Benchmark, can highlight a lot of this quickly.

3. Move to group-based access

Direct user permissions are behind most permission sprawl. Replace them with security groups that reflect how your organisation actually works, whether that’s by team, department or client. Group-based access is easier to understand, much easier to review, and far simpler to maintain when people join, move roles or leave.

4. Restore inheritance where you can

Broken inheritance is sometimes needed, but it’s usually overused. Where folders don’t genuinely need different permissions to their parent site, put inheritance back. Where they do, write down why and give that folder a named owner.

5. Archive what nobody needs

Old, duplicate and inactive content is all risk and no reward. It clutters search results and can actually lower the quality of Copilot’s answers. Agree on a retention approach with the business, archive what’s no longer needed, and keep it recoverable where you’re required to.

6. Test changes with real users

Permission changes can disrupt people’s work if they aren’t tested properly. Check access with a representative group of users before and after changes, explain clearly what’s happening, and make sure there’s a quick route for fixing anything that goes wrong.

7. Put guardrails in place for the future

Fixing permissions once isn’t enough on its own. To stop the problem creeping back, restrict who can create new sites and Teams, set sensible sharing defaults and expiry dates for external links, require every site to have an owner, use sensitivity labels and data loss prevention for sensitive information, and review access regularly.

What this looks like in practice

For Infinite Global, an international communications consultancy, we reviewed and reorganised the client document library before Copilot was rolled out to the wider business. We identified direct user permissions and broken inheritance, moved everything to a security group-based model, archived inactive and duplicate client folders, and validated access with users along the way.

The result was a much cleaner, more manageable foundation. Copilot was then introduced through a controlled pilot, followed by wider rollout and training across the firm’s London, New York and San Francisco offices. You can read the full story in our Infinite Global case study.

Warning signs you’re not ready yet

It’s probably worth pausing your rollout if nobody can say with confidence who has access to your most sensitive sites, if “Everyone” groups appear in your sharing reports, if lots of sites have no clear owner, or if the plan is to assign licences first and tidy up later. Those are exactly the situations where Copilot surfaces things it shouldn’t.

Planning a Copilot rollout?

Copilot readiness is really a data governance exercise, far more than a licensing one.

Here at Reliable, our complimentary Secure AI Readiness Review looks at your Microsoft 365 readiness, data and sharing risks, governance and potential use cases, then gives you an initial view of your readiness and recommended next steps. It’s an introductory review rather than a full technical audit, so you’ll know where you stand before committing to anything.

Get the permissions right first, and Copilot becomes a productivity tool rather than a data exposure risk.

Free IT Health Check: Identify Risks, Gaps and Quick Wins in Your IT

Get a clear picture of your IT, spot risks early, and prioritise the fixes that matter most.

Picture of Gregory Olczyk

Gregory Olczyk

Latest articles

Copilot Sees What Your Users Can See: Fix Permissions Before Rollout

AI for Golf Clubs: A Practical Route from Repetitive Admin to Measurable Value

Free IT Health Check

Fill in the form below to claim your check.