Supporting technical capability

Check Microsoft 365 data access before your Copilot rollout.

Review SharePoint and OneDrive permissions, find sensitive content shared too broadly and prioritize corrections. You receive access findings and a plan for the changes needed before the Copilot pilot.

Illustrative sample · supporting capability

Can an unrelated pilot user open the same sensitive file?

CONSTRUCTED EXAMPLETechnical record
Constructed access check · project budget
Observation
A project member and an unrelated user can both open the budget through a broad sharing group.
Decision
Record an access finding before pilot expansion.
Next action
Identify the sharing path and owner; scope permission correction and repeat both user tests.

This capability can inform the next service. Its inclusion, price and calendar must be agreed in that service’s scope; following the link does not make it included.

Explore the relevant next service

Technical context

When this work applies

  • A Copilot rollout is on the table and nobody can say what it would expose.
  • You cannot list who can open your HR and finance files today.
  • You need written proof of what is exposed before you approve switching AI on.

Possible outputs

Outputs to agree in scope

Copilot Oversharing Trace + Exposure Heat Map

Where sensitive data sits, who can already reach it, and which locations Copilot would draw on, risk-ranked by site.

Copilot-readiness verdict

A straight verdict you can act on: go ahead, go ahead with limits, or wait until the sharing is fixed.

90-day implementation plan

The oversharing to close first so Copilot can stay on, scoped to what each role should see.

Commercial & delivery basis

The scope and conditions of the work.

Delivery window

This supporting capability has no separate confirmed delivery window. The proposal names its scope and calendar.

How engagements are scoped
Capability scope to confirm
  • A scan of where sensitive files sit and who can open them today
  • A check of what is shared company-wide or with outside guests
  • Copilot-readiness verdict
  • 90-day implementation plan
Scope assumptions
  • Microsoft 365 files and sites only
  • No review of the contents of the files, only of who can open them
Exclusions
  • Hands-on fixes to the exposure (scoped separately)
  • Copilot licensing or deployment
Required access
  • Read-only access to SharePoint, OneDrive, and Teams sharing permissions
  • A list of the sites and folders holding your most sensitive files
  • A 30-minute kickoff with a data owner

Acceptance

The agreed completion standard.

The engagement is complete when the exposure heat map, readiness verdict, and implementation plan are delivered and walked through.

Discuss the work

Tell us what you need to change.

Share the systems involved, why the change is needed and your deadline. We clarify the work, responsibilities and information needed for a proposal.

Discuss this project