Understanding Copilot's Power and Risk
Updated 8 October 2026: Microsoft is retiring Restricted SharePoint Search, so this post now points to Restricted Content Discovery and SharePoint Advanced Management instead.
Microsoft 365 Copilot uses AI to surface insights, draft content, and automate tasks across your Microsoft 365 environment. However, Copilot inherits your existing Microsoft Graph permissions—meaning it can access and expose any data your users can reach. AI-powered tools amplify the consequences of pre-existing permission sprawl, which makes governance preparation essential before deployment. Without proper governance, Copilot can inadvertently surface sensitive information, amplifying oversharing risks that existed before Copilot was deployed.
1) How Copilot Works (and Why This Matters for Security)
Microsoft Graph as the Foundation
- Permissions model: Copilot uses the logged-in user's permissions to access SharePoint, OneDrive, Teams, Outlook, and other M365 services.
- No elevation: Copilot cannot access data the user doesn't already have permission to view.
- Real-time grounding: Copilot searches your M365 content in real-time to answer prompts; it doesn't train on your data.
- Amplification risk: Copilot makes overshared content discoverable via natural language queries, exposing misconfigured permissions.
What Copilot Can Access
| Service | Data Copilot Can Access |
|---|---|
| SharePoint/OneDrive | All documents user has permission to view (even if never opened) |
| Teams | Chat history, channel messages, files shared in Teams |
| Outlook | Emails, calendar, contacts (user's own mailbox only) |
| Viva Engage | Public and private community posts user can access |
| Loop | Workspaces and pages user has permissions for |
2) Pre-Deployment Security Assessment
Data Governance Audit
- Oversharing analysis: Use Microsoft Purview or ShareGate to identify files shared with "Everyone," "Company-wide," or excessive external sharing.
- Sensitivity labels coverage: Audit percentage of content with sensitivity labels applied; unlabelled content carries unknown risk.
- Permission sprawl: Review SharePoint permissions for broken inheritance, nested groups, and direct user assignments.
- Orphaned content: Identify SharePoint sites and OneDrive accounts for departed users; reassign or delete.
Use Microsoft Purview Data Discovery
# Connect to Security & Compliance Center
Connect-IPPSSession
# Run Content Search for overshared files
$Search = New-ComplianceSearch -Name "Overshared Files Audit" -ExchangeLocation None -SharePointLocation All -ContentMatchQuery "SharedWithDomain:*"
Start-ComplianceSearch -Identity $Search.Identity
# Review results in Purview portal
# https://compliance.microsoft.com/contentsearch
Licensing & Readiness Checks
- Licence requirements: Copilot requires Microsoft 365 E3/E5 or Business Standard/Premium as base licence, plus Copilot add-on (per-user, per-month; confirm current pricing with Microsoft). Organisations frequently underestimate the total cost of AI tool deployments when governance and remediation work is excluded from initial budgets.
- Minimum users: There is no longer a seat minimum for Microsoft 365 Copilot; confirm current licensing prerequisites with Microsoft before planning a rollout.
- Defender for Cloud Apps: Highly recommended for session-level monitoring and policy enforcement.
- Purview Information Protection: Essential for sensitivity labelling and DLP; enables encrypted content protection.
3) Security Controls to Deploy Before Copilot
Step 1: Implement Sensitivity Labels
- Classification schema: Define labels (Public, Internal, Confidential, Highly Confidential) aligned to data handling requirements.
- Auto-labelling: Configure trainable classifiers and keyword-based rules to label content automatically.
- Default labels: Set default labels for SharePoint libraries and Outlook to reduce unlabelled content.
- Encryption: Enable encryption for Confidential and Highly Confidential labels to protect content even if overshared.
Step 2: Configure Data Loss Prevention (DLP)
# Create DLP policy to prevent sharing sensitive content externally
$DLPRule = @{
Name = "Block External Sharing of Confidential Content"
ContentContainsSensitiveInformation = @(
@{Name = "Australia Tax File Number"}
@{Name = "Credit Card Number"}
)
AccessScope = "ExternalDomain"
BlockAccess = $true
}
New-DlpComplianceRule @DLPRule -Policy "Copilot Data Protection"
- Copilot-specific policies: Block Copilot from summarising or extracting content labelled as Highly Confidential.
- Policy tips: Educate users in real-time when attempting to share restricted content.
- Incident reports: Alert security team on DLP violations involving Copilot interactions.
Step 3: Restrict Sharing Permissions
- Disable "Anyone" links: Prevent anonymous sharing in SharePoint and OneDrive tenant settings.
- Default to "Specific People": Configure default sharing links to require explicit recipient selection.
- Expiration policies: Enforce automatic expiration for external sharing links (e.g., 30 days).
- External sharing audit: Monitor external sharing activities via Purview audit logs and alert on anomalies.
Step 4: Implement Privileged Access Controls
- Exclude sensitive sites: Use Restricted Content Discovery in SharePoint Advanced Management (Microsoft Learn — Restricted Content Discovery) to keep HR, Legal and Finance sites out of Copilot responses while you review their permissions, then limit access with Restricted Access Control. It does not change permissions, so treat it as a temporary measure.
- Privileged account separation: Ensure admin accounts cannot use Copilot (apply Conditional Access block).
- Board-level content: Store executive and board materials in dedicated tenants or encrypted containers not indexed by Copilot.
4) Deployment Strategy (Phased Rollout)
Phase 1: Pilot (10-50 Users, 4-6 Weeks)
- Participant selection: Choose tech-savvy users from different departments; exclude users with access to highly sensitive data initially.
- Enable Copilot: Assign licenses via Microsoft 365 Admin Center; confirm activation in Copilot apps (Word, Outlook, Teams).
- Monitor usage: Track Copilot interaction logs in Purview; review prompts and content accessed for inappropriate usage.
- Gather feedback: Survey pilot users on productivity gains, accuracy, and concerns.
- Tune policies: Adjust DLP, sensitivity labels, and sharing settings based on pilot findings.
Phase 2: Expanded Deployment (100-500 Users, 8-12 Weeks)
- Department rollouts: Deploy by department (Sales → Marketing → Operations); stagger to manage change and support burden.
- Training sessions: Conduct hands-on workshops on effective prompting, data handling, and acceptable use.
- Acceptable Use Policy: Publish and require acknowledgment of Copilot usage guidelines (no customer data in prompts, verify AI outputs, etc.).
- Monitor oversharing incidents: Track DLP alerts for Copilot-related violations; coach users on secure practices.
Phase 3: Broad Rollout (All Licensed Users, Ongoing)
- Automate licence assignment: Use group-based licensing to assign Copilot to eligible users.
- Continuous monitoring: Establish baseline usage metrics; alert on anomalous activity (e.g., spike in external sharing post-Copilot use).
- Quarterly access reviews: Audit SharePoint permissions, sensitivity label coverage, and Copilot usage patterns.
5) Monitoring & Governance
Key Metrics to Track
- Copilot adoption: % of licensed users actively using Copilot; prompts per user per month.
- Sensitivity label coverage: % of Copilot-accessible content with labels applied.
- DLP incidents: Number of DLP policy violations involving Copilot; trends over time.
- Oversharing reduction: Decrease in "Everyone" or "Company-wide" sharing post-Copilot governance.
- User feedback: Productivity impact surveys; reported accuracy issues or hallucinations.
Use Purview Audit Logs for Copilot Monitoring
# Search for Copilot interactions in audit logs
Search-UnifiedAuditLog -StartDate (Get-Date).AddDays(-7) -EndDate (Get-Date) `
-RecordType "MicrosoftCopilot" -ResultSize 5000 |
Select-Object CreationDate, UserIds, Operations, AuditData |
Export-Csv "C:\\Copilot_Audit.csv" -NoTypeInformation
Implement Defender for Cloud Apps Policies
- Session controls: Monitor Copilot sessions for unusual data access patterns. Continuous monitoring of AI-assisted workflows is a sound practice for securing cloud-based productivity tools.
- Anomaly detection: Alert on mass file downloads following Copilot usage.
- App permissions: Review and revoke excessive OAuth permissions granted to third-party apps integrated with Copilot.
6) Common Pitfalls & Solutions
- Oversharing revelation shock: Copilot exposes pre-existing permission sprawl; budget time for remediation before broad rollout.
- Unlabeled content: A large share of content in a typical tenant is unlabelled; auto-labelling and default labels are essential before Copilot.
- Hallucinations: Copilot may generate plausible but incorrect responses; train users to verify AI outputs and cite sources.
- Prompt injection risks: Malicious users could craft prompts to extract sensitive data; monitor audit logs for suspicious queries.
- Licensing confusion: Users expect Copilot but lack base E3/E5 licence; clarify licensing requirements upfront.
Before / After
Before Copilot: Overshared content hidden by obscurity, unlabelled files, minimal DLP, users unaware of permission sprawl.
After Copilot (with proper governance): Sensitivity labels on 90%+ content, DLP policies enforced, restricted sharing, Copilot safely enhances productivity without exposing sensitive data.
Australian Context & Compliance
- Privacy Act 1988: Copilot data processing occurs in Microsoft's Australian datacentre (Sydney/Melbourne); confirm residency commitment. The Office of the Australian Information Commissioner (OAIC) (OAIC — Privacy Act 1988 / APP 11, accessed 16 June 2026) has clarified that APP 11 security obligations apply to AI-assisted processing of personal information, requiring organisations to assess governance controls before enabling AI tools at scale.
- Data sovereignty: Copilot queries and grounding data remain in-region; verify Microsoft's Data Residency for M365 Copilot commitment (Microsoft Learn — data, privacy and security for Microsoft 365 Copilot, accessed 16 June 2026).
- ACSC guidance: Implement Essential Eight Control 5 (Restrict Admin Privileges) (ACSC — Essential Eight Maturity Model, accessed 16 June 2026) to prevent admin accounts from using Copilot.
- Industry regulations: Financial services (APRA), healthcare (My Health Records Act) require additional controls; consult legal before broad deployment.
Evidence to Collect
- Data governance audit reports (oversharing analysis, sensitivity label coverage)
- DLP policy exports and Copilot-specific incident logs
- Copilot usage analytics (adoption metrics, prompts per user)
- Acceptable Use Policy with user acknowledgments
- Purview audit logs showing Copilot interactions and data access
Call to Action
Don't rush Copilot deployment—invest time in data governance first. Fix oversharing, apply sensitivity labels, and deploy DLP before rolling out Copilot to your organisation.
CTA: Book a Copilot readiness assessment to identify governance gaps and build a secure deployment roadmap.
Sources referenced in this article: OAIC (Privacy Act 1988 / APP 11), Restricted Content Discovery (Microsoft Learn), Data, privacy and security for Microsoft 365 Copilot (Microsoft Learn), ACSC Essential Eight Maturity Model, ShareGate.


