Plenty of New Zealand businesses have bought Microsoft 365 Copilot licences expecting a lift in productivity. A few months later the picture is often the same. A handful of people use it to tidy up emails. Someone in finance has stopped trusting it after it quoted figures from an old spreadsheet. Most of the team tried it twice and went back to doing things the way they always have. The licences renew anyway.

None of that means the tool doesn’t work. A stalled rollout almost always comes down to the same few causes, and most of them have very little to do with AI.

The five usual causes

1. Your permissions weren’t ready for it

Copilot answers from the content each person can already reach. Microsoft describes it as grounding responses in the data users already have permission to access, and treats fixing oversharing as the first job before deployment (Microsoft’s Copilot oversharing blueprint).

That sounds safe until you look at how most Microsoft 365 tenants have grown. SharePoint sites shared with everyone. Teams set up for a project years ago and never closed. A payroll folder shared with a link anyone in the company can open.

Before Copilot, overshared files were hard to stumble across. Copilot makes them easy to find. Then one of two things happens: people see things they shouldn’t, or IT locks everything down so tightly that Copilot has nothing useful left to work with. Either way, confidence drops.

2. Nobody owns a use case

“Give everyone Copilot and see what happens” is the most common rollout plan and the least effective. Without a defined job, people use it for whatever comes to mind, get mixed results and decide it’s a novelty.

Teams that get real value usually start with a short list of specific tasks. Summarising supplier contracts. Drafting a tender response from previous ones. Preparing the first cut of a board paper. Finding the current version of a policy. Each task has an owner who cares whether it works.

3. Licences went out without training

Copilot is only as good as the request it’s given. Most staff got a licence and a launch email. They tried a couple of vague prompts, got vague answers and moved on. A short session built around their actual work, using their own documents, changes that quickly.

4. The information underneath is a mess

If your source of truth is three versions of the same spreadsheet in three folders, Copilot will find all three. It can’t tell which one finance actually uses. Old policies, duplicate price lists and draft contracts saved next to signed ones all turn up in answers. AI doesn’t fix messy information. It surfaces it faster.

5. Nobody is measuring anything

If you can’t say what success looks like, you can’t tell whether you’re getting it. Usage reports tell you who opened Copilot, not whether it saved anyone time or made the work better. Without a baseline, the renewal conversation comes down to opinion.

A fix-it plan

You don’t need to start again. This is the sequence we follow when a rollout has stalled:

  1. Talk to the people who stopped using it. Fifteen minutes each with five or six of them will tell you more than any usage report. Find out what they tried, what went wrong and what they’d actually like help with.
  2. Find and fix oversharing. Review permissions across SharePoint, Teams and OneDrive. Remove company-wide links, archive dead sites and put sensitive areas such as payroll, HR, board papers and client files behind proper groups. Microsoft includes SharePoint Advanced Management with Copilot licences, and its Purview tools help find and protect sensitive content. Both are worth switching on.
  3. Pick three use cases, each with an owner. Choose tasks that are frequent, slow and text-heavy, where a good first draft saves real time and a person still checks the result. Write down who owns each one and what better looks like.
  4. Tidy the content those use cases rely on. If the use case is tender responses, clean up the tender library. If it’s policies, archive the old versions. Small, targeted clean-ups beat a company-wide information project that never finishes.
  5. Train around real work. Run short sessions team by team, using their own documents and tasks. Keep the prompts that worked somewhere people can find them.
  6. Right-size the licences. Move licences from people who don’t need them to people who will use them every day. There’s no prize for 100 per cent coverage.
  7. Measure for 60 days, then decide. Track time saved on the chosen tasks, the quality of the output and how often people come back to it. Then expand, adjust or cut.

When Copilot isn’t the right tool

Sometimes the honest answer is that Copilot was the wrong fit for the job. It’s good at working across documents, email and meetings. It’s less suited to questions that need exact numbers from your accounting or inventory systems, or to multi-step processes that must run the same way every time.

For those jobs, a reporting model you trust, an automated workflow or a purpose-built agent connected to the right systems will usually do better. Part of fixing a rollout is being clear about which tool suits which job, and not expecting one product to do everything.

Where to start

If your Copilot rollout has stalled, begin with the permissions review and the conversations with the people who gave up. Both are cheap, and together they usually explain most of the problem. If you’d like a hand, our AI and agents work includes fixing rollouts that haven’t paid off. Get in touch and we’ll tell you straight what’s worth fixing and what isn’t.