An explainx.ai guide makes a useful distinction between training for Microsoft 365 apps, Copilot Cowork, and Copilot Studio. The company also sells a course covering all three, so treat its agenda as a provider example, not a benchmark. Microsoft’s documentation makes the distinction more useful for buyers: opening Copilot Chat doesn’t prove an employee can complete an Excel lab, a Microsoft 365 Copilot license alone doesn’t get them into Cowork, and a Studio trial lets them build and test an agent but not publish it.
Microsoft 365 apps: Teach the work people already do
Choose this track if the goal is better day-to-day work in Excel, Outlook, Word, PowerPoint, or Teams. Ask the instructor to use one representative task and leave time to check the result. In Excel, that could mean analyzing a sample workbook and reconciling Copilot’s answer against a known total. In Outlook, have attendees compare a generated thread summary with the original messages and spot a decision or deadline the summary missed. The skill worth paying for is knowing what to check after the answer appears.
For the preflight, don’t stop at “Copilot opens.” Microsoft Learn distinguishes the Copilot Chat experience available with eligible subscriptions from the fuller licensed experience, and shows that Chat itself can appear inside supported Microsoft 365 apps. Ask the provider to name the exact feature each lab needs, then test it in the app attendees will use. A Chat-only workshop can be worthwhile; it just shouldn’t be sold as a lab for features the participants don’t have.
Copilot Cowork: Rehearse the moment before Send
Cowork training is about delegating a multi-step task and deciding whether to let the proposed action go ahead. Microsoft Learn’s worldwide prerequisites include an assigned Microsoft 365 Copilot license, Cowork enabled in the organization’s environment, and usage-based billing enabled. Microsoft recommends Edge or Chrome for browser access. If the syllabus promises app creation with Cowork’s built-in App skill, check Frontier enrollment too; that requirement is specific to the skill. Government Community Cloud customers should check their separate requirements rather than assume the worldwide exercise will work unchanged.
A good lab can be as simple as asking Cowork to prepare a meeting follow-up from sample notes and propose sending it to a test mailbox. Have attendees inspect the recipients and content, then cancel one proposed send and approve another. Microsoft documents approval prompts for actions such as sending email, posting in Teams, or scheduling meetings. It also says some approval choices can suppress similar prompts for the rest of the conversation. That’s worth demonstrating explicitly rather than letting a convenience setting pass unnoticed.
Give the lab a billing owner as well as an instructor. When Microsoft announced Cowork’s general availability on June 16, 2026, it listed pay-as-you-go at $0.01 per Copilot Credit and described usage reporting at the tenant, group, and user levels. That was a Cowork rate, not a per-task quote or a budget for a Studio deployment. Ask which organization pays for the lab and who will review consumption afterward.
Copilot Studio: Put “publish” in the syllabus or take it out
Studio is the right track when attendees need to build a reusable agent, not just complete another task in chat. A useful first lab is an agent that answers questions from an approved sample document. Test it with a question the document answers and one it doesn’t. That gives the class a concrete result without pretending it has built a production service.
Microsoft says an individual Studio trial can create agents and run them in the test chat panel, but cannot publish them. Administrators can also block self-service trial sign-up. If publishing is part of the course, get the target environment and channel in writing and have a representative attendee publish a disposable test agent there in advance. Microsoft’s troubleshooting guidance distinguishes publishing failures caused by the author’s license or permissions from failures caused by missing capacity in the environment or tenant. A successful test chat doesn’t rule out either problem.
The pre-purchase checklist
- Get the lab list, not just the topic list. For each exercise, ask what participants will do, what access they need, and what successful completion looks like.
- Run a preflight with an ordinary attendee account. Use the planned app or browser, approved sample files, and the actual training environment. An instructor’s admin account is not a substitute.
- Agree on data and billing. Decide which files and test recipients are permitted, whether the workshop uses your tenant or the provider’s, and who pays for any Cowork or Studio usage.
- Ask what happens when access fails. A provider sandbox, paired exercise, or instructor demonstration can all be useful. Only one of them may let every attendee do the work independently, so get the fallback in writing.
- Name the takeaway and its owner. A checked workbook, a prompt with a verification routine, or a tested agent gives the team something to reuse. If an agent is headed for deployment, name who will maintain its knowledge source and review it after class.
If licenses and tenant approvals aren’t ready, use a briefing or self-paced practice for now. Book the hands-on session when an ordinary attendee can finish the promised lab, not merely watch someone else finish it.
References
- Copilot Workshop: Curriculum, Licences, and Vet Checklist - explainx.ai explainx.ai · 2026-11-22T00:00:00+00:00
- Copilot Cowork is now generally available | Microsoft Copilot Blog microsoft.com
- Copilot Cowork is now generally available | Microsoft Copilot Blog microsoft.com