Notifications
Clear all
Topic starter
06/06/2026 2:32 am
TL;DR: Microsoft Copilot’s cross-application reach through Microsoft Graph can expose emails, files, chats, and meetings at machine speed, while 97% of organisations that suffered an AI-related breach reported weak AI access controls, according to WitnessAI analysis. The governance gap is not the model, but the latent permissions, prompt injection surface, and audit blind spots already present in the enterprise stack.
NHIMG editorial — based on content published by WitnessAI: Microsoft Copilot security risks and mitigation guidance
By the numbers:
- 97% of organizations that experienced an AI-related breach reported a lack of proper AI access controls.
- 72% of organisations have experienced or suspect they have experienced a breach of non-human identities, 46% confirmed and 26% suspected.
Questions worth separating out
Q: How should security teams control Copilot access to enterprise data?
A: Start with the permissions model, not the chatbot interface.
Q: Why do AI assistants like Copilot create governance risk in IAM programmes?
A: Because they activate existing entitlements and compress discovery time.
Q: What breaks when AI audit logs only show interaction metadata?
A: Investigation quality breaks first, then compliance confidence follows.
Practitioner guidance
- Remediate broad content permissions before enabling Copilot Identify SharePoint sites, mailboxes, and shared folders that Copilot can reach through inherited permissions, then remove Anyone links and company-wide sharing patterns that create unintended retrieval paths.
- Validate audit completeness for prompts and responses Test whether your logging stack captures the actual prompt, response, and policy decision, not just metadata that an interaction occurred, so investigations can reconstruct what the AI accessed and returned.
- Apply AI-specific identity controls to Copilot use Use Conditional Access and least-privilege administration to restrict who can use Copilot and who can change its settings, then review those roles as part of the AI rollout rather than after it.
What's in the full article
WitnessAI's full article covers the operational detail this post intentionally leaves for the source:
- Step-by-step guidance for remediating SharePoint and Microsoft 365 oversharing before Copilot rollout
- Detailed configuration notes for Microsoft Purview, Conditional Access, and Copilot-specific DLP controls
- Examples of prompt injection and data exfiltration paths that security teams can test against
- The article's full mapping of native controls to their known blind spots and residual risks
👉 Read WitnessAI's analysis of Microsoft Copilot security risks and controls →
Microsoft Copilot access control gaps: what IAM teams need to know?
Explore further
06/06/2026 4:15 am
Copilot governance is an entitlement problem disguised as an AI problem. The article shows that the real risk comes from inherited Microsoft Graph permissions, not from the model itself. When an AI system can instantly surface everything a user is already entitled to see, old assumptions about manual discovery and low-frequency data access collapse. Practitioners should treat the retrieval plane as part of the access model, not a separate AI layer.
A few things that frame the scale:
- 72% of organisations have experienced or suspect they have experienced a breach of non-human identities, 46% confirmed and 26% suspected, according to The 2024 ESG Report: Managing Non-Human Identities.
- Enterprises that have experienced a compromised NHI averaged 2.7 separate incidents in the past 12 months, according to the same report.
A question worth separating out:
Q: How do security teams reduce prompt injection risk in enterprise AI systems?
A: Treat enterprise content as part of the attack surface, not just the prompt box. Use layered controls that inspect model-facing inputs, enforce runtime policy, and limit which content sources can influence high-risk workflows. The goal is to stop malicious instructions embedded in ordinary documents and messages from steering model behaviour.
👉 Read our full editorial: Microsoft Copilot security risks expose gaps in AI access control
