We Already Use Copilot. Do We Need Anything Else?
On this page
For a lot of UK businesses, Microsoft Copilot is enough, as long as the work lives inside Microsoft 365 and a person asks for it each time. You need something more when a task has to run on its own, or has to change records in systems Microsoft doesn't own without a person asking for each one.
That's the short answer to a question that usually arrives as a reason to stop talking about AI altogether. "We already use Copilot" is a fair thing to say. Most mid-market businesses already pay for Microsoft 365, and Copilot is the AI that sits closest to how their people work. The more useful question is which parts of your work it covers, and which parts it was never designed to touch.
Three questions will tell you whether it's enough for a given job, and there's one piece of housekeeping to do before any of it works safely. Every claim about Copilot's features below is as of November 2026, and Microsoft changes the line-up often, so check its own pages before you buy.
What is Microsoft Copilot good at?
Copilot is good at the work one person does in front of a screen. It summarises a long report, drafts an email, pulls the actions out of a Teams meeting you missed and rewrites a document in a different tone. For a lot of knowledge work, that is exactly where the minutes go.
The UK government has tested this more carefully than most buyers ever will. In the cross-government Copilot experiment, published in June 2025, 20,000 government staff used Microsoft 365 Copilot for three months and reported saving an average of 26 minutes a day. That figure is self-reported. People picked a range in a survey and the report used the middle of each range, so it tells you how the tool felt to use rather than what it measurably changed.
The Department for Business and Trade went further. Its evaluation, published in August 2025, used a control group and timed tasks. Copilot users summarised reports in around 13 minutes against around 42 for people without it, and their summaries were more accurate. The report is careful to say its timed samples were small.
That pattern is worth holding onto. Copilot makes a person quicker at the task in front of them. Whether the business gets anything back depends on what happens to the time it saves, and on whether the task was the expensive part of the work in the first place.
I've written before about the difference between AI inside your tools and AI working across them. Copilot is the best example of the first kind that most businesses will ever own, and for plenty of them that is the right place to be.
Which Copilot does your business actually have?
"We use Copilot" can mean two quite different things, so this is the first thing to check.
Copilot Chat comes with eligible Microsoft 365 plans at no extra cost. Microsoft describes it as web-grounded. Its own documentation says it can only work with your company's content when you upload a file with your prompt or have the email or Teams chat open, unless you add a pay-as-you-go agent. It won't go and find last quarter's proposal in SharePoint for you.
Microsoft 365 Copilot is the paid add-on. It grounds its answers in your emails, files, meetings and chats through Microsoft Graph, and it puts Copilot inside Word, Excel, PowerPoint and Teams. This is the version most people picture when they hear the name.
On top of the seat, some newer features and agents are billed by usage, in what Microsoft calls Copilot Credits. Prices and bundles change through the year, so Microsoft's UK pricing page is the place to check rather than a figure in a blog post. Microsoft has also been renaming parts of the line-up during 2026, which makes it worth asking your IT lead which licences your people actually hold.
Three questions that tell you whether Copilot is enough
Take the jobs that cost your team the most hours each week and ask three things about each one.
1. Does the work live inside Microsoft 365?
If the inputs and outputs are emails, Word documents, spreadsheets and Teams meetings, the paid Copilot can reach them. That covers a lot of office work.
Plenty of important work lives elsewhere, though, in a CRM, a job management system, a finance package or a supplier portal. Microsoft offers prebuilt Copilot connectors to systems such as Salesforce, ServiceNow and Jira, which let Copilot search their data alongside your files. Grounding Copilot in connector data needs the paid add-on, not the free tier.
So the first question is really whether Copilot can see the information the job depends on. If it can, you're in good shape. If the information sits in a system without a connector, someone has to build one.
2. Does a person ask for it, or does it have to happen on its own?
Copilot answers when someone asks it something. Many of the jobs that cost a team the most time don't start with a question. They start with an event, such as a new enquiry arriving, a form being submitted or a file landing in a folder, and someone has to notice it and act.
Copilot Studio, Microsoft's tool for building agents, can respond to events like these with what it calls event triggers. Microsoft's documentation on triggers sets out the current terms plainly. Triggered agents run on the credentials of the person who built them. Trigger activity uses Copilot Credits, and so do the flows it calls, even for people who hold a Copilot licence. Microsoft also recommends keeping a single sequence to fewer than 15 actions, because longer chains can struggle to run reliably.
None of that rules it out. It does mean the job that runs on its own is a piece of build work, with someone responsible for it, rather than a feature that arrives with the licence.
3. Does it need to change a record somewhere Microsoft doesn't own?
Reading a CRM and updating it are different jobs. Moving a deal to the next stage, creating a job, booking a delivery or raising an invoice all mean writing to another system.
Copilot can now do some of this itself. Microsoft's federated connectors, which cover apps such as HubSpot, Xero and Notion, can create, update or delete records where the connector provides the tools for it. A person asks, Copilot shows the change, and nothing happens until that person approves it. If your systems are on the list, a one-off update no longer needs anything built.
That still leaves the update that should happen on its own, the system with no such connector and the change that has to land in several systems in the right order. Those need an action built for the purpose, such as a Power Platform connector, an API connection or an MCP server. Microsoft's own example is a sales agent that reads Salesforce through one connector and updates records through another. It works, and it is also a build. Someone has to design it, decide where a person checks it, test it against real cases and keep it working when the other system changes.
If all three answers keep you inside Microsoft 365, with a person asking, Copilot is very likely enough. Each answer that points outside it is usually a piece of work Copilot won't do by itself. That's a reason to plan the work properly rather than a reason to doubt Copilot.
What will Copilot show your team?
Before any of this pays off, there's a job that catches a lot of businesses out. Microsoft is clear that Copilot only shows people what their existing permissions already let them open. It doesn't create new access. It does make old access very easy to find.
Think of the salary spreadsheet in a folder that was shared with everyone in 2019, the board pack someone saved to the wrong site or the HR file that inherited the wrong permissions. None of them were a problem while nobody went looking. Once anyone can ask a question in plain English, they turn up as answers.
That's why Microsoft's own deployment blueprint for Copilot starts with remediating oversharing. The Copilot licence includes SharePoint Advanced Management, which helps find overshared and sensitive sites, and a setting called Restricted Content Discovery can keep high-risk sites out of Copilot's answers while permissions are tidied. If you're following an older guide that recommends Restricted SharePoint Search, Microsoft is retiring it and stopped new enablement on 31 July 2026.
Gartner analyst Dan Wilson made the same point to a conference audience in June 2025. He said Copilot rollout plans were often built on the assumption of a clean data environment, which is rarely the case. The tidying is real work, and it is better done before people start asking questions than after.
What does needing more look like in practice?
When we built a lead intelligence system for a global biometrics company, every inbound lead needed 30 minutes or more of research, qualification and routing before a rep could reply. The work started on its own whenever a lead came in. It pulled from outside sources and ended in the sales team's systems and inboxes. That's all three questions pointing outside Copilot.
The system now puts a full brief in the right rep's inbox in under 90 seconds, and the reps stay in control of every customer conversation. An assistant waiting to be asked wouldn't have done that, because nobody was asking it anything. The work had to start the moment the lead arrived.
Needing more rarely means replacing Copilot. The assistant people talk to and the workflow that runs underneath do different jobs, and they sit side by side quite happily. Some of that build can happen inside Copilot Studio, especially when the systems involved are mostly Microsoft's. Some of it is better built outside Microsoft, particularly when the CRM, the job system and the finance package all belong to other vendors. Either way, make sure your business owns what gets built, and the questions worth asking about vendor lock-in apply whoever builds it.
When is Copilot the right answer?
Copilot is the right answer more often than you might expect to hear from a business that builds custom AI. If your team's work is mostly documents, email and meetings, if the repetitive part is reading and writing rather than moving information between systems, and if you've tidied your permissions, Copilot is probably the right first step, and you should get it working well before you build anything else.
How you roll it out matters as much as which tool you choose. Microsoft's own 2026 Work Trend Index, a survey of 20,000 people who use AI at work, found that organisational factors such as manager support and culture accounted for more than twice the reported impact of individual ones, at 67% against 32%. That's Microsoft's survey of its own market, so weigh it accordingly, but the point stands. The licence is the easy part, and the change in how the work is done is where the value sits.
Practical takeaways
- Check which Copilot you have. The free Copilot Chat and the paid Microsoft 365 Copilot answer very different questions, so find out which licences your people hold.
- Tidy permissions first. Copilot shows people what they can already open, so find the overshared sites before anyone starts asking questions.
- Run the three questions on your most expensive jobs. Ask whether the work lives in Microsoft 365, whether a person asks for it and whether it has to change a record somewhere else.
- Treat anything unattended or cross-system as a build. Give it a design, a human checkpoint and an owner, whether it lives in Copilot Studio or outside it.
- Measure against a baseline. Time the task before and after, because self-reported minutes saved tell you how a tool feels rather than what it changed. If you'd like a structured way to decide what comes first, the free AI roadmap shows where you stand.
Frequently asked questions
Is Microsoft Copilot enough for a mid-sized business?
Often it is. If most of the work your team wants help with is reading, writing and summarising inside Microsoft 365, and a person asks for that help each time, the paid Microsoft 365 Copilot licence covers it well. It stops being enough when a task has to start on its own, such as every new enquiry being researched as it arrives, or when it has to update records in systems Microsoft does not own without a person asking and approving each change. Those jobs can be built, inside Copilot Studio or alongside it, but a licence alone will not do them.
What is the difference between Copilot Chat and Microsoft 365 Copilot?
Copilot Chat comes free with eligible Microsoft 365 plans and answers mainly from the web. It only uses your work content when you upload a file or have an email or Teams chat open, unless you add a pay-as-you-go agent. Microsoft 365 Copilot is the paid add-on, which grounds its answers in your emails, files, meetings and chats through Microsoft Graph, and adds Copilot inside Word, Excel, PowerPoint and Teams. When someone says the business already uses Copilot, it is worth checking which of the two they mean, because they answer very different questions.
Can Copilot update records in our CRM?
Sometimes. If your CRM has a federated Copilot connector with write tools, such as HubSpot's, Copilot can create or update a record when a person asks and approves the change, using that person's own permissions. Other connectors, including the prebuilt Salesforce one, let Copilot search the data without changing it. Updates that should happen on their own, or that touch several systems at once, still need an action built for them, such as a Power Platform connector, an API connection or an MCP server, usually set up in Copilot Studio. That is entirely possible. It is also a piece of build work with an owner, because someone has to design it, test it and keep it working when the other system changes.
Will Copilot show staff files they should not see?
Copilot only shows people what their existing permissions already let them open, so it does not create new access. What it does is make old access easy to find. A folder shared with everyone years ago becomes an answer to a question rather than something nobody stumbles on. Microsoft's own deployment guidance starts with fixing oversharing for that reason, and the Copilot licence includes SharePoint Advanced Management to help find and tighten overshared sites before or during rollout.
Can Copilot and custom automations work together?
Yes, and in most businesses that is the sensible shape. Copilot stays as the assistant people talk to for drafting, summarising and finding things in Microsoft 365. The automated workflows run underneath, handling the jobs that start on their own or move information between systems. Some of those workflows can be built in Copilot Studio and some are better built outside Microsoft, particularly when most of the systems involved are not Microsoft's. The two do different jobs, so there is rarely a reason to choose one over the other.
Related Articles
Building Your First Intelligence System: What Goes In, and In What Order
How to build a business intelligence system in the memory sense, not the dashboard sense. What goes in first, who owns it, and what a first build costs.
13 min readUK AI Adoption Statistics: Why the Numbers Disagree
UK AI adoption statistics range from 30% to 88% depending on the survey. Why the numbers disagree, which to use, and why depth is the figure to compare.
10 min readHow to Prioritise AI Automation: Knowing What Comes First
Most businesses can list what AI could automate. The hard part is the order. Why your AI roadmap is yours alone, and why it should keep changing.
13 min read