Copilot training is judged on one thing: whether the jobs your team does every week are running differently a month later. That means starting with what each person can actually reach, then working on their own files in the apps they already have open.
Good Microsoft Copilot training happens inside Word, Excel, Outlook and Teams, on your own documents, not in a demo tenant. It starts by confirming which Copilot each person is actually in, because the free chat is grounded on the web rather than on your files and email, and no amount of enthusiasm changes that. And it ends with every person owning one named job that now runs through Copilot, with a human still approving the result. Where the setup is part of the problem, that is part of the day too.
Ours is run from Sydney by someone who spent eight years inside Microsoft. That makes the Copilot world familiar ground, and it is also why the advice stays independent: we sell the training, not the licences.
People often arrive having never been shown how to use Copilot properly. Nine times in ten that also means nobody set it up properly, because the two problems have the same cause: it was bought as a licence and never rolled out as a change.
So we do not treat setup as something you have to sort out before you are allowed to book. We look at it with you: who is licensed, who is in the free chat, what each person can actually reach, and whether sharing and permissions are in a state you would be happy for an assistant to read. Sometimes that is a short conversation at the start of the day. Sometimes it is the day.
If you would rather work through the licence and permission questions yourself first, they are laid out in order in getting value from Microsoft Copilot
The same two strands as all our training, made specific to the Microsoft world your team already works in.
Which Copilot each person is actually signed into, and why it matters: enterprise data protection applies when someone signs in with their work account, not by default. What is safe to put in, what never goes in, and who checks what comes out. Settled once, so the hands-on work is not interrupted by doubt. These are the same rules we publish in our own AI use policy
Each person brings a job they did last week and does it again with Copilot beside them: the quote in Word, the report figures in Excel, the inbox and the meeting notes in Outlook and Teams. Nothing convinces like watching your own job get shorter.
When they come up, the first lesson is how the billing works, because it turns on what the agent reaches rather than on holding a licence, and the metered kind arrives switched off. Then we train the judgement, not just the mechanics.
Nobody leaves without one job to own, a named next step and a date. That rule is not Copilot-specific and it is the part most training skips, which is exactly why we hold to it.
A training day can go well and still change nothing. The room is motivated, the feedback is warm, and a month later no job runs differently, because nobody left owning one.
So ours end in commitments, not applause: one job per person, an owner, a date, and a check-in a month later against the only measure that matters, whether the job actually runs differently now.
The full training service is AI training and enablement
How the wider engagement runs is the Korbai Method
Copilot is the one already inside the licence, which is usually the argument for training on it before buying anything new. It rarely has the team to itself though, and the session works on what people genuinely have open rather than on the tidy version of the stack.
The Microsoft-specific ground. Which Copilot each person is actually signed into, what the licensed one reaches in your tenant while the free chat stays grounded on the web, and practice inside Word, Excel, Outlook and Teams on your own documents rather than a demo tenant. Prompting habits are general. The places where Copilot behaves differently from every other assistant are not, and that is where the sessions spend their time.
Yes, and a split like that changes nothing about how the day is built. The licensed half practise inside Word, Excel, Outlook and Teams on their own files. The rest work in Copilot Chat signed in with their work account, which is grounded on the web rather than on your files and email, so we teach exactly what that difference means and which jobs still fit it. Nobody sits out, and by the end you know who would genuinely use a licence before you buy any more.
We start by checking what each person is signed into, because that is what decides how content is handled. Copilot Chat carries enterprise data protection when someone signs in with their work account, and what the licensed Microsoft 365 Copilot reaches is scoped to what the person asking can already open. The rule we teach is the one we publish ourselves: work goes through the business account, never a personal one, and nothing goes in that a client contract forbids.
Yes, with the billing reality on the table first. Whether an agent costs extra turns on what it reaches: publish one to Microsoft 365 Copilot and licensed users are covered, point one at SharePoint or Graph connector content and the usage is metered, a setting Microsoft leaves off until you turn it on. The useful training is judgement: when an agent is worth that meter, and when a well-built prompt does the same job for nothing.
More than starting cold. The habit of asking properly carries over. What does not carry is knowing what Copilot can reach inside your tenant and how that changes what you can ask it to do, which is precisely where it differs from an assistant on a personal account. We spend the time on that difference rather than re-teaching what your team already does.
Three things. Who holds a licence and who does not, confirmed rather than assumed. One real task per person, nominated in advance: the quote, the report, the inbox. And an honest word about the setup, because if permissions or sharing are known to be wrong, that becomes part of the day rather than a reason to postpone it.
Microsoft, Microsoft 365, Copilot and ChatGPT are trademarks of their respective owners. Korbai is independent and not affiliated with any of them.
Book a discovery call and tell us who holds a licence and what the team actually does all day. If training is not the right first step, we will say so on the call.
