Companion notes
Lesson summary
This module explains how Microsoft Copilot fits into everyday work: it uses context from the user, the conversation, connected apps, and permitted data to help produce useful responses.
Key ideas
- Copilot answers are shaped by context: prompts, chat history, documents, meetings, app state, and organizational data.
- Permissions still matter. Copilot should not become a shortcut around access control.
- Chat is useful for open-ended assistance, while app-integrated Copilot experiences are closer to the work surface.
- Agents add workflow focus and can be designed for repeatable business tasks.
Practice focus
For AB-730, pay attention to what information Copilot can use, where the user is working, what permissions apply, and whether an agent or a general chat experience is the better fit.