Get more from Microsoft

Copilot will find whatever your people can already reach

That's the whole readiness question in one sentence. If access is tidy and your files are where they should be, Copilot is genuinely useful. If they aren't, it becomes a very efficient way of surfacing the salary spreadsheet somebody shared too widely in 2019.

Why readiness is mostly housekeeping

Copilot doesn't create new permissions. It works within whatever access each person already has — which sounds reassuring until you consider how access tends to accumulate. A site opened up temporarily, a folder shared with the whole organisation to save a conversation, a leaver's files inherited by a team that didn't need them.

None of that causes much trouble while finding things is hard. Search is imperfect, people don't go looking, and the awkward document stays quietly where it is. Introduce a tool that's good at finding things and the picture changes.

The second issue is more mundane. Copilot draws on the content you have, so if the current version of a policy lives in someone's OneDrive alongside four older drafts, the answer it gives will reflect that. Neither problem is a reason not to adopt it. They're just reasons to spend a few weeks on housekeeping first.

Access that grew by accident
Sharing set up years ago for one purpose, still in place and now easy to find.
No single version of the truth
Drafts, duplicates and superseded documents that a tool can't tell apart from the real thing.
Licences bought before a use case
Seats paid for monthly while people work out what they'd actually use them for.

What usually moves the needle

Not everything at once, and not in the order a sales pitch would suggest. This is the sequence most organisations get the most from.

  1. 01

    Look at who can reach what

    Review over-shared sites, organisation-wide links and dormant guest access.

    This is the single most important step, and it's worth doing whether or not Copilot ever arrives. Most tenants have a handful of places open far wider than anyone intended.

  2. 02

    Tidy the content that matters most

    Focus on the areas people will ask questions about: HR, finance, policies, client work.

    You don't need to sort out every file in the organisation. Getting the frequently referenced material into one current version, in one obvious place, covers most of the risk of poor answers.

  3. 03

    Pick a small group and a real task

    A pilot with a specific job to do beats a general rollout.

    Meeting summaries, first drafts of recurring documents, or digging through long email threads are the uses that stick. Handing licences to everyone and hoping usually produces a lot of quiet seats.

  4. 04

    Agree what people shouldn't put in it

    A short, readable guideline rather than a policy document.

    People need to know where the line is on client data, personal information and anything commercially sensitive. One page that someone will actually read is worth more than ten that they won't.

  5. 05

    Review before you buy more seats

    Check what the pilot group actually used before scaling up.

    Copilot licences are a real monthly commitment. Looking honestly at whether the pilot saved time — and for whom — is a much better basis for the next decision than enthusiasm.

Readiness isn't really about AI. It's about knowing who can see what, and that's a question worth answering anyway.

What good looks like

A sensible starting position looks much like a well-run tenant. That's not a coincidence — the groundwork is the same work.

  • You know which sites and folders are open wider than intended.
  • External sharing and guest access have been reviewed recently.
  • Key documents exist once, in a current version, where people expect them.
  • A small group is using it for a task they'd otherwise do by hand.
  • Everyone knows what shouldn't be typed into it.
  • The decision to buy more seats is based on what happened, not what was hoped for.

How we help

We help organisations work out whether they're ready, and what readiness would actually involve for them. Usually that's a review of access and sharing, a look at where important content lives, and an honest conversation about which teams have a job Copilot would genuinely help with.

Sometimes the answer is that it's too early — the access picture needs work first, or nobody can name a task they'd hand over. We'll say so. Paying monthly for licences that sit unused is an easy mistake to make and an expensive one to unwind.

Where it does make sense, we'll help you start small, keep the guidelines short and review it properly before it spreads.

Questions people ask us

No. You need the access review done and the content people will ask about in reasonable shape. Perfect information hygiene isn't realistic and isn't the bar.

Start with a conversation, not a proposal

Get an IT health check that reviews your support, security and Microsoft setup, then gives you a short, prioritised list of what's worth doing.