Microsoft Copilot privacy policy
Your Copilot policy says HR data stays in HR. Does your tenant agree?
A Copilot privacy policy is a statement about permissions, and in a typical tenant the permissions do not match the document: payroll folders shared with the whole company, sensitive sites Copilot indexes, agents nobody registered reading mail. 1Security shows which sites, files and agents Copilot can actually reach, constrains what the policy forbids behind a review window, and keeps the numbers that prove the policy is being kept.
The problem
The policy was written. The permissions were never consulted.
Copilot honours your permissions by design - which means your permissions are the policy. It reads whatever the signed-in user can already open, so every stale sharing link, every over-broad group and every forgotten site is one well-phrased prompt away from a summary. A typical user can already reach hundreds of thousands of files.
A privacy policy that says "Copilot must not surface HR or payroll data" is therefore broken the moment 200 people can technically open the salary review folder - no prompt filtering required. In the tenants we connect to, 20-40% of files with sensitive content carry no sensitivity label, and dozens of Copilot-indexed sites hold card numbers, IDs or health data.
Copilot respects your permissions by design, so the tenant-side half of any privacy policy - what those permissions let Copilot read - is yours to govern. Enforcing the policy means mapping that reach, removing what it should not include, and measuring the gap continuously instead of re-discovering it in a generated answer.
In practice
From a document to an enforced state, in four steps.
How a Copilot privacy policy becomes something you can measure in 1Security.
- 01
Map what Copilot can read today
Open Sites, filter to Copilot enabled + with sensitive info, sort by detections. Open Agents to see every Copilot agent employees built or installed, with its reach in files, sites, users and emails and a sensitive-data flag. Together that is the list of places where the policy and reality disagree - typically 30-80 sites and a handful of agents nobody had on a list.
- 02
Constrain what the policy forbids
Declare the policy in the product: mark the sensitive types it names - HR data, payroll, health records - as no-AI-access, and every agent, app and user still reaching them becomes a listed violation, with the declaration on record. Then enable the suggested automations: block Copilot org-wide search on the sensitive sites, expire the anyone and organization-wide links, and work the violations down. Each stages a proposal per resource behind a 72-hour review window before anything changes.
- 03
Measure the policy as a number
The prebuilt "Sensitive Data Exposure to Copilot" trend counts exposed sensitive files week over week, and Sensitivity Labels shows real label coverage per label - so "our privacy policy is enforced" becomes a chart the privacy office can put in a report, not a paragraph you hope is true.
- 04
Keep the evidence
Copilot and AI-agent activity are entries in Activity logs, retained for up to three years on standard licenses - comfortably past the EU AI Act's six-month log floor, with a retention attestation in the agent evidence pack. When the DPO or a regulator asks what AI touched and who could reach it, the answer is a filter and an export, not an investigation.


What makes it work
Three parts of the platform behind the policy.
Enforcing the privacy policy runs on capabilities you can read about in depth.
Copilot security
Every AI agent inventoried, its reach quantified in files, sites, users and emails - before rollout, not after the first bad answer.
Explore the feature →SharePoint governance
The sites Copilot indexes, ranked by sensitive content and exposure, with staged site-level automations to block Copilot search where the policy says so.
Explore the feature →Reporting
Label coverage, exposure counts and AI activity as live, exportable numbers for the privacy office and the auditor.
Explore the feature →
FAQ
Common questions.
Is this Microsoft's Copilot privacy policy?
No. Microsoft's own documentation is the authority on how Copilot handles prompts, responses and chat history. This page is about the complementary half: governing what Copilot can read inside your own tenant, which is decided by the permissions you already manage.
Does 1Security itself send our content to an AI?
No. File and email content is streamed into analysis and discarded; only the detection type, match count and confidence are kept, and the matched values themselves are never written to the database. Detection is deterministic, and no third-party AI service sees file content in the default configuration.
Copilot already respects permissions. Why is more needed?
Because the permissions are the problem. Copilot only surfaces what the signed-in user can already view, so the risk lives in years of accumulated grants, links and group memberships. Enforcing a privacy policy means fixing that reach, and fixing it needs a map of it.
Do we need a premium license or Purview for this?
No. Sensitive-data detection is 1Security's own engine, on standard Microsoft 365 licenses. If you run Purview, its labels and detections are synced in and shown alongside, and the coverage gap is measured against them.
The 1Security platform
Copilot Privacy Governance is just the beginning
Copilot Privacy Governance is one screen of the 1Security platform for Microsoft 365. Locations, devices, apps, AI agents, logs, permissions, sensitive data, compliance, reports and actions run on the same read-only connection, on the licence you already have.
- Activity logs and forensicsUp to three years of searchable activity on a standard licence. What was opened, downloaded, shared, by whom, from where, on which device.


- Anomalies and detectionsSpikes in sharing, downloads, sign-ins, consent and agent activity, scored against each tenant’s own pattern, with curated response actions.


- Permissions and sharingWho can reach what, through which group, link or guest, and whether anyone meant it. The sharing map every audit asks for.


- Sensitive dataPersonal data, credentials, financial and health records found by our own classifiers, with a Microsoft second opinion where the client has it.


- Sensitivity labelsLabel coverage and gaps across sites and files, so the protection the client paid for is actually applied.


- Files, sites and the column browserBrowse the tenant like a file system: site, library, folder, file, with the permissions and sensitivity of each level beside it. A problem solved in itself.


- Microsoft 365 Alerts ToolOne alert model across policies, activity and anomalies - with the evidence attached and the alert threshold in your hands.
- Microsoft 365 Monitoring ToolReal-time monitoring that catches a mass download while it is unfolding - across users, files, apps, AI agents and devices.
- Copilot Security ToolEvery AI agent's real blast radius - quantified before rollout, watched and constrained after.
- Shadow Device DetectionEvery device touching your data, reconstructed from real activity - including the machines that never enrolled anywhere.
- Impossible Travel DetectionLocations as identities, not IPs: country, city and network for every action, first-seen origins, travel timelines with verdicts - no E5, no P2.
- Conditional Access MonitoringDeclared Conditional Access compared against observed sign-ins: coverage verdicts, ungoverned traffic share, and the ranges your offices outgrew.
- Office 365 Access ManagementEffective access, resolved - who can reach what, through which grant, and one place to take it away.
- SharePoint Governance ToolEvery site ranked by exposure and abandonment - links, guests and Copilot access under control.
- Office 365 User ProvisioningLifecycle access from day one to offboarding - reach, dormant accounts and license reclaim in one flow.
- Microsoft 365 Audit ToolUp to three years of searchable activity history - every action tied to an actor, device and location.
- Microsoft 365 Inventory ToolEight live inventories on one permission graph - including the sites, devices and AI agents that were never registered anywhere.
- Office 365 ReportingAnswers, not exports - regulator-grade numbers, saved views and a read-only API for your SOC.
- Microsoft 365 File PermissionsWho has access to any file, and why - people, links, apps and AI agents on one map, with the fix in the same place.
- Sensitive Data DiscoveryWhere regulated data lives and everything that can reach it - two detection engines, no premium licence required.
- Office 365 Email MonitoringOutbound sensitive content, delegated-send abuse and whole-thread evidence that survives deletion.
- Purview Label CoverageWhat your sensitivity labels actually cover, and which of them protect anything at all.
- AI Agent InventoryEvery agent in the tenant with its real reach counted, its blueprint reviewed, and guardrails you can verify.
- AI Data RestrictionDeclare a data type off-limits to AI and every agent, app and user still reaching it becomes a live violation - recorded for the auditor.
- AI Spend TrackingInteractions, Copilot credits and Azure tokens in one ledger per agent - with the spend column next to what each agent can reach.
- Microsoft 365 User Access ReviewEvery identity with what it can reach, what it did, and whether it should still exist - including SharePoint-only guests that live outside the directory.
- Group Access AnalysisWhat membership in a group actually unlocks - nesting resolved, external members surfaced, blast radius counted.
- App and OAuth Consent GovernanceEvery app with a foothold in the tenant: how it got in, who let it in, and what it can actually read.
- Remediation AutomationFindings become fixes at tenant scale, counted before you enable them and staged behind a review window.
- Microsoft 365 Licence OptimizationThe seats you pay for and nobody uses - unassigned units, licences on guests, and dormant accounts still billing.
- Microsoft 365 Anomaly DetectionEvery policy, user, app and agent measured against its own baseline - with an alert line you move and see the answer to at once.
- Office 365 Sign-in LocationsEvery place your tenant is reached from, with your Conditional Access configuration laid over observed reality.
- Microsoft 365 Unified Audit LogWho did what, when, from where and on which device - retained up to three years on a standard licence.
- SharePoint Site InventoryEvery site, channel site and OneDrive in one list, ranked by external reach, abandonment and what Copilot can read.
- Microsoft 365 Activity AnalyticsThe extremes rather than the averages - a mass download inside the hour, and everything nobody has touched in a year.
- Microsoft 365 Trend TrackingAny number in the tenant followed over time, with the change and the deviation attached - and alerting on the same object.
- Microsoft 365 Compliance MonitoringReadiness for eleven regulations measured from live tenant data - with weekly snapshots and a dated evidence pack per framework.
- Microsoft 365 Security ScoreMicrosoft Secure Score beside the score measured from what actually happens - one worklist ranked by points still on the table.
- External Domain MonitoringEvery organisation your tenant exchanges data with, resolved to a real company - with drift flags and an enforceable verdict per domain.
- All featuresExplore everything
Make the privacy policy true in the tenant.
Connect read-only and see what Copilot can reach today. Then constrain what the policy forbids, with a review window in front of every change - on standard Microsoft licenses.
Or keep hoping the permissions match the document.