Draft and analyze business content by using AI
Meetings, Copilot Pages, Memory, and Instructions
CoreUse meeting context across the meeting lifecycle, collaborate on durable Pages, and manage how memory and custom instructions personalize responses.
Aligned to the AB-730 skills measured as of July 22, 2026; product behavior verified August 23, 2026.
Why this matters
Meeting assistance, collaborative artifacts, and personalization all reuse context, but they solve different problems. AB-730 expects the user to select the right stage, artifact, and personalization control while preserving verification and privacy.
Must Know
- Before a meeting, use authorized emails, files, prior discussions, and calendar context to prepare a concise briefing, questions, and open decisions, then review it.
- During or after a Teams meeting, use the meeting-specific Copilot or recap context for discussion points, decisions, and action items. Available results depend on the meeting, transcript, history, product configuration, and permissions.
- Verify meeting summaries before distribution: confirm decisions, owners, dates, commitments, and any missing context with accountable participants.
- Copilot Pages is a persistent, editable canvas created from Copilot output. A Page can be refined beside chat and shared so colleagues collaborate on the Page without access to the originating chat.
- Use a Notebook for a scoped body of references and conversations; use a Page when the output itself must become a durable co-edited artifact.
- Copilot Memory saves or infers useful personal context that can shape future responses. Users can review and delete saved memories or turn memory behavior off.
- Custom instructions deliberately state how Copilot should respond, such as preferred structure, tone, or standing working style. They are edited separately from memory.
- Use temporary chat when a one-off conversation should not use or update personalized information or appear in the user’s chat history, while recognizing that organizational retention may still apply.
Compare and Distinguish
- Meeting preparation vs catch-up vs follow-up: assemble relevant context before the event vs understand current discussion vs verify and distribute recap/actions afterward.
- General chat vs meeting Copilot: broad assistance vs meeting-specific evidence and controls.
- Page vs Notebook: co-edit the durable output vs collect scoped references, conversations, and instructions for focused work.
- Share a Page vs share a prompt: collaborate on one artifact vs let others rerun reusable instructions.
- Memory vs custom instructions: retained or inferred personal context vs deliberate standing response rules.
- Delete/rename chat vs memory controls: manage conversation history vs manage what personal context influences future responses.
Scenario examples
- Scenario: A seller has a customer meeting tomorrow and needs open issues from authorized email and files. Think: prepare a reviewed meeting brief before the meeting.
- Scenario: A late participant needs decisions from the current Teams discussion. Think: use meeting-specific Copilot and recognize transcript/history availability.
- Scenario: Colleagues must edit a useful Copilot response without seeing the full chat. Think: move it to a Page and share the Page.
- Scenario: Copilot keeps treating a user as a former role, while the user wants every summary in bullet form. Think: remove or update the stale memory and set the desired response style in custom instructions.
Exam traps
- A generated meeting recap is not an authoritative record until decisions, owners, and commitments are checked.
- General chat does not automatically have identical meeting evidence or controls.
- Sharing a Page does not require sharing the originating conversation.
- Renaming a chat does not change memory; turning off memory does not automatically delete saved memories already present.
- Temporary chat limits user-facing memory and history behavior but does not promise exemption from organizational retention.
Key takeaways
- Choose Copilot use by meeting stage and verify every consequential recap.
- Pages are durable collaborative canvases; Notebooks are focused context collections.
- Memory retains context, instructions declare response behavior, and temporary chat limits personalization for a one-off conversation.
How it works
- Meeting context provides the evidence for a briefing, catch-up, or recap; the user validates it and can move structured results into an appropriate collaboration or tracking workflow.
- A Page separates the durable artifact from the source chat. Memory and instructions separately contribute personal context and deliberate response preferences to later conversations.
Objects and administrative surfaces
- Copilot in Teams meetings and meeting recap — meeting-specific preparation, catch-up, recap, and follow-up where available.
- Copilot Pages — side-by-side persistent canvas for editing, sharing, and group collaboration on selected output.
- Personalization settings — saved memories, chat-history personalization, and custom instructions.
- Temporary chat — a one-off user experience that does not access or store personalized information and does not appear in the user’s chat history.
When to use it
- Use meeting context for meeting-specific evidence and Pages for shared editing of selected output.
- Update or delete stale memory, edit custom instructions for standing response behavior, and use temporary chat for a sensitive or one-off nonpersonalized discussion.
Security and governance implications
- Review Page sharing and downstream artifact permissions, and avoid including unnecessary sensitive meeting content.
- Treat temporary chat as a personalization control, not as a promise that organizational compliance retention does not apply.
How to reason about this
- If a meeting answer lacks recent discussion, confirm meeting context and transcript/history availability before switching to general chat.
- If personalization is wrong, determine whether the source is saved memory, chat-history inference, or custom instructions and change the matching control.
More detail
- Meeting Copilot can surface discussion points and action items when the required meeting context is available. Exact availability depends on meeting and product settings, so AB-730 scenarios should state the evidence condition rather than rely on click-path trivia.
- Pages can be edited, shared, and converted to Word or PowerPoint. Collaborators receive the Page content without needing access to the originating Copilot chat session.
- Saved memories and chat-history inferences can both personalize responses. Deleting a saved memory, deleting a chat, and turning off chat-history personalization are distinct controls.
- Temporary chat neither uses nor updates personalized information and does not appear in the user’s chat history, but its data can remain subject to the organization’s retention policy.
Ready for the quiz?
- When is meeting-specific Copilot preferable to general chat?
- Why can teammates collaborate on a Page without the original chat?
- Which action fixes an outdated remembered role?
- Which action establishes a standing bullet-format preference?
Related objectives
- D3.2.a — Describe how to use Microsoft 365 Copilot for meetings
- D3.2.b — Describe how to use Copilot Pages for collaboration
- D3.2.c — Describe how Copilot uses memory and instructions