Copilot 365, Demystified

A few months ago, someone asked me: “So… is Copilot the same as ChatGPT? Is it the thing in Teams, or the thing I get on Edge?”

Fair question. “Copilot” has quietly become one of the most overloaded words in enterprise tech. Microsoft has stuck the name on at least a dozen things, and the result is a lot of people sitting with a licence, a blank prompt box, and no real idea what they’re holding.

What Copilot actually is

The single most useful thing I can tell you: Microsoft’s Copilot isn’t one product. It’s a brand sitting across several genuinely different tools and application. The ones most people mean:

• Microsoft 365 Copilot – the assistant inside Word, Excel, PowerPoint, Outlook and Teams. The important bit: it’s grounded in your organisation’s own data, your emails, files, chats, meetings, through the Microsoft Graph. That’s what makes it useful, and also what makes governance matter.
• Copilot Chat – (the free one) the chat experience on the Copilot website or in Edge. Handy, but by default it reasons over the public web, not your internal documents. Different tool, different rules.
• Copilot Studio – where you build your own agents: small, purpose-built assistants grounded in a specific knowledge source or wired into a process. This is where the genuinely interesting work happens, and where I spend a lot of my time.

If you remember nothing else: the version grounded in your work data and the version reasoning over the web are not the same thing. Most of the confusion comes from people not knowing which one they’re using.

What it isn’t

• It isn’t a search engine. Asking a basic single-sentence question and trusting the first answer is the fastest route to disappointment. It’s a reasoning assistant, not an index.
• It isn’t a magic button. It won’t turn a vague request into a brilliant output. What you get out is shaped by what you put in. Garbage in, garbage out
• It isn’t going to fix your data. M365 Copilot can see whatever your permissions let it see. If half the organisation can open a sensitive folder they shouldn’t, Copilot will cheerfully help them do it faster. It inherits your mess; it doesn’t tidy it.
• And it isn’t “set and forget”. Adoption is a programme, not a switch. Handing out licences and waiting is how organisations end up with a shelf full of expensive, unused seats. People need real use cases from their own day-to-day work, a bit of structured practice, and somewhere to ask the awkward questions. Questions like “why did it make that up?” is a teachable moment for everyone, not a support ticket. The organisations that get value treat the first three months as an active programme: champions who share what’s working, short sessions built around actual tasks rather than product tours, and someone paying attention to who’s using it and who’s quietly given up. The tool is the easy part. The habits are the work.

Now, before anyone objects: yes, Copilot and agents can find files, can help clean up data, can support an adoption programme. Every “isn’t” above has a “but, done properly…” behind it and doing it properly is exactly what this series is about. We’ll get to each one in future posts.

Where to actually start

Forget the grand rollout for a minute. In the first week, do this:

1. Pick three real, recurring tasks you already do – summarising a long email thread, drafting a first version of a document, pulling the actions out of a meeting. Boring is good. Boring is repeatable. AI loves boring.
2. Work where you already live – don’t go hunting for a special “Copilot place” – use it inside Teams, Outlook, Excel and Word, in the flow of the work you’re doing anyway.
3. Use a simple prompt shape – the one that consistently works: tell it who to be, what to do, what to work from, and how you want it back. “You’re my comms lead. Draft a short update to the project team, based on the notes below, in three bullet points.” Role, Task, Context, Format. That’s 80% of good prompting. We will cover more examples in future posts.

One thing to do tomorrow

Open the Copilot you already have, take the most tedious thing on your to-do list, and give it the Role, Task, Context, Format treatment once. Not to be impressed, just to get a feel for what it’s actually good and bad at. That single rep teaches you more than any demo.

That’s the foundation. Over the next few posts I’ll go deeper, demystifying more concepts and covering real examples of how Copilot and AI should and shouldn’t be used. And if you’re testing Copilot somewhere and hitting a wall, tell me where you’re stuck, those are the posts worth writing.