Copilot readiness assessment
What will Copilot find on day one that you did not know was there?
In a typical tenant an ordinary account can open hundreds of thousands of files, and dozens of sites hold card numbers, IDs or payroll data behind links anyone in the company can follow. Copilot honours every one of those permissions. 1Security scans your tenant read-only, ranks the sites Copilot would read by sensitive content and exposure, and - once you turn write access on - revokes, blocks or grants that access behind a review window, before the licenses go out.
The problem
The rollout is decided. Nobody can describe what Copilot will see.
The business wants Copilot this quarter, and security is asked to sign off on a tenant nobody has mapped: sites from projects that ended in 2022, sharing links from 2023, groups nested inside groups. Copilot does not break your permissions - it reads exactly what the signed-in user can already open. The permissions are the problem.
What we see on the first scan is consistent: a typical user can reach hundreds of thousands of files, most tenants hold several times more sites than IT believes they have, and 20-40% of the files with sensitive content carry no sensitivity label at all. Every one of those files is one plain prompt away from a summary on somebody's screen.
Assessing that by hand means months of per-site reviews that are stale before they finish. The assessment has to come from the tenant itself: what would Copilot read, where is the sensitive data concentrated, and which of it is exposed further than anyone intended.
And by the time the licenses go out, Copilot is rarely the only agent in the tenant. Agents built in Copilot Studio, agents from Azure AI Foundry, agents that arrive with a third-party SaaS tool - each inherits somebody's permissions exactly the way Copilot does. Readiness stopped being "what will Copilot read" and became "what can anything with a model behind it reach, and who is on the other side of it".
In practice
From read-only consent to a go decision in four steps.
The whole assessment runs on read-only consent and standard licenses - first numbers the same day.
- 01
Connect read-only and let the scan run
One consent, no agent, nothing installed. The inventory of sites, files, users and groups starts filling the same day, and 1Security's own engine scans content for 300+ sensitive information types - no E5, no Purview deployment required. Sensitive Info shows what has been found and how many files, sites and users can reach each type.
- 02
Rank the sites Copilot would read
Open Sites, filter to Copilot enabled + with sensitive info, sort by detections. Every row shows storage, external users, sharing links and how many people can enter. In a mid-size tenant this list is typically 30-80 sites - the exact places an AI answer could go wrong, in order.
- 03
Stage the cleanup before rollout
Enable the suggested automations - block Copilot org-wide search on externally exposed sensitive sites and on abandoned sites, expire the anyone links on files with sensitive content - and 1Security stages a proposal per site behind a 72-hour review window, with owners able to object before anything changes.
- 04
Keep the gate closed after rollout
The prebuilt "Sensitive Data Exposure to Copilot" trend counts the exposed sensitive files week over week, and the Agents screen carries every agent employees build or install - Copilot Studio, Foundry, Entra Agent ID and third-party - with its reach in files, sites, users and emails and an anomaly baseline of its own: today's activity scored against the agent's own last 30 days, so a spike becomes an episode within minutes. Add Microsoft Agent 365 later and those agents join the same inventory with nothing to reconfigure.
From assessment to control
The assessment ends in a change, not in a report.
Ranking the sites Copilot would read is the measurement. What follows is always one of three decisions - leave it, close it, or hand the access out properly - and all three are one action away from the row you are already looking at.
Revoke the grant, the nested membership or the anyone-link behind an exposed site. Block Copilot org-wide search on it, close its external sharing, expire its links, or disable sign-in for the app an agent runs through. Or declare a sensitive type off-limits to AI and work down the listed violations. Or grant what somebody legitimately needs, scoped to one site instead of the whole tenant.
Write access is a separate consent - the assessment itself never needs it. Every action is staged as a proposal inside a review window, 72 hours by default, and can be routed to the owner of the resource, who answers in their own restricted portal. Silence applies it; everything that ran sits in one audit trail with who approved it and when. Declared restrictions, oversight status and log retention roll up into a per-agent evidence pack mapped to EU AI Act and NIS2 articles - so the readiness assessment doubles as the start of the compliance file.
What makes it work
Four parts of the platform behind the assessment.
The assessment is not a separate product. Everything below keeps running after rollout.
Copilot security
Every AI agent in the tenant, from every source, inventoried in one place, with its reach measured in files, sites, users and emails before employees start chatting with it.
Explore the feature →SharePoint governance
The Copilot-enabled flag, sensitive-info counts, external users and sharing links per site - the columns the readiness ranking is built from.
Explore the feature →Access management
Effective access resolved through groups, links and inheritance, so "what would Copilot read for this user" has an exact answer, not an estimate.
Explore the feature →Agents beyond Copilot
Copilot Studio, Azure AI Foundry, Entra Agent ID and third-party agents in one inventory - each with its reach resolved to content, its owner, and an anomaly baseline of its own.
See it next to Agent 365 →
FAQ
Common questions.
Do we need E5 or Purview to run the assessment?
No. 1Security detects 300+ sensitive information types with its own engine, including OCR for scans and screenshots, on a Microsoft 365 Business Basic license upward. If you already run Purview, its detections and labels are synced in and shown right next to ours.
Does 1Security change how Copilot behaves?
Only where you tell it to. Blocking Copilot org-wide search per site and expiring sharing links are staged automations under the separately consented write module, each with a review window. Everything else is read-only measurement.
Does the assessment cover agents our own teams build?
Yes. Copilot Studio agents, declarative Copilot agents, Azure AI Foundry agents, Entra Agent ID identities and third-party SaaS agents all land in the same inventory, each with the files, sites, users and mailboxes it can reach and an anomaly baseline of its own. The ones nobody registered are usually the surprise.
Can 1Security close what the assessment finds?
Yes, once you turn write access on - a separate consent the read-only assessment never needs. Revoking a grant, expiring links, closing external sharing, blocking Copilot org-wide search on a site or granting scoped access are all staged as proposals inside a review window, optionally routed to the resource owner, and recorded in one audit trail.
How long until we have numbers?
The same day. The site ranking, the reach counts and the label coverage gap update continuously as the scan proceeds. Large tenants keep scanning in stages for weeks, but the top of the list is usually right within hours.
How does this relate to SharePoint Advanced Management?
They work together. SharePoint Advanced Management gives you site-level reports and controls inside SharePoint. 1Security adds what is inside those sites, the people, apps and AI agents that can reach them, and stages the fix - on standard Microsoft 365 licenses.
The 1Security platform
Copilot Readiness Assessment is just the beginning
Copilot Readiness Assessment 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.
- AlertingInstant and digest channels per client, routed to the right people, themed under your brand or theirs.


- Trends and the daily briefWhat moved this month, what needs a decision today, ranked, for the client meeting and for your own morning.


- LocationsWhere every sign-in and every action really comes from, on a map, per tenant. Breaches by location, impossible travel, allow lists per person. Works without premium sign-in logs.


- DevicesRegistered, unregistered and shadow devices, attributed from activity rather than from an agent. The device nobody enrolled still shows up.


- Apps and consentEvery app with access to the tenant, what it can reach, who consented, and whether it still needs to.


- AI agents and CopilotThe agent registry: owners, reach, who each agent acts as, what Copilot will see. The EU AI Act checks per agent, accountable owner, instruction transparency and impact assessment, measured from the tenant. Readiness before the licences, governance after.


- 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
Assess it on your tenant, not on a slide.
Connect read-only and see the sites Copilot would read ranked by sensitive content and exposure - the same day, before the licenses go out. Then close what it finds, staged behind your own review window.
Or sign off on a permission state nobody can describe.