Control over AI
Blog
AI governance 6 min read

We have Copilot. Why do employees still use other AI tools?

The organisation has Copilot, yet staff still open ChatGPT, Perplexity and Gamma. What people are trying to get done, and what the organisation decides for each tool.

Abstract sphere above soft waves on the horizon
Quick answer

Employees use other AI tools alongside Copilot because they are trying to get something done for which Copilot is not the obvious choice: a presentation that looks good straight away, research with sources, a longer text or the tool they are used to, with a free account that already existed. That is not disobedience; it is information. The organisation can do three things with it: see which tools are in use, take a decision on each one (allow, allow with a condition, not allow or designate Copilot as the preferred tool) and show that decision when someone opens the tool. The counts then show whether people use the preferred tool.

01

Copilot is strong at Microsoft 365 work, but not the natural tool for every task

02

Habit, speed and a free account that already existed outweigh policy on paper

03

The interesting question is not who ignores the policy but what someone is trying to achieve

04

A decision per tool can also mean designating Copilot as the preferred tool

05

Whether people use the preferred tool shows up in counts per tool, not in names

In a team meeting at a consultancy, a consultant shows a presentation she built in Gamma. The director asks why she did not use PowerPoint with Copilot, since that is what the firm pays for. The answer comes without hesitation: "This was done in ten minutes and it looked right straight away."

That answer is the whole explanation. Employees use other AI tools not because they ignore the policy, but because they are trying to get something done for which Copilot is not the obvious choice at that moment. Reading that as disobedience misses the information it carries.

What are they trying to achieve?

Copilot is strong at the work that happens inside Microsoft 365: summarising an email thread, rewriting a document, reducing a Teams meeting to action points. A lot of work sits outside that, and that is where people turn to other tools.

A presentation that looks good without design work is what Gamma is for. Images and layout are what Canva is for. Research with sources attached is why people open Perplexity. For a long text in a particular tone, or a piece of code, they turn to ChatGPT or Claude, because they know what they will get. And alongside the familiar names are the specialist tools: transcription, legal search, data analysis, each with an AI layer of its own.

Then there is habit. Someone has used ChatGPT in their own time for a year, knows how to phrase a question and has projects and a chat history there. The free account existed before the organisation bought Copilot, and a tool that is already open beats a button you still have to find. Speed works the same way: the chatbot tab is already there, the Copilot pane in Word still has to be opened.

What someone is afterWhere it comes fromWhat it asks of the organisation
A task Copilot does not do wellPresentations, images, research with sources, codeA decision about that tool, not about Copilot
A tool that is already familiarHabit, history, a free account that already existedAn explanation of why the organisation prefers another tool
Speed in the momentThe tab is already openMaking the preferred tool visible at that moment
Better results for a specific taskPeople compare answersBeing honest about where Copilot is not the best option
A feature Copilot lacksA specialist AI layer in a professional toolA decision per specialist tool, with a condition

None of those reasons is unreasonable. They are the reasons people use AI at all: it makes the work easier. The question for an organisation is not how to stop that, but how to deal with it sensibly.

Is it a problem?

That depends on two things: which tool, and which account. Using Perplexity to search public case law is different from pasting a client file into a ChatGPT account under consumer terms, where input can be used for training by default and there is no data processing agreement behind it. The type of account matters more than the name of the tool.

The real problem is usually not the tool. It is that the organisation does not know it is in use, and so has decided nothing about it. That is exactly what shadow AI is: a tool that anyone can start using on their own, that has no decision behind it and that is actually in use. Buying Copilot does not change that, because the decision was about Copilot.

What do you do with it?

First, see which tools are in use. Not through a survey, because people name the tools they remember, but through what gets opened in the browser. A consultancy with Copilot included in its Microsoft licences found eleven AI tools in use after a month. Copilot was at the top, ChatGPT just below it, and Gamma was opened daily in one team. For four of the eleven, nothing had been decided.

Then, a decision on each tool. That does not have to be a ban. The four outcomes are allowed, limited use (with a condition the organisation writes itself, such as "public information only"), no decision yet or not allowed. And every decision comes with the question: which tool do we point to as the alternative? Designating Copilot as the preferred tool is a decision too, and a stronger one than a ban, because it answers what someone was trying to do. If the question is whether to allow ChatGPT and Claude alongside Copilot, read which of ChatGPT, Claude and Copilot to allow.

That decision then has to reach people where it matters: when they open the tool. A policy document on the intranet does not reach them there. A notice in the browser does, with the allowed alternative as the first button and, if the organisation set it up that way, the option to continue anyway. This is what that register looks like, with the decision the organisation took on each tool:

AI register
AllowedUnder reviewNot allowedAll tools
Search by tool, vendor, domain or former name…
1,012 tools
DeepSeek
Critical · 90/100
Not allowed
Otter.aiNew
High · 68/100
No decision yet
Grok
High · 67/100
Not allowed
ChatGPT
High · 62/100
Allowed
Perplexity
Medium · 55/100
No decision yet
HeyGen
Medium · 53/100
No decision yet

Every tool, scored for risk

Over 1,000 AI tools, each scored from Low to Critical. Nothing is approved or blocked until someone decides.

More about AI Governance

BeeSensible links a catalogue of over 1,000 AI tools to the use observed in the organisation, and an admin records the decision for each tool, including the alternative the notice points to. The usage data contains only the tool's domain, at most once per day per device, without a user ID or any content. The product page covers what else the module does.

How do you see whether people use the preferred tool?

From the counts, and only from the counts. The share of AI use that runs through allowed tools, and its trend. How often a tool that is not allowed is still opened. How often people pick the alternative after a notice, and how often they continue. Those are figures about the organisation, not about people, and they tell you whether the decision is working in practice.

If the share through Copilot rises after you designate it as the preferred tool, the choice is working. If Gamma is still opened every day, that is not a discipline problem but a sign that Copilot is not an alternative for that task. What comes next is a decision about Gamma, not a sterner message about Copilot.

Blocking looks like the shortcut, but it is not. It moves the use to personal devices and accounts, and the very visibility you needed in order to decide goes with it. The wider decisions around Copilot, from which version of Copilot to use to who reviews a new use case, are covered in Microsoft Copilot governance; the rest of the subject is covered on the AI governance overview page.

What to do differently from now on: the next time someone shows you a Gamma presentation, do not ask why they did not use Copilot. Ask what Gamma does that Copilot does not. The answer is a decision that still has to be taken.

FAQ

Common questions

Why do employees use ChatGPT when we have Copilot?

Rarely out of unwillingness. Someone is used to ChatGPT, has a free account that already existed, finds the answers better for a particular task or does work that sits outside Microsoft 365. Copilot is strong at email, documents and meetings; for a presentation design or research with sources, people reach for the tool that gets it done fastest.

Is using other AI tools alongside Copilot a problem?

That depends on the tool and the account. Using Perplexity for public sources is different from pasting a client file into a free ChatGPT account under consumer terms. The problem is usually not the tool itself, but that nothing has been decided about it and the organisation does not know it is in use.

Should we block other AI tools to enforce Copilot?

Blocking moves the use to personal devices and accounts, where you no longer see it. A decision for each tool, shown when someone opens it, with Copilot as the suggested alternative, lets employees choose for themselves and gives the organisation figures on whether people take up that alternative.

How do you designate Copilot as the preferred tool?

By recording, for each tool, the decision and the allowed alternative that goes with it. When someone opens a tool that is not allowed, that decision appears in the browser with the alternative as the first button. They can still continue, unless the organisation has set it up so that employees cannot go on to a tool that is not allowed. The preferred tool becomes visible when it matters, rather than in a policy document.

How do you see whether people use the preferred tool, without tracking employees?

By counting per tool, not per person. How often each tool is opened, what share of AI use runs through allowed tools and how that share moves over time. Those figures contain no user ID and no content, and they are enough to see whether the decision is working in practice.

Portrait of Rens Timmermans from BeeSensible

Prefer someone to walk you through it?

Rens, BeeSensible

I'm happy to give you a twenty-minute tour. Leave your details and I'll find a time that suits you. You're also welcome to call or email.

Prefer to talk to someone first?

Want a live demo, or a quote for 100+ users? Leave your details and we'll be in touch within one working day.