What MSPs should fix before enabling Copilot

Microsoft Copilot is showing up in more client environments every month. But there’s a big difference between having a license and being ready to use it safely. Gartner says only 6 percent of organizations have moved beyond a pilot toward full deployment. And MSPs leading these rollouts say the reason most stall isn’t the technology. It’s what the AI finds when you turn it on.

Here’s the problem: Copilot can see anything a user already has permission to see. That sounds reasonable until you consider that most Microsoft 365 environments have years of messy permissions built up: files shared with everyone in the company, old links that were never cleaned up, and folders that were meant to be private but weren’t configured that way.

Nobody noticed because finding that buried information was hard. Copilot, for better or worse, makes it easy.

Jens Hagel, founder of hagel IT-Services, a Hamburg-based MSP with more than 150 mid-sized Microsoft 365 clients, tells SmarterMSP, “Copilot creates no new access, but one simple question pulls those old shares to the front.”

Start with permissions

That’s why experienced MSPs start with the same step before turning Copilot on: cleaning up who can see what.

“Week one is a list of the sensitive areas: HR, payroll, management,” Hagel said. From there, MSPs can review which files and folders are overshared and clean up access. Only then should licenses roll out more broadly.

Barracuda’s Data Inspector can accelerate that pre-launch cleanup by scanning a client’s Microsoft 365 environment to identify sensitive data and overshared files before Copilot surfaces them. This turns what Hagel describes as a week of manual work into a process MSPs can run systematically across clients.

Jeff Dettloff, Head of AI Strategy at Courser, a group of more than 15 IT services organizations, ran his own MSP for years before moving into AI strategy. He’s seen what happens when clients skip this step, and it isn’t always pretty.

“Our closest calls came from clients who already had Copilot running before anyone checked permissions,” he said.

Dettloff can reel off several examples of Copilot calamities he has witnessed.

At one client, an equipment dealer, finance and HR files were visible to people who shouldn’t have been able to see them. Multi-factor authentication wasn’t enabled for everyone, and internal emails were quietly being forwarded to outside addresses.

At a law firm, a small group had been using Copilot for weeks before anyone ran an assessment. The assessment uncovered a folder accessible to anyone without even logging in, along with an old account that still had access to someone else’s email.

“We caught both before Copilot was enabled for the rest of the staff,” Dettloff said.

Copilot can surface problems that were already there

The near-misses follow the same pattern. A manager asks Copilot about an upcoming reorganization and gets details from a planning document that was accidentally shared with the entire company years earlier.

Nobody hacked anything. The permissions were simply wrong, and Copilot did exactly what it was supposed to do.

Meeting recordings are another common issue. They can be stored in ways that allow everyone who attended the meeting, including outside guests, to access them. Most clients have never considered what happens when someone asks Copilot to summarize one.

Chris Stegh, who wrote a book on Microsoft 365 Copilot governance and serves as CTO at eGroup Enabling Technologies, adds a practical warning about sequencing.

Stegh says some organizations refuse to turn on Copilot until they’ve completed a full data cleanup project. The problem is that employees can get tired of waiting and start using outside AI tools on their own, creating a different set of risks.

His recommendation is to clean up the most sensitive files first, then move forward.

“The labeling of the entire tenant before go-live becomes an endless project,” he said. “The labeling of the five libraries in scope takes days.”

Test before launch and track progress

Proving to a client that Copilot is under control also requires real evidence, not just assurances.

Hagel’s method is straightforward: Before launch, log in as an ordinary employee and ask Copilot questions that should be off-limits. Salaries. Confidential agreements. HR cases. If those prompts return results, the client needs to know before an actual employee discovers the information.

After launch, monthly reports can track how many overshared sites have been cleaned up, how many sensitive files are properly labeled, and how many risky Copilot interactions were blocked.

“Executives understand a declining graph,” Hagel said. “They do not understand the slide about governance in place.”

Dettloff keeps a similar paper trail for every client: before-and-after comparisons showing what changed, a simple one-page policy every employee signs, and a log of every new AI feature that gets turned on because Microsoft adds them regularly.

“The client needs a record showing who approved what,” he said.

Make Copilot readiness part of the service

Hagel’s advice for MSPs is simple: Charge for the readiness work upfront.

“Those clients who skip it will pay for the same effort afterwards, once something leaks internally.”

Copilot doesn’t create new permission problems. It surfaces the ones that were already there, quickly and in plain language anyone can understand. For MSPs, that makes readiness work more than a technical prerequisite. It’s an opportunity to help clients understand their existing risk, clean it up, and put stronger governance in place before Copilot exposes it for them.

Photo: Mehaniq / Shutterstock

This post originally appeared on Smarter MSP.