Who this is for
Microsoft 365 teams and managers planning responsible adoption.
Start with the challenges your team faces and each person’s current skills.
Many organizations pay for Copilot licenses that go unused. How to train teams on Copilot across Word, Excel, Outlook, Teams and PowerPoint — and measure whether adoption sticks.
Microsoft 365 teams and managers planning responsible adoption.
Start with the challenges your team faces and each person’s current skills.
A reviewed Microsoft 365 task and follow-through plan.
This is an example to help scope the learning; delivery arrangements are agreed before booking.
Choose a task supported by the cohort’s actual licences and settings.
Work from approved material and specify the expected output.
Check names, numbers, decisions and source references before sharing.
Use these stages to discuss the learning scope. Timing, tools and exercises depend on the team’s brief.
Choose a task supported by the cohort’s actual licences and settings.
Work from approved material and specify the expected output.
Check names, numbers, decisions and source references before sharing.
Confirm licences, available applications and permissions before choosing the exercise. Bring approved material and nominate a reviewer.
Estimate the time your team needs for sessions and follow-through. Change the example to fit your people; this is not a workshop package or quote.
Compare programs against your challenge, audience and available time. Confirm the actual schedule and fees with the organizer.
Find relevant programs in AISFYYou may need to sign in. Results stay on this page and are not saved or transferred to your AISFY account. Copy your plan before continuing.
Cohorts = participants ÷ cohort size, rounded up. Per-person time = session hours + weekly practice × weeks. Team time multiplies that by participants. Delivery hours count repeated sessions across cohorts; they exclude facilitator preparation.
Defaults are illustrative inputs, not benchmarks or recommended commitments. Changing or leaving the page resets the plan.
Open a topic for the full guidance, examples and references.
The September–December 2024 trial involved over 20,000 civil servants. Survey responses implied an average saving of 26 minutes per day. UK government — cross-government Copilot experiment.
Evidence limits: The estimate was self-reported and calculated from response bands. It is not a causal estimate of cash savings or proof that released time produced additional output.
Teach staff to identify the tasks where assistance fits their work, then include the checking effort in any local comparison. The trial’s survey estimate is useful context for forming a hypothesis; it should not become a promised benefit in the training brief.
Use a fictional meeting transcript containing a proposal, a confirmed decision and an unresolved owner. Ask participants to create an action list. The review must keep the proposal separate from the decision and leave the owner unassigned until confirmed. Time the full workflow through correction, not just initial generation.
Sources checked 20 October 2026. External examples are not AISFY customer results. Practice scenarios are editorial examples.
Copilot access, employee use and useful work are separate questions. Before designing training, check which accounts and features participants can use, then examine a task they need to complete. The session should teach an observable method and include a reviewer who can judge the resulting work.
Because Copilot reaches organizational data through Microsoft Graph, its governance conversation is different from public chatbots: permissions hygiene matters, oversharing surfaces in AI answers, and admins should treat a Copilot rollout as a reason to review access controls — before employees discover the gaps for you.
Start with one approved Microsoft 365 task. Define the input, expected output and review criteria; demonstrate the method; then let participants repeat it with different material. Choose applications according to the cohort’s actual work. Agree a follow-up owner and assessment date rather than assuming that attendance will produce sustained use.
Use product documentation for available features and your organization’s policies for permitted information, approval and escalation. A workshop should make both visible in the task brief. Review staff work samples after the session to determine whether further practice or a process change is needed.
Choose a task supported by the organization’s current plan and settings, such as producing a draft summary from approved material. Confirm permissions and available features before the session; a participant’s access may differ from the facilitator’s.
Ask participants to verify names, numbers, decisions and source references. Where information is missing, the output should flag the gap. The exercise should not encourage users to assume that a summary is complete because it was generated inside a familiar application.
An account may be able to retrieve information that should not be used for a particular purpose. Follow the organization’s data rules and review the output before sharing or acting. If the exercise reveals a permissions issue, route it to the appropriate owner instead of treating it as a training shortcut.
For follow-through, nominate a reviewer and repeat the task with new approved material. Licence allocation and attendance are useful administrative signals, but they do not demonstrate sustained adoption or financial value.
For workshop options, explore enterprise AI workshops. Use the preparation checklist and evaluation guide to connect the session to a practical next step.
Use fictional meeting notes with an agreed decision, a suggestion and an unresolved question. Ask participants to produce an action record with an owner, due date and source reference for each confirmed action. An unassigned task should remain unassigned rather than acquire a plausible owner.
Compare the record with the notes and ask the meeting owner to resolve ambiguity. If practising a meeting feature, first confirm that it is available, permitted and configured for the cohort. A generated recap is a draft for review; the approved action record remains the basis for follow-through.
Select applications and exercises after checking licences, organizational settings and actual participant access. This is a planning checklist, not a statement that every account includes every feature.
Before the session, ask a participant to open the approved sample material in the intended application. Confirm permissions with the organization’s administrator; do not widen document sharing merely to make an exercise work. Prepare an alternative fictional example if access cannot be resolved.
During evaluation, record whether a failure came from unavailable functionality, poor source material, unclear instructions or an incorrect review decision. These require different remedies. Repeating training will not fix a missing licence or a document that employees are not authorized to access.
Place Copilot exercises within your corporate AI training plan and agree how reviewed work samples will guide the next learning step.
Confirm that each participant has the account, licence, permissions and application features needed for the selected exercise. The requirements depend on the task and environment. Use an approved demonstration or alternative exercise if access is unavailable, and assess hands-on capability separately.
Start with the applications used for the team’s recurring task. A reporting exercise may involve Word or Excel; a communication task may involve Outlook. Confirm feature availability and choose a small number of relevant applications instead of assuming every cohort needs the same sequence.
Set an output-quality standard and record drafting, checking and correction effort. Assess a different task after practice, then review whether the method remains useful under supervision. Separate self-reported confidence, observed skill, continued use and any independently measured business outcome.
Share the challenge, audience and skills you want to develop. AISFY helps you plan the learning and connect with relevant expertise.
Scope, facilitator, availability and fees are confirmed before booking.
Explore AI workshops ↗