What MSPs are telling CRN
CRN's reporting is built on interviews with three MSP voices and one vendor executive.
Entech. Michael Goldstein, market president for Southeast Florida, says customers are so eager that readiness assessments have become a hard sell. His summary: "It's like a kid in a candy store." He also says the issue is not mainly technical. In his words it is a management issue, because executives need to understand their exposure even though an MSP can technically roll out the tools.
GSC Technologies. Cloud security analyst Brenda Scott says an AI engagement starts by finding what employees already use. In many tenants, staff are using several AI tools before the business has decided anything about AI. These are not only websites. GSC also finds desktop apps, Office add-ins and browser apps. Her biggest worry is confidential material such as client data, financials or internal documents pasted into tools the company doesn't control. She says the review has to repeat, because tools and usage keep changing.
Fluid Designs. Founder Stanley Louissaint says customers often decide first and call afterward, usually when they hit permission problems or other roadblocks. His firm's stance is to lay out the risks, recommend safeguards and leave the final decision to the client. He says it takes about 30 seconds to sign up for ChatGPT with a Google account, and nothing stops staff from doing so.
The numbers: Inforcer's MSP Microsoft Readiness Report
CRN cites the UK-based Inforcer report, a survey of 406 MSPs worldwide.
- 76% of MSPs say customers ask about AI at least monthly. 47% get AI questions weekly.
- Only 14% say they have full visibility into the AI tools their customers use. Another 63% have partial visibility.
- Among customer tenants paying for Copilot, 56% have neither DLP policies nor sensitivity labels enabled. Only 16% have both.
- 62% of MSPs offer Copilot readiness services. 46% offer Purview or data protection services.
- 41% name data hygiene as the most commonly cited obstacle to Copilot deployment.
These are survey results as reported by CRN. I could not locate the underlying report or its methodology. They describe what responding MSPs observe in their own customer bases, not an audit of all Microsoft 365 tenants. Inforcer also sells multi-tenant Microsoft 365 management and Copilot readiness assessment tooling. Its own marketing says a tenant with overshared files, missing sensitivity labels or poorly configured DLP policies risks exposing sensitive information once Copilot is switched on. The vendor therefore has a commercial interest in this problem being seen as urgent. That doesn't make the figures wrong, but it is worth keeping in mind.
Why Copilot makes old permission mistakes matter
Inforcer co-founder Will Connor argues that many MSPs helped customers move files into SharePoint without tightening permissions or access controls. Copilot then makes that sloppiness more consequential. His examples are payroll runs or redundancy lists that were never properly permissioned or labeled. These are his illustrations, not confirmed incidents.
Microsoft's documentation puts the mechanism more precisely than the headline phrasing. Inforcer's own guidance says Copilot is not secure by default. Microsoft's data protection page for Copilot says Copilot respects existing SharePoint and OneDrive permissions, and that if content is already overshared, Copilot can surface it to anyone with access. Copilot does not bypass access controls. What it does is make content easy to find, so a file nobody ever stumbled across may now appear in a summary. Inforcer's guidance makes the same point: Copilot surfaces data based on whatever permissions a user's account already has through Microsoft Graph.
Two separate problems that often get lumped together
Shadow AI visibility is about knowing which AI tools staff use and what they paste into them. That is what the GSC and Fluid Designs accounts describe, and it is where the 14% "full visibility" figure lands. Copilot-specific Purview controls do not govern ChatGPT or other external AI apps.
Copilot readiness is about whether permissions, labeling and DLP in the Microsoft 365 tenant are fit for AI-assisted discovery. The 56% and 16% figures describe this problem.
A team that fixes only one will still have the other.
What Microsoft actually provides
Microsoft's documentation lists several controls, each with limits that matter in practice.
- Discovery and access controls. These include Restricted Content Discovery, which limits which sites and content appear in Copilot and in organization-wide search. They also include restricted access control for SharePoint sites and OneDrive. For ongoing cleanup, Microsoft points to site access reviews and inactive site policies in SharePoint Advanced Management.
- Sensitivity labels. Labels classify content, and Copilot recognizes them. With encryption, Copilot needs the user to hold both the VIEW and EXTRACT usage rights before it will summarize the content. With VIEW only, it can return a link so the user can open the item outside Copilot. Microsoft lists limits: Copilot and agents can't access content protected by Double Key Encryption, and they don't currently recognize labels that protect Teams meetings and chats.
- Purview DLP for Copilot. A policy can stop Copilot from processing files and emails that carry chosen sensitivity labels. Those items can still show up in a response's citations, but their content isn't used in the summary.
- Prompt-level DLP. A separate rule can block Copilot from responding to prompts containing sensitive information types. Microsoft describes this as a preview feature that is rolling out. It checks only text typed into the prompt. Files uploaded directly into a prompt are not scanned.
- Coverage gaps. Label-based DLP covers file items and emails sent on or after January 1, 2025. Calendar invites are not supported. A policy applies when a file is opened, so a label added mid-session takes effect the next time the file opens. Policy updates can take up to four hours to reach Copilot experiences.
Microsoft also lets admins use policy simulation mode for Copilot DLP, which makes it possible to test a rule before enforcing it.
A practical readiness sequence
This is my synthesis of the MSP accounts and Microsoft's documentation, not a checklist from CRN.
- Inventory what's already in use. Look for AI websites, desktop apps, Office add-ins and browser extensions, as GSC does. Repeat the check regularly.
- Review SharePoint and OneDrive sharing. Find overshared sites, broad groups and stale content before anyone gets a Copilot license.
- Decide what Copilot should not touch. Build a label taxonomy and use DLP to exclude the most sensitive labels from processing.
- Use discovery controls for the leftovers. Restricted Content Discovery and access reviews can help while permission cleanup continues.
- Test, then enforce. Use simulation mode and allow for the policy propagation delay.
- Get executive sign-off. Goldstein's point is that someone in management must own the risk decision, and that decision should be recorded.
Be careful with permissions. Microsoft's role list for Copilot DLP policies includes Entra Global Admin, but its own advice is to use roles with the fewest permissions.
Analysis: sell the cleanup first
Connor's advice is that MSPs should run readiness work before selling AI licensing. He is selling a product in this space, but the reasoning holds up on its own. A Copilot rollout that surfaces an exposed HR spreadsheet in its first week is a worse outcome for everyone than a slower start. The counterpoint comes from Louissaint's position. Customers who have already decided will not wait, and an MSP that insists on gating the rollout may simply be bypassed. His "explain the risks, document them, let the client decide" approach is realistic, and it protects the provider. It also leaves the client carrying whatever the survey numbers imply about missing DLP and labels.
For admins, the useful point is that these controls exist and are documented, but they have to be configured. The CRN-reported survey suggests that in many paying Copilot tenants they have not been.
References
- MSPs On Customers Rushing To Deploy AI: ‘It’s Like A Kid In A Candy Store’ - www.crn.com www.crn.com · Mon, 16 Nov 2026 14:00:00 GMT
- Microsoft 365 Copilot Readiness Assessments inforcer.com
- How to Assess Microsoft Copilot Readiness as an MSP inforcer.com