Start with a task, not a product label
Ask whether the learner needs to draft from supplied material, work inside a particular Microsoft 365 app or use organizational content available through their account. Write the expected output and the source it depends on. This separates a general prompting exercise from one that requires a particular integration. Both can be useful, but they have different preparation needs and should not be sold as the same experience.
Check the current Microsoft experience
Microsoft documents a range of Copilot access depending on subscription, add-on licence, app and organization configuration. Confirm the actual capabilities with your administrator and current product guidance. Avoid simplistic assumptions that every chat experience is identical, that all organizational data is available or that every employee can use the same feature in Word, Excel or PowerPoint.
Choose the classroom path that fits
For a supplied-document task, a trainer can teach clear instructions, source boundaries and output review in an approved chat experience. For app-based practice, test the precise workflow in the participant environment first. When two paths are used in one cohort, explain which steps differ and which learning objective is shared. A fallback should preserve that objective rather than simply fill time with another product demonstration.
Keep other Copilot products in their own scope
A business-productivity workshop is different from developer assistance with GitHub Copilot or agent-building work with Copilot Studio. Ask buyers which outcome they mean when requesting “Copilot training.” A developer curriculum needs coding context and software review. Agent building needs its own permissions, testing and action boundaries. These may be later learning paths, but they should not be silently added to an employee productivity workshop.
Document the agreed boundary
Put the selected experience, planned apps, access owner and fallback in the proposal. Also state who provides subscriptions and how product changes before the workshop will be handled. Participants should leave knowing what they practised, which parts depend on their environment and where to ask for help. This is more durable than memorizing a menu path that may change after a product update.