MC1139493 - Microsoft Teams Copilot without transcription becomes default for meetings - conversation history now persists

Message ID

MC1139493

View in Message Center

Service

Microsoft Teams

Last Updated

Sep 5, 2025

Published Aug 22, 2025

Tag

Updated message

Feature update

User impact

Admin impact

Roadmap ID

478611

View in M365 Roadmap

Platforms

Android

Desktop

iOS

Mac

Web

Summary

Microsoft Teams Copilot will default to operating without transcription for new meetings starting November 2025, with conversation history persisting during meetings. Transcription must be manually enabled for post-meeting insights. Custom policies remain unchanged, and admins can control settings via Teams meeting policies.

More information

Updated September 5, 2025: We have updated the timeline. Thank you for your patience.

Introduction

We’re updating the default behavior of Microsoft Teams Copilot in meetings. Copilot without transcription will become the default mode for newly scheduled Teams meetings where Copilot is allowed. Additionally, conversation history will now persist during meetings, improving multitasking and continuity of insights.

This update is associated with Microsoft 365 Roadmap ID 478611.

When this will happen

General Availability (Worldwide): We will begin rolling out in early November 2025 and expect to complete by mid-November 2025.

How this affects your organization

Copilot without transcription becomes default:
- Applies to new tenants and new users.
- Existing users without a set policy will inherit the host configuration and receive this new default.
- Custom policies will remain unchanged.
- In Teams meeting policy, the default property value for “Copilot” will change from EnabledWithTranscript to Enabled. This affects how Copilot behaves in newly scheduled meetings unless overridden by custom policy.
- Starting Copilot during a meeting will no longer automatically start transcription.
- Transcription must be manually enabled in Meeting Options or during the meeting if users want post-meeting insights or access to Copilot conversation history.
Conversation history now persists during meetings:
- Users can switch between meeting features (chat, participant list) without losing Copilot insights.
- This change applies to all users using Copilot without transcription.

What you can do to prepare

Review your organization’s Teams meeting policies for dependencies on transcription defaults.
Update internal documentation and training to reflect the new default behavior and conversation history persistence.
Communicate to users how to manually enable transcription when needed, especially if they want to retain Copilot insights after the meeting.

Learn more:

Compliance considerations

Question	Answer
Does the change alter how existing customer data is processed, stored, or accessed?	Conversation history is now retained during the meeting instead of being cleared when switching panels.
Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?	Copilot behavior is updated to persist conversation history, enhancing AI-driven meeting insights.
Does the change provide end users any new way of interacting with generative AI?	Users can now maintain a continuous Copilot interaction during meetings without transcription.
Does the change include an admin control and, can it be controlled through Entra ID group membership?	IT admins can enforce or override defaults via Teams meeting policy.
Does the change allow a user to enable and disable the feature themselves?	Users can manually enable transcription during meetings to retain Copilot insights post-meeting.