How do you get real value from Microsoft Copilot?
Most businesses that have paid for it cannot point to what changed. The answer is rarely the technology, and it is almost never that you bought the wrong thing.
The short answer
Four things account for most disappointing Copilot rollouts. Staff are frequently signed into a different account from the one the business pays for, which from mid-August 2026 happens inside the same app instead of a different one. A work account without a licence gets Copilot Chat, which is grounded on the web rather than on your own files and email. Permissions decide what it can reach, and most tenants have never had those reviewed. And it reads your actual documents, so if those are scattered, duplicated or years out of date, the answers will be too.
None of those is fixed by a better prompt or a different licence. They are fixed by deciding what the thing is for and then setting it up to do that.
Are you using the Copilot you paid for?
Start here, because it is the cheapest thing to check and the most common single cause.
Until now the consumer Copilot and the business one were two separate apps that happened to share a name. From mid-August 2026 they are a single app on mobile and web, with Windows and Mac following from mid-September.
What is not merging is the accounts, and that distinction is worth holding onto. Microsoft is explicit that work and personal accounts remain separate, that data does not flow between them, and that the two are distinct by design. Your organisation's security and compliance controls carry on applying to the work account exactly as they did.
Which makes this harder to spot rather than easier. What decides the assistant somebody gets used to be visible as two different icons. It is now the account they signed in with, in one app, and nothing on the screen announces it.
There are two ways to be in the wrong place and they are worth separating, because they have different fixes. Someone signed in with a personal account is not in your organisation's Copilot at all. Someone signed in with their work account but without a licence is in Copilot Chat, which is grounded on the web rather than on your files and email. The first is a sign-in problem and the second is a licensing one, and both produce the same sentence: it cannot see any of my work, so it is useless. I have watched a team decide exactly that, back when it at least took two apps to get there.
So check which account people are signed in with, and which licence sits behind it, on their actual machines, before spending anything on training or on more licences.
What the licensed one reaches
Worth being clear about, because the rest of this page is about why businesses are not getting it. The advantage is real and it is structural rather than a matter of which model is cleverest this quarter.
Your documents, email and meetings, scoped to what the person asking can already open, with no connector to configure and nothing indexed into a second system. Other tools can be connected to the same content. The difference is how much setup sits between you and it, and who maintains that.
Inside Word, Outlook, Excel and Teams rather than in another tab. That sounds minor and is not: the tools people abandon are the ones that need a context switch before they help.
It is designed to work within your existing permissions and labels rather than adding another place company information lives. That is the right architecture. It is also worth knowing that design intent and guarantee are different things, which is what the January 2026 defect below illustrates.
Microsoft 365 Copilot Chat carries enterprise data protection when people sign in with their Entra work account, so staff experimenting there are not feeding a consumer service. That protection is conditional on the sign-in and on nothing else. A personal account in the same app does not carry it, and once the apps merge there is no longer a separate icon to give that away.
What actually goes wrong
Copilot can surface anything the person asking already has permission to open. It does not break your permissions. It makes them visible, often for the first time. Where sharing has been loose for years, that surfaces quickly and awkwardly. Where it has been tight to the point of nobody being able to find anything, Copilot has nothing to work with. Both are setup problems wearing a technology problem's coat.
The advantage of an assistant inside your tenant is that it can see your content. That is also the limit. Three versions of the same template across two drives, a policy last updated in 2023, a naming convention two people follow: it inherits all of that and answers confidently from it.
The most expensive pattern. Licences are assigned, an email goes round, and nothing else happens. No named job, no owner, no decision about what gets checked. Six months later the renewal comes up and nobody can say what changed.
Worth understanding before you widen anything, and less alarming than it sounds. Agents published to Microsoft 365 Copilot are included for anyone licensed for it. Agents that reach SharePoint or Graph connector content are billed on metered consumption, and Microsoft ships those switched off by default. Copilot Cowork is a third case again: the licence is the entry ticket, usage then bills separately in credits, and an admin decides whether it is available at all. So the question is not whether you will be billed by surprise, it is which of these someone is about to turn on.
Setup first, then the job, then the team
What you actually hold
Which Copilot is licensed, who has it, which account they are signed in with, and whether anything is already included in the plan you pay for.
What it can reach
A look at sharing and permissions before a wide rollout rather than after, so the first thing it surfaces is not something awkward.
One job, made repeatable
A named piece of work it does the same way twice, inside the app your team already has open, with someone accountable for the output.
Training on that job
On your own work, once the setup is right. Training people on a tool that cannot reach the right content teaches them it does not work.
The thing I say in every one of these conversations
What matters is that AI is applied consistently across the business, so that whatever return you get comes back to the business owner. Otherwise you have a situation where the owner says go and use it, and people go and use it, and they are guessing at what is allowed. They might be leaking private data without knowing.
That is the argument for doing the setup before the enthusiasm, and it applies more inside a Microsoft tenant than anywhere else, because the assistant there can reach real company content rather than just what someone pastes into it.
How an engagement runs is in the Korbai Method, and the training side in Microsoft Copilot training.
Who this is for
Small and mid-sized Australian businesses running on Microsoft 365, where someone has already paid for Copilot and cannot point to what changed. Usually professional services: accounting, legal, property, advisory. The common thread is a business with real documents worth reading and no one whose job it is to make the tool read them well.
If nobody has bought anything yet, that is a better position to be in, and the honest first question is whether the plan you already hold covers it. See which AI platform should your business use, which mostly argues that the platform matters less than what you do with it.
Questions we get asked
Why is Microsoft Copilot not working for us?
Work through it in order, cheapest first. Check which account people are signed in with and which licence sits behind it, because a personal sign-in is not in your organisation’s Copilot at all, and a work sign-in without a licence gets Copilot Chat, which is grounded on the web rather than on your files and email. No amount of training changes either. Then check what it is allowed to reach. Then look at the state of the documents themselves. Most rollouts fail at the first step and get diagnosed at the third.
Microsoft is merging the Copilot apps into one. Does that end the confusion?
It moves the confusion rather than ending it. The consumer and business apps are becoming a single Microsoft Copilot app, on mobile and web from mid-August 2026 and on Windows and Mac from mid-September. The accounts are not merging with them. Microsoft is explicit that work and personal accounts remain separate, that data does not flow between them, and that the two are distinct by design, with your organisation’s security and compliance controls continuing to apply on the work side. So what decides which assistant someone gets is now the account they signed in with rather than the icon they tapped, and nothing on screen announces it. Separately, the Copilot name still covers the assistant embedded in Word, Excel, Outlook and Teams and a builder for making your own, which are different products again.
Do we already have Copilot in our Microsoft 365 plan?
Possibly, and it is worth checking rather than assuming. Microsoft sells Copilot two ways: bundled into some business plans, and as a paid add-on to others. Which you have depends on the plan you bought and when. On agents, the line runs differently from where people expect: agents published to Microsoft 365 Copilot are included for anyone licensed for it, while agents that reach SharePoint or Graph connector content are billed on metered consumption, and Microsoft ships those switched off.
What is Copilot Cowork, and would we already have it?
Cowork went generally available worldwide in June 2026, and a Microsoft 365 Copilot licence is the entry ticket rather than the whole answer. Microsoft is direct about the rest: "Cowork is off by default. Admins decide when to enable Cowork in their tenant and who gets access." Usage then bills separately from the licence, in Copilot Credits at a cent a credit on pay-as-you-go, and the cost of a single task comes from four things: model use, context retrieval, tool calls and runtime. So the same instruction can cost different amounts on different days, which is the part most people do not expect. Budgets and per-user caps are available, and they are worth setting before anyone is invited in rather than after.
Can Copilot see files our staff should not have access to?
It can surface anything the person asking already has permission to open. It does not break your permissions, it makes them visible. In a tenant where sharing has been loose for years, that is often the first time anyone notices. Review sharing before a wide rollout, not after.
Is Copilot safe for client information?
It turns on the account rather than the app. Enterprise data protection applies when someone signs in with their Entra work account; a personal account does not carry it, and once the apps merge there is no longer a different icon to give that away. Between 21 January and 3 February 2026 a defect Microsoft tracked as CW1226324 let Microsoft 365 Copilot summarise mail carrying confidential sensitivity labels, despite DLP policies configured to prevent it. Microsoft began rolling out a server-side fix in early February. Worth checking your own setup rather than assuming.
Should we train the team or fix the setup first?
Setup first, almost always. Training people to use a tool that cannot reach the right content teaches them it does not work, and that impression is expensive to reverse. Get the licences, permissions and one named job right, then train on that job.
Do you work with Microsoft on this?
No. Korbai is independent and not a Microsoft partner. Paul spent eight years at Microsoft leading channel sales across Asia Pacific, which is why the Microsoft world is familiar. The advice here is on nobody’s behalf but yours, including when it is that you do not need to buy anything.
Microsoft, Copilot, ChatGPT, Claude and Gemini are trademarks of their respective owners. Korbai is independent and not affiliated with any of them.
Make the licence you already bought worth something.
Book a discovery call and tell us what your setup looks like. We will tell you straight whether the problem is the tool, the setup, or the way it was rolled out.