Copilot, where your teams already work.
You already pay for the licences; this training is about getting the value out of them. Outlook, Teams, Word, Excel, PowerPoint: everyone learns to prepare, write, analyse and follow up on their own work with Copilot.
Four ways in, depending on your rollout.
The format depends on how many licences are live, the level of the teams and how long the rollout has been running.
Reach everyone
A remote session to set the basics, show what the tool actually does and clear the first questions. No cap on attendees.
or the entire company
Start a practice
The most requested format. Fundamentals plus two or three use cases worked directly on the participants' own files.
from the same function
Build autonomy
The full programme, with time to practise, get it wrong and build your own working methods.
at a similar level
Make it stick
Short sessions spread out, with real work in between. The only format that lets you measure how practice actually evolves.
or internal champions
Application by application, use case by use case.
The outline below is the full-day format, adjusted to the applications and licences actually deployed at your organisation. The content is adjusted before each session to the features available in your environment and the way your teams work.
Understanding what Copilot sees
The question that comes up in every session. Answering it clearly removes half the resistance and prevents careless use.
- Microsoft Graph — for organisational information, Copilot only draws on what you already have access to: mail, files, meetings, Teams conversations, depending on licence and configuration
- Permission scope — why Copilot will never surface a document you have no access to
- Copilot on the web vs Copilot in the apps — depending on the request, the feature used, your licences and permissions, an answer may draw on organisational information, the web or the model itself
- Document grounding — the difference between an answer drawn from your files and one from the model alone
Outlook and Teams
The most immediate gains, and often the most under-used. This is where to start to win over the sceptics.
- Summarise a long thread and pull out the decisions
- Draft a reply from the context of the thread
- Catch up on a missed meeting — summary, decisions taken, actions assigned
- Prepare an upcoming meeting from the previous exchanges
- Limits: what Copilot handles badly on very long or multilingual threads
Word and PowerPoint
The most anticipated use cases, and the ones that need the most method to produce presentable results.
- First draft from notes or an outline
- Referencing your own documents — build on an existing template or document rather than starting from scratch
- Rewriting, changing tone, adjusting length
- PowerPoint — generate an outline from a Word document or notes, then rework the structure rather than the content
- Why the raw output is rarely publishable, and how to work in iterations
Excel
The most technical part, with specific prerequisites. Framed properly, it is a considerable time-saver for anyone working with tables.
- Prerequisite: the structured table — why Copilot does almost nothing with a raw range of cells
- Query a table in plain language
- Create calculated columns and understand the formula suggested
- Spot trends and outliers
- What remains out of reach: workbooks with nested formulas and cross-references
Beyond simple conversation
Depending on availability and your organisation's licences, some features let you hand over longer tasks. They are covered when your environment offers them, for example:
- Copilot Notebooks — a persistent workspace that holds the context of a case: files, threads and notes in one place, queryable together
- Agent mode in Word, Excel and PowerPoint — hand over a multi-step task inside the document instead of steering every edit
- Copilot Cowork — delegate a complete piece of work, track it in “My tasks”, schedule recurring tasks and keep checkpoints before anything goes out
- Picking the right surface — a one-off question, a case followed over time, or a task to delegate: these are not the same tools
Assistants and agents in Microsoft 365
Microsoft's vocabulary has become confusing. This sequence clears it up before considering anything custom-built.
- Ready-made assistants — the agents Microsoft ships in Teams and SharePoint, switched on without development
- Cowork or agent — delegating a complete task to Copilot is Cowork; giving a team a permanent assistant is an agent. Two different needs, two different answers.
- What belongs in Copilot Studio — as soon as you need defined topics, triggers or actions into other systems
- Governance — who is allowed to create an agent at your organisation, and how those creations stay visible
Building the routine
The difference between a successful demo and real adoption. Without this step, usage collapses within three weeks.
- Each participant identifies the three use cases that matter for their role
- Anchoring those use cases in specific moments of the week
- Verification habits — what gets re-read every single time before sending
- Watch points on confidentiality and sharing
What it looks like, function by function.
A first selection of cases seen in training. The scoping session will bring out yours.
Meeting preparation
Rebuild the history of an account from past emails and meetings, ahead of a client meeting.
Case tracking and write-ups
Summarise the exchanges on a case, draft the routine replies, structure interview write-ups.
Reading tracking spreadsheets
Query a budget tracking table in plain language, spot the variances and generate an analytical commentary.
Inbox handling
Give Cowork a recurring task on the inbox: sort the day's messages by priority, produce a summary, draft the routine replies and flag what needs a decision.
Custom agent on your own rules
An agent grounded in your agreements, charters and procedures: leave, expenses, remote work — with a link back to the source text and escalation to HR on edge cases.
Catching up and deciding
Catch up on missed meetings, follow several files in parallel, prepare team check-ins.
“Jonathan brought our people on board during an awareness webinar with genuine enthusiasm, clear materials and a knack for taking the drama out of the subject. Very attentive throughout the process.”
Frequently asked questions
The training is for employees who want to use Microsoft Copilot practically in their daily work. Exercises are adapted to their roles and to the features actually available in the organisation’s Microsoft environment.
Depending on needs and available licences, the training may cover Word, Excel, PowerPoint, Outlook and Teams, as well as more advanced Microsoft Copilot uses. The programme is adapted to the applications and features participants can actually access.
Yes, when the features available in the client’s environment allow it. Participants can learn to build a simple assistant or agent using instructions and knowledge sources. More advanced needs involving additional actions, workflows, connections or governance can be addressed with Microsoft Copilot Studio.
Microsoft Copilot supports users in their daily work and can combine, according to the licence and configuration, information from the web and Microsoft 365 work context they are authorised to access. Microsoft Copilot Studio is used to design and govern custom agents with their own knowledge, instructions, tools, connectors and workflows for specific business needs.
Get the full value of your Copilot licences.
Book 30 minutes
A scoping call: your context, your teams, the format that fits best.
Describe your need
Three lines is enough: reply within 24 h.