Microsoft Copilot Implementation

Copilot works on what your files already say it can see.

Microsoft 365 Copilot reads whatever your permissions already allow, which is why the first job is finding out what that actually is. We run a readiness check, fix the oversharing it turns up, then licence, roll out and build the Copilot Studio agents worth having. Training from £1,200 a day, readiness check at the audit price.

  • Permissions checked before Copilot goes live
  • Copilot Studio agents built for real Teams and Outlook use cases
  • Adoption measured against the per-user licence cost
The problem this solves

Copilot is not the risk. What it finds already sitting in SharePoint is.

Microsoft 365 Copilot does not have its own idea of what you should see. It reads with your existing permissions, at speed, across every site and every old share it can reach. Most SharePoint estates that have grown for a decade have folders shared "with everyone in the company" that nobody remembers opening up, and Copilot will happily summarise them for the first person who asks the right question.

A proper rollout starts by finding that oversharing and closing it, then licenses the tool per user, and only after that builds the Copilot Studio agents and Teams or Outlook habits that make the licence worth paying for.

What we do

Permissions first, then the rollout that sits on top of them.

The Copilot add-on is billed per user, on top of an existing Microsoft 365 licence, so the cost is visible from day one.

A readiness check

We review SharePoint and Teams permissions for the oversharing Copilot would otherwise surface, and hand over a fixed list of what to close before any licence goes live.

Fixing the oversharing

Site by site, the shares that should never have been open are locked down, so Copilot answers from what people should see rather than everything technically reachable.

Licensing and rollout

The Copilot add-on assigned by role rather than blanket-purchased, so the spend matches who will actually use it.

Copilot Studio agents

Purpose-built agents inside Copilot Studio for a specific job, an IT helpdesk triage, a policy lookup, a meeting-follow-up drafter, rather than the general assistant left to find its own uses.

Teams and Outlook use cases

Meeting summaries, email drafting and document search set up around real work, with a short session so people know when Copilot is actually the fastest route.

Adoption measured

Usage checked against the per-user cost at 30, 60 and 90 days, so unused licences are found and reassigned rather than quietly renewed.

How a rollout runs

Permissions fixed before the licence goes live.

  1. 1

    Readiness check

    A structured review of SharePoint and Teams sharing, producing a fixed list of what needs closing down before Copilot can see it.

    Week 1–2
  2. 2

    Fix the sharing

    The list is worked through with whoever owns IT or the Microsoft tenant, typically your existing provider rather than us.

    Week 2–3
  3. 3

    Licence and roll out

    Seats assigned by role, admin settings configured, and a short training session for each department.

    Week 3–4
  4. 4

    Build the agents worth having

    One or two Copilot Studio agents built for a defined job, tested, and handed over documented.

    Week 4 onward

Not sure which of these fits? Twenty minutes on a call usually settles it.

Why permissions come first

A readiness check finds the folder before Copilot does.

Every SharePoint estate we have reviewed has had at least one site shared more widely than anyone intended. Copilot does not create that risk, it just makes it fast to find, which is exactly why the check has to happen first, not after the first awkward question in a meeting.

  • Site and library permissions audited against who should actually have access
  • Old "everyone" links and stale guest access identified
  • A fixed remediation list, not a vague warning
  • Re-checked before Copilot is switched on for the business
Fit

Who this is for, and who it is not.

A good fit

  • A UK business already on Microsoft 365, considering or holding unused Copilot licences
  • A SharePoint estate that has grown for years without a permissions review
  • A director who wants a defined use case per department, not a blanket rollout
  • Interest in Copilot Studio agents for a specific job

Not this, yet

  • You are not on Microsoft 365, this is specific to that ecosystem
  • You want a customer-facing chatbot, that sits under AI Chatbot instead
  • Nobody will own the Copilot Studio agents once built

Not sure which of these fits? Twenty minutes on a call usually settles it.

Where it earns its cost

The uses worth the per-user licence.

Usually worth itOften not
MeetingsSummaries and action points from Teams callsMeetings nobody rereads notes from anyway
EmailDrafting replies from a known context in OutlookShort internal messages faster to type directly
Document searchFinding and summarising across a tidy, permissioned SharePointA SharePoint estate too messy to trust the answer
Custom agentsA defined job in Copilot Studio with a clear ownerA general assistant with no specific task

This is our honest read from rollouts we have run, not a guarantee. A messy SharePoint estate is the single biggest reason Copilot disappoints.

Straight answers

Questions people ask before they book.

What does Copilot actually cost?

Microsoft 365 Copilot is billed as a per-user add-on on top of an existing Microsoft 365 licence. The exact rate is set by Microsoft and changes; we help you decide how many seats to buy and for whom, not what Microsoft charges.

What is the oversharing problem, exactly?

Copilot reads with the permissions each user already has. Where SharePoint sites or Teams have been shared more widely than intended, over years, Copilot can surface that content quickly and clearly, which is why we check permissions before it goes live.

Do you fix our SharePoint permissions yourselves?

We produce the fixed list from the readiness check and work through it with whoever administers your Microsoft tenant, usually your existing IT provider. Where nobody internal can do it, we can carry that work as part of the rollout.

What is a Copilot Studio agent?

A purpose-built agent inside Microsoft's Copilot Studio, scoped to one job such as an IT helpdesk lookup or a policy question, rather than the general Copilot assistant left to find its own uses.

How is adoption measured?

We agree the tasks the rollout targets, then check usage against the per-user cost at 30, 60 and 90 days, so licences nobody is using get found and reassigned rather than renewed automatically.

How is this priced?

A Copilot readiness check is priced as our standard audit, from £1,500. Rollout and training are billed by the day, from £1,200. A Copilot Studio agent build starts from £4,500.

We already use ChatGPT or Claude, why also Copilot?

Copilot's advantage is depth inside Microsoft 365, Teams, Outlook and SharePoint specifically. Many businesses run it alongside another model for general work; we help decide which tool does which job.

Check what Copilot would find before you switch it on.

A 30-minute call on your current Microsoft 365 setup and whether a readiness check should come before any licences are bought.