Trainer Guide
Workshop overview
Copilot Cowork is the agentic workspace inside Microsoft 365 Copilot. You describe an outcome and Cowork plans the steps. It then works across Outlook, Calendar, Teams, OneDrive, SharePoint, Word and Excel to deliver the finished result. Any action that changes something, such as sending an email or creating an event, goes through an approval card first, so the user stays in control.
Over six progressive labs, participants move from their first Cowork task to building and publishing their own plugin. By the end they can:
- Hand Cowork multi-step email, calendar and file work, and review each action before it runs
- Set standing calendar rules and automate an out-of-office handoff
- Produce grounded executive meeting briefs and post-meeting follow-up
- Classify, rename and govern business documents in OneDrive, with approval at each step
- Build reusable custom skills with the conversational Skill Builder
- Schedule a self-refreshing personal work dashboard built on Microsoft Graph data
- Package, validate and publish a custom plugin that connects Cowork to an external system through the Model Context Protocol (MCP)
Important
Disclaimer for participants: Cowork is AI-powered, so outputs vary between users and sessions. Follow the workflow and the expected outcome; don't expect your results to match the screenshots word for word.
Lab map
| Lab | Title | Duration | What participants produce |
|---|---|---|---|
| 1 | Getting Started with Copilot Cowork | 40 min | A seeded environment (5 emails, 3 events, OneDrive files, a Teams team) and a first scheduled automation |
| 2 | AI-Powered Calendar Optimization and Executive Meeting Coordination | 40 min | Standing calendar rules applied to a week, two new meetings, a Word prep brief, and an approved vacation handoff |
| 3 | Intelligent File Organizer | 40 min | Project Orion files classified and renamed into business-function folders, an approved archive, an Excel governance tracker and a Teams summary |
| 4 | Building Custom Cowork Skills (read-only) | 30 min | A skill specification in Notepad (hands-on); walkthrough of building, testing, sharing and publishing two custom skills |
| 5 | Building a Personal Work Dashboard (read-only) | 30 min | Walkthrough of an HTML work dashboard that refreshes hourly on weekdays, emails itself at 9 AM, and has a locked-in format |
| 6 | Building and Publishing a Custom Cowork Plugin (read-only) | 30 min | Walkthrough of a Financial Research plugin (7 skills + SEC EDGAR MCP connector) generated by Cowork, deployed from the Microsoft 365 admin center and tested |
Dependency: Lab 1, Tasks 2–4 seed the data that every later lab uses. Participants must complete them before moving on.
Prerequisites
Each participant needs:
- A Microsoft 365 Copilot license with Copilot Cowork enabled. Cowork is currently delivered through the Frontier program, so the tenant must be enrolled.
- Permission to use Outlook, Calendar, Teams, OneDrive, SharePoint, Word, Excel and Microsoft To Do
- Access to the provisioned lab VM and its local folder
C:\LabFiles\lab file - Basic familiarity with Microsoft 365 apps
For Lab 6 only:
- Access to the Microsoft 365 admin center, as a tenant administrator or with the Copilot administrator role
- Permission to upload custom apps (Manage apps > Upload custom app). Custom app policies control who can sideload.
Trainer pre-flight (run the day before):
- Sign in with one lab account and run Lab 1 end to end.
- Confirm that Plugins and Automations appear in the left navigation.
- Check whether Teams meeting links can be created in the tenant (see Lab 1, Task 3).
- Confirm that
C:\LabFiles\lab filecontains 5 folders (Archivecandidates,Healthcare,Project Orion Files,Retail,Shared files) and 4 files.
Trainer delivery notes
Behaviors to expect (and explain to the room):
- Approval cards are not consistent. Even when the prompt grants upfront approval, Cowork sometimes shows a Send email? or Create calendar event? card and sometimes acts directly. Both are correct. Use the moment to explain risk levels: cards carry a Medium risk badge.
- Same conversation, longer step list. Task 3 runs in the same Cowork conversation as Task 2, so the Workspace Steps counter carries over (for example, 7/11).
- Dates shift with the run day. Calendar events go on the next 3 business days, so every participant gets different dates.
- Names vary. The scheduled task in Task 5 may be called Weekday Morning Briefing, Weekday Morning Day-Ahead Briefing or similar. Check the type and schedule, not the exact name.
- "Always allow" is scoped. The button on a scheduled email reads Always allow: Only to \<your address>. Point out that the permission covers self-addressed mail only.
Known environment issue:
- In some sandbox tenants Cowork cannot add a Teams meeting link to events. It creates them anyway and says so in its summary. Tell participants this is an environment limit, not their mistake. They can switch on Teams meeting in Outlook if they need the link.
Screenshot hygiene before publishing:
- Blur every user ID and tenant name. Two Lab 1 source shots (the Project Orion folder upload and the Add content picker) showed an ODL user number. The copies in this guide are blurred, but your original files are not.
- Recapture the app-launcher shots (Outlook, OneDrive, Teams) taken in the older Cowork UI (New task / My tasks / Scheduled / Customize).
- Never print real Temporary Access Passes in the guide; use placeholders.
Timing tip: Task 4 (uploads) is the slowest part of Lab 1. Start the uploads, then talk through the Plugins page while they finish.
Lab 2 notes
- Data volume sets expectations. The Lab 2 Task 3 screenshots come from a mailbox with about 22 messages, 4 drafts and 11 meetings (Clearwater, Fourth Coffee, Zava and more). Lab 1 only seeds 5 emails and 3 events, so participants will see far fewer findings. Either extend the Lab 1 seeding or tell the room up front.
- Intentional conflicts. The vacation week is the same week that Tasks 1 and 2 fill with focus blocks and meetings. Point this out so nobody thinks they set the wrong dates.
- Planner and To Do may be unreachable. Cowork often reports them as a coverage gap. Use it as a teaching moment on honest agents.
- Placeholder signatures. In the screenshots, Cowork signed the Tailspin reply as Alex. Make participants edit drafts before clicking Reply.
- Overlap with Lab 3. Lab 2 Task 2 already builds a Steering Committee prep brief. Make sure Lab 3 goes further (for example, post-meeting follow-up) rather than repeating it.
Lab 3 notes
- One conversation only. Tasks 2 and 3 reuse the file inventory from Task 1. A participant who starts a new task in between loses it and gets different results.
- File count. Lab 1 says Project Orion Files holds 8 items, but in Lab 3 Cowork reads 11 files. Check the source folder and align the two numbers.
- Archive location. In the original run, Cowork created Archive directly under Lab Files, while the guide said to look inside Project Orion - Renamed Files. The archive prompt now names the location explicitly.
- Sharing check. Cowork can't report 'anyone' links from the content inventory, and file timestamps are all fresh after the rename. Expect these gaps and use them to discuss evidence quality.
- Upload fallback. The tracker upload to Lab Files can fail; Cowork then saves it to the Cowork folder and the Teams post names the file without a link.
- Retail is a team, not a channel. The Task 3 prompt now posts to the General channel of the Retail team.
Lab 4 notes
- Read-only scope. Only Task 1 (Notepad) is hands-on. Tasks 2–8 are a walkthrough to save Copilot credits. Building and testing skills consumes credits, so if you demo live, budget for it.
- Pre-existing skill in the screenshots. The demo account already had a weekly-status-email skill, so Cowork mentions it in its summaries and in "When NOT to Use". A clean tenant won't show it.
- Older interface. Many screenshots show the Customize page and Create skill with Cowork; the current UI uses Plugins and New skill. Recapture when possible.
- Duplicate skill after upload. Task 7 leaves two copies with the same triggers. Delete project-status-brief-1 after the demo.
- Risk rating. The two quality reports show Risk medium and Risk high. Be ready to explain why before learners share skills.
Lab 5 notes
- Read-only scope. The whole lab is a walkthrough. The original labelled it read-only but wrote every step as hands-on; the steps now describe what happens.
- Credit cost. The scheduled task runs 12 times every weekday. If you demo it, pause or delete it at the end of the session.
- Time zones. The schedule prompt was written for a Pacific-time device on an account set to IST. Adapt it to your region.
- Task name. "Refresh work dashboard (hourly at 9 AM, email at 9 AM)" is confusing; consider "Refresh work dashboard (hourly, email at 9 AM)".
- Duplicate task. The final screenshot shows the task twice. Delete the duplicate so it doesn't run (and cost credits) twice.
- Older interface. Some screenshots show the Chat / Cowork / Code tabs and the Customize page. Recapture when possible.
Lab 6 notes
- Read-only scope. The whole lab is a walkthrough: publishing needs an admin role participants don't have. The original note said AI Administrator while Task 3 said Global Administrator; the lab now says "an admin role participants are not assigned". Confirm which role you want to name.
- Two upload paths. The prompt and Cowork's summary say Copilot > Agents > All agents > Upload agent; the screenshots use Settings > Integrated apps > Upload custom apps. Both are in the Microsoft 365 admin center. The lab keeps the screenshots' path and explains the difference. Never use the Teams admin center.
- Third-party MCP server.
secedgar.caseyjhand.comis a community server with no authentication. Fine for public SEC data in a demo; stress that production plugins should use approved servers only. - Publisher shown as Microsoft. The manifest sets the developer to Microsoft and the package name to
com.microsoft.*, so the plugin page says Created by Microsoft. Consider using your organization's name so learners don't copy that pattern. - Leftover plugins. The demo tenant already had three Financial Research copies before Task 1. Remove old copies before a live demo.
- Older interface. Some screenshots show the Customize page and the Chat / Cowork / Code tabs. Recapture when possible.
- Not investment advice. The results include real financial figures. Remind learners to check them against the filings.