Find out what Copilot would surface before you switch it on

Copilot does not grant anyone a single permission they did not already have. It just makes what they already had very easy to find, which is why the permissions work belongs before the licences and not after.

Request this assessment
Free45 minutes, plus a written readiness summary within three working days
Why oversharing matters, and how we get Copilot ready, safe and actually used. Plays from YouTube. Nothing is requested from YouTube, and no cookie is set, until you press play. Read the transcript

Who books this

  • Somebody has asked whether Copilot is safe to turn on
  • You have licences ready and have not rolled them out
  • Nobody has reviewed sharing, guests or site ownership in a couple of years
  • You are in a regulated sector and need to evidence the decision

What you get

  • What Copilot would be able to surface across your tenant as it stands
  • The oversharing and site-ownership gaps that matter, ranked
  • A straight answer on whether to proceed, pilot narrowly, or fix first
  • What to label and restrict before anyone gets a licence

What we need from you

  • Read access to Microsoft 365 sharing and site configuration
  • A sense of which sites hold the sensitive material, however informal
  • Whether anyone owns SharePoint governance today, or whether it has drifted
Or do it yourself, free

You do not have to book anything to get an answer. The full written assessment is on this site, and it lets you score your own Copilot readiness across four dimensions in about thirty minutes.

When not to book this

If your tenant is small, tightly permissioned and somebody actively owns sharing, you can probably switch it on and watch. This earns its place where nobody is certain what is shared with whom, which is most estates over about three years old.

Other assessments

  • Microsoft estate review: Forty-five minutes and a written summary. What you are licensed for, what is switched on, where the gaps are, and what we would fix first.
  • Security posture review: Most of what we find is not missing products. It is features you already pay for that were never switched on. Forty-five minutes to find out which.
  • Cloud cost review: Non-production running around the clock, orphaned resources nobody decommissioned, and licences still assigned to leavers. Forty-five minutes to quantify yours.
Show all 12 assessmentsShow fewer assessments
  • Cyber Essentials readiness check: The five control themes, checked against what you actually run. Most first-time failures are the same handful of things, and all of them are cheaper to fix before you apply.
  • Application compatibility assessment: Migrations do not stall on operating systems, they stall on a handful of applications nobody can account for. This sorts your estate into the four groups that actually matter, before you commit budget to any of it.
  • Virtual desktop review: Whether you are choosing between Azure Virtual Desktop and Windows 365 or already running one and paying more than you expected, this is the same review: what the estate is doing, what it costs, and what it should cost.
  • Backup and recovery review: Everyone has a backup. Far fewer have a restore. The question worth answering is not whether jobs are running, it is when somebody last proved one and how long the business would be down.
  • Application and reporting discovery: Most bespoke software goes wrong at scoping rather than in the build, and the most valuable thing a first conversation can do is establish whether you should be commissioning software at all.
  • Endpoint and Intune review: Not whether Intune says the estate is compliant, but whether that means what you think it means: what is enrolled, what has gone quiet, which policies are actually winning, and what you could prove if somebody asked.
  • DfE digital standards baseline: Sixty minutes against all twelve DfE digital and technology standards, the six core ones first. You get a governor-ready summary of where you stand and a dated plan for each gap, whether or not anything else follows.
  • RDS health check: Connection Broker, Session Hosts, Gateway, Web Access, licensing, profiles and load balancing, reviewed as one estate. You get an executive summary to take to budget approval, the technical findings with their root causes, and a rectification path in the order we would do it.
  • Kemp LoadMaster health check: Load balancers are the classic forgotten appliance. We review your LoadMaster's configuration backup and logs offline, so nothing connects to or changes the appliance, and you get a written report on its health with the evidence behind every finding.