Pillar 02, where most firms start
AI enablement and adoption
This page is written for whoever runs IT inside the firm. You have probably already been asked about Copilot licensing, and you have probably already found and already blocked something somebody installed. What follows is what we would touch, what we would not, and why the order matters.
In short
EPX Intelligence prepares the Microsoft 365 estate before Copilot licences land, because Copilot surfaces whatever a user already has permission to see and years of accumulated oversharing becomes visible on day one. We fix the data and permissions first, then handle licensing, then deliver role based training, then measure adoption and report it. The programme arrives with resource attached, so it does not land on an already full backlog.
The failure mode
Copilot rollouts do not fail on the technology. They fail on the data estate and on the training that never happened.
Copilot respects existing permissions, which sounds reassuring until you remember what a decade of quick sharing does to a SharePoint estate. The salary review folder somebody shared to a group in 2019 was effectively hidden by being hard to find. It is not hidden any more. That is the first failure, and it is a data governance problem wearing a technology costume.
The second is treating adoption as an event. Licences get assigned, an all staff session gets recorded, usage spikes for a fortnight and then collapses back to the three people who were already using it. Microsoft retired its standalone Adoption and Change Management specialisation in June 2026 and folded adoption into the Copilot specialisation, which tells you where the industry has landed: adoption is not a separate discipline you bolt on, it is how deployment is measured.
What we do about it
We put readiness before licensing and training before scale. In practice that means a data and permissions assessment first, remediation of what it finds, then a controlled pilot with a defined cohort, then role based rollout by team rather than a firm wide switch.
Written for the IT manager
What we touch, and what we do not
Everything below is scoped and agreed in writing before anything is changed, reviewed with you, and applied in a change window. Nothing is applied first and explained afterwards.
| Area | What we do | What stays yours |
|---|---|---|
| SharePoint and OneDrive | Assess sharing configuration and site permissions, report oversharing, propose and apply remediation. | Site ownership, content decisions, retention policy |
| Sensitivity labels and DLP | Design the label taxonomy with your compliance lead, pilot it, then roll it out with the policy behind it. | Classification decisions, and the policy itself |
| Licensing | Model the seat count, advise on the trial route, assign in a controlled wave. | The commercial relationship and the renewal |
| Entra ID groups | Correct group membership where it is the cause of a permissions problem, with a change record. | Identity architecture, conditional access, MFA policy |
| Endpoints, servers, network | Nothing. We ask questions and we do not make changes. | All of it, with your provider |
| Service desk and support | Nothing. We are not a support contract and we do not want to be. | Your incumbent arrangement, untouched |
The programme brings its own people
You have a backlog that is already unrealistic. The point of bringing us in is that the remediation and the training get done by us, with you steering, so it does not join your queue with a deadline attached.
You are not being audited
We will find things. Most of them will be things you already knew about and never had the time or the authority to fix. Our reports say that, in writing, because the alternative makes you look unprepared for decisions that were never yours.
You can run it after we leave
Documentation, runbooks and the adoption reporting are handed over and walked through. If you cannot maintain it without us, we have built the wrong thing.
The sequence
How a Copilot programme runs
Readiness and baseline
Data estate, permissions, oversharing, licensing position, existing shadow AI usage, and a measured baseline of how long the target workflows take today.
Two to three weeksRemediate and pilot
Fix what the assessment found, stand up labels and policy, then a defined pilot cohort with real work rather than a demo. Measured against the baseline.
Four to six weeksRoll out by role, then report
Team by team, with training written for what that team actually does, then monthly adoption reporting against the baseline so the board sees value and not just seat count.
Ongoing, reviewed quarterlyStraight answers
Enablement questions we get asked
Do we have to change IT provider?
No, working with EPX Intelligence does not require you to change IT provider. We expect there to be an incumbent and an internal team, because that co managed model is the norm at your size and it is the model we designed the practice around. Enablement is bought standalone. It is not a route into a managed IT contract and we will not treat it as one.
Our people are already using ChatGPT. Do we stop them?
Stopping them rarely works and usually just moves the usage onto personal devices where you cannot see it at all. The better sequence is to publish an approved tool list with a usable alternative on it, then enforce. That is why enablement and governance are neighbouring pillars rather than separate products.
What does it cost, roughly?
Readiness is fixed scope and fixed price so you can budget it without a commitment to the rest. The rollout is priced on user count and the state the readiness assessment finds, which is why we will not put a number on this page. We will put one in writing after the discovery call, and it will not move afterwards.
Can we trial Copilot before committing?
Yes, you can trial Microsoft 365 Copilot before committing, and EPX Intelligence would encourage it. Microsoft has partner led trial frameworks aimed specifically at organisations under 300 employees, which covers your band. We can run the readiness work in the trial window so the trial is a fair test rather than a demonstration of your oversharing problem.
Bring your IT manager to the call
Find out what your data estate would look like with Copilot switched on.
A 30 minute discovery call, no proposal attached. We would rather have the person who knows the estate in the room from the first conversation.