Microsoft 365 Copilot (Premium): Teams meetings as a reference in Copilot Notebooks

Microsoft 365 Copilot (Premium) will integrate Teams meeting content—transcripts, chats, and shared files—into Copilot Notebooks, enhancing context-based insights. Rolling out from April to May 2026, it respects existing permissions and governance, requires no admin setup, and is enabled by default for licensed users.

[Introduction]

Meetings as references in Copilot Notebooks bring Microsoft Teams meeting content into the notebook experience, enabling users to ground Copilot on the discussions, decisions, and context that drive their work. By adding meetings as knowledge sources, users can connect transcripts, notes, chats, and shared content directly to their projects—enriching notebooks beyond files alone and improving downstream outputs such as presentations and briefs. This enhances productivity and decision-making by connecting conversational context with existing documents, while continuing to respect existing access controls and organizational data governance policies. Available in Copilot Notebooks for licensed Microsoft 365 Copilot (Premium) users.

[When this will happen:]

• Public Preview (Worldwide): We began rolling out in late April 2026 and expect to complete by mid-May 2026.
• General Availability (Worldwide): We will begin rolling out in mid-May 2026 and expect to complete by late May 2026.

[How this affects your organization:]

Who is affected:

• Users with access to Copilot Notebooks in Microsoft 365
• Organizations using Microsoft Teams meetings with transcription or recording enabled
• A Microsoft 365 Copilot (Premium) license is required to use this feature

What will happen:

• Users can incorporate Teams meeting content (for example, transcripts, chat, and shared materials) into Copilot Notebooks as references.
• Copilot will generate insights and content grounded in meeting context.
• The feature will be on by default where Copilot Notebooks are available.
• Access to meeting content will respect existing user permissions for the meeting and related files.
• Existing Teams meeting policies, retention settings, and organizational data governance controls are respected.
• There is no change to user workflow unless meetings are added as references.

[What you can do to prepare:]

• No additional admin setup is required.
• Admins should ensure Teams transcription and recording policies and meeting access permissions are configured appropriately for their organization’s governance requirements.
• Confirm meeting access permissions align with organizational governance policies.
• Communicate this change to helpdesk staff and Copilot users.
• Update internal documentation for Copilot Notebooks usage, if applicable.

Learn more:

• Manage Teams recording policies for meetings and events - Microsoft Teams | Microsoft Learn
• Admins- Manage transcription and captions for Teams meetings | Microsoft Learn
• Before General Availability rollout, we will update this post with new documentation.

[Compliance considerations:]

Compliance area	Explanation
Does the change alter how existing customer data is processed, stored, or accessed (e.g. documents, emails, chats, etc.)?	Copilot Notebooks can reference existing Microsoft Teams meeting artifacts (such as transcripts, chat, and shared files) to generate grounded outputs based on meeting context.
Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?	Microsoft Copilot will use meeting content as contextual grounding for generative AI responses within Copilot Notebooks.
Does the change provide users any new way of interacting with generative AI?	Users can include Teams meeting content as knowledge sources for Copilot-generated insights and content.
Does the change allow a user to enable and disable the feature themselves?	Users can choose to add or remove meeting references within Copilot Notebooks.