check before: 2025-09-15
Product:
Copilot, Defender, Entra, Microsoft 365 admin center, Microsoft 365 Apps, Microsoft 365 Copilot, Teams, Windows
Platform:
Android, iOS, Mac, Online, Web, Windows Desktop, World tenant
Status:
Launched
Change type:
Admin impact, Feature update, Updated message, User impact
Links:
Details:
Summary:
Microsoft Teams Copilot will default to a mode without transcription for new meetings starting late March 2026, with conversation history persisting during meetings. Transcription must be manually enabled for post-meeting queries. Tenants with policies updated after June 2024 are unaffected; admins can adjust policies to retain current behavior.
Details:
Updated January 14, 2026: 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 late March 2026 (previously mid-January) and expect to complete by early April 2026 (previously early February).
[What's changing?]
Who is affected:
Affected tenants: If your TeamsMeetingPolicy was created or modified before the Copilot without transcription policy option was introduced (June 2024), your tenant will be affected by this change.
Not Affected: If your TeamsMeetingPolicy was created or modified after June 2024 when the Copilot without transcription option was introduced, your tenant will not be affected.
What will happen:
The default Copilot policy will change from EnabledWithTranscript to Enabled for both new and existing Teams meetings where Copilot is allowed.
Copilot and Facilitator will no longer automatically start transcription for meetings in affected tenants.
Users must manually enable transcription to use post-meeting Copilot or Facilitator queries.
Conversation history will persist during meetings for Copilot without transcription.
Tenants with TeamsMeetingPolicy created or modified after June 2024 are not affected.
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
General Availability
Created:
2025-08-22
updated:
2026-01-15
Task Type
XXXXXXX ... free basic plan only
Docu to Check
XXXXXXX ... free basic plan only
MS Preperations
XXXXXXX ... free basic plan only
MS Urgency
XXXXXXX ... free basic plan only
MS workload name
XXXXXXX ... free basic plan only
linked item details
XXXXXXX ... free basic plan only
summary for non-techies**
XXXXXXX ... free basic plan only
Direct effects for Operations**
Transcription Availability
Users will need to manually enable transcription for post-meeting queries, which may lead to missed insights and reduced productivity if not prepared.
- roles: End Users, Meeting Facilitators
- references: https://learn.microsoft.com/microsoftteams/copilot-teams-transcription, https://support.microsoft.com/office/use-copilot-without-recording-a-teams-meeting-a59cb88c-0f6b-4a20-a47a-3a1c9a818bd9
User Experience with Conversation History
The change to persistent conversation history may confuse users who expect the previous behavior of cleared history, impacting their meeting engagement.
- roles: End Users, IT Support
- references: https://learn.microsoft.com/microsoftteams/copilot-teams-transcription, https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=478611
Policy Management and Compliance
Admins may face compliance issues if they do not update TeamsMeetingPolicy to reflect the new defaults, leading to potential data retention violations.
- roles: IT Administrators, Compliance Officers
- references: https://learn.microsoft.com/microsoftteams/copilot-teams-transcription, https://support.microsoft.com/office/use-copilot-without-recording-a-teams-meeting-a59cb88c-0f6b-4a20-a47a-3a1c9a818bd9
Configutation Options**
XXXXXXX ... paid membership only
Opportunities**
Enhanced Meeting Insights through Persistent Conversation History
The new feature of persistent conversation history allows users to reference past discussions without losing context, significantly improving the user experience during meetings. This can enhance decision-making and collaboration among team members.
- next-steps: Conduct training sessions to familiarize users with utilizing the persistent conversation history effectively. Update internal documentation to reflect this change and highlight best practices for leveraging this feature.
- roles: Project Managers, Team Leaders, Executives
- references: https://learn.microsoft.com/microsoftteams/copilot-teams-transcription, https://support.microsoft.com/office/use-copilot-without-recording-a-teams-meeting-a59cb88c-0f6b-4a20-a47a-3a1c9a818bd9
User Empowerment through Manual Transcription Activation
By requiring users to manually enable transcription, the organization can empower users to take control of their meeting experiences, allowing them to decide when transcription is necessary. This can lead to a more tailored and efficient meeting environment.
- next-steps: Communicate the change to users and provide guidance on how to enable transcription when needed. Create a quick reference guide or video tutorial to facilitate this process.
- roles: IT Administrators, Training Coordinators, Team Members
- references: https://learn.microsoft.com/microsoftteams/copilot-teams-transcription, https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=478611
Policy Review and Compliance Management
The update necessitates a review of TeamsMeetingPolicy to ensure compliance with the new defaults. This presents an opportunity to streamline policies and reduce administrative overhead by consolidating settings where possible.
- next-steps: Schedule a review meeting with IT and compliance teams to assess current TeamsMeetingPolicies. Update policies as necessary to align with the new defaults and ensure all relevant stakeholders are informed of changes.
- roles: Compliance Officers, IT Administrators, Policy Managers
- references: https://learn.microsoft.com/microsoftteams/copilot-teams-transcription, https://support.microsoft.com/office/use-copilot-without-recording-a-teams-meeting-a59cb88c-0f6b-4a20-a47a-3a1c9a818bd9
Potentional Risks**
XXXXXXX ... paid membership only
Data Protection**
XXXXXXX ... paid membership only
IT Security**
XXXXXXX ... paid membership only
Hypothetical Work Council Statement**
XXXXXXX ... paid membership only
DPIA Draft**
XXXXXXX ... paid membership only
explanation for non-techies**
Microsoft Teams is introducing a change in how its Copilot feature works during meetings. Imagine you're in a meeting room where someone usually takes notes and writes everything down word-for-word. This is similar to the transcription feature in Teams. Now, Teams is shifting to a new default setting where this note-taker doesn't automatically write everything down, but instead focuses on keeping track of the conversation flow and important points.
For those who are used to having everything transcribed, think of it like switching from having a full script of a play to just having the key scenes highlighted. If you still want the full script, you can ask for it by enabling transcription manually during the meeting. This means you have the choice to turn on the transcription feature when you feel it's necessary, just like deciding when you need detailed notes.
Additionally, the conversation history will now stay visible during the meeting, much like having a whiteboard that everyone can see and refer back to, even if the discussion moves to different topics. This helps everyone keep track of what's been discussed without losing context.
For organizations that set their meeting policies before June 2024, this change will automatically apply. However, if policies were updated after that date, they remain unaffected. Admins have the option to adjust settings if they prefer to keep the old behavior, similar to deciding whether to keep using the same note-taking method or try the new approach.
Overall, this update aims to enhance how meetings are conducted by focusing on key insights and maintaining a seamless flow of conversation, while still providing the flexibility to capture detailed notes when needed.
** AI generated content. This information must be reviewed before use.
a free basic plan is required to see more details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
change history
| Date | Property | old | new |
| 2026-01-15 | MC Last Updated | 10/31/2025 17:47:57 | 2026-01-15T00:38:09Z |
| 2026-01-15 | MC Messages | Updated October 30, 2025: We have updated the timeline and the content. 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 mid-January 2026 (previously early November 2025) and expect to complete by early February 2026 (previously mid-November 2025). [What's changing?] Who is affected: Affected tenants: If your TeamsMeetingPolicy was created or modified before the Copilot without transcription policy option was introduced (June 2024), your tenant will be affected by this change. Not Affected: If your TeamsMeetingPolicy was created or modified after June 2024 when the Copilot without transcription option was introduced, your tenant will not be affected. What will happen: The default Copilot policy will change from EnabledWithTranscript to Enabled for both new and existing Teams meetings where Copilot is allowed. Copilot and Facilitator will no longer automatically start transcription for meetings in affected tenants. Users must manually enable transcription to use post-meeting Copilot or Facilitator queries. Conversation history will persist during meetings for Copilot without transcription. Tenants with TeamsMeetingPolicy created or modified after June 2024 are not affected. | Updated January 14, 2026: 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 late March 2026 (previously mid-January) and expect to complete by early April 2026 (previously early February). [What's changing?] Who is affected: Affected tenants: If your TeamsMeetingPolicy was created or modified before the Copilot without transcription policy option was introduced (June 2024), your tenant will be affected by this change. Not Affected: If your TeamsMeetingPolicy was created or modified after June 2024 when the Copilot without transcription option was introduced, your tenant will not be affected. What will happen: The default Copilot policy will change from EnabledWithTranscript to Enabled for both new and existing Teams meetings where Copilot is allowed. Copilot and Facilitator will no longer automatically start transcription for meetings in affected tenants. Users must manually enable transcription to use post-meeting Copilot or Facilitator queries. Conversation history will persist during meetings for Copilot without transcription. Tenants with TeamsMeetingPolicy created or modified after June 2024 are not affected. |
| 2026-01-15 | MC End Time | 03/10/2026 08:00:00 | 2026-05-25T09:00:00Z |
| 2026-01-15 | MC Summary | Microsoft Teams Copilot will default to running without transcription for new meetings starting mid-January 2026, with conversation history persisting during meetings. Transcription must be manually enabled for post-meeting queries. Tenants with policies updated after June 2024 are unaffected; admins can adjust policies to retain current behavior. | Microsoft Teams Copilot will default to a mode without transcription for new meetings starting late March 2026, with conversation history persisting during meetings. Transcription must be manually enabled for post-meeting queries. Tenants with policies updated after June 2024 are unaffected; admins can adjust policies to retain current behavior. |
| 2025-10-31 | MC prepare | https://learn.microsoft.com/microsoftteams/copilot-teams-transcription
https://support.microsoft.com/office/use-copilot-without-recording-a-teams-meeting-a59cb88c-0f6b-4a20-a47a-3a1c9a818bd9 https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=478611 | If adopting the new defaults:
Review TeamsMeetingPolicy for transcription dependencies. Update internal documentation and training. Communicate to users how to enable transcription when needed. Optional admin steps to retain current behavior: Update Global and Custom TeamsMeetingPolicy settings via TAC or PowerShell. TAC UI Portal: Navigate to Teams Admin Center and set the Copilot policy default value as required. For example, if the current default value is desired, update it to a different value, then set it back. Please ensure both TeamsMeetingPolicy and all Custom Policies are updated. PowerShell example to set Copilot policy to EnabledWithTranscript for all relevant meeting policies: get-csteamsmeetingpolicy | ? { $_.Identity -ne "Tag:AllOn" -and $_.Identity -ne "Tag:AllOff" -and $_.Identity -ne "Tag:Default" -and $_.Identity -ne "Tag:Kiosk" -and $_.Identity -ne "Tag:RestrictedAnonymousAccess" -and $_.Identity -ne "Tag:RestrictedAnonymousNoRecording" } | % { $_.Identity; set-csteamsmeetingpolicy -identity $_.Identity -Copilot EnabledWithTranscript } Learn more: Manage Microsoft 365 Copilot in Teams meetings and events | Microsoft Teams | Microsoft Learn Use Copilot without recording a Teams meeting | Copilot in Teams | Copilot | Microsoft Support Compliance considerations QuestionAnswer 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. https://learn.microsoft.com/microsoftteams/copilot-teams-transcription https://support.microsoft.com/office/use-copilot-without-recording-a-teams-meeting-a59cb88c-0f6b-4a20-a47a-3a1c9a818bd9 https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=478611 |
| 2025-10-31 | MC 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. | Microsoft Teams Copilot will default to running without transcription for new meetings starting mid-January 2026, with conversation history persisting during meetings. Transcription must be manually enabled for post-meeting queries. Tenants with policies updated after June 2024 are unaffected; admins can adjust policies to retain current behavior. |
| 2025-10-31 | MC Last Updated | 09/05/2025 19:18:58 | 2025-10-31T17:47:57Z |
| 2025-10-31 | MC Messages | 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. | Updated October 30, 2025: We have updated the timeline and the content. 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 mid-January 2026 (previously early November 2025) and expect to complete by early February 2026 (previously mid-November 2025). [What's changing?] Who is affected: Affected tenants: If your TeamsMeetingPolicy was created or modified before the Copilot without transcription policy option was introduced (June 2024), your tenant will be affected by this change. Not Affected: If your TeamsMeetingPolicy was created or modified after June 2024 when the Copilot without transcription option was introduced, your tenant will not be affected. What will happen: The default Copilot policy will change from EnabledWithTranscript to Enabled for both new and existing Teams meetings where Copilot is allowed. Copilot and Facilitator will no longer automatically start transcription for meetings in affected tenants. Users must manually enable transcription to use post-meeting Copilot or Facilitator queries. Conversation history will persist during meetings for Copilot without transcription. Tenants with TeamsMeetingPolicy created or modified after June 2024 are not affected. |
| 2025-10-31 | MC End Time | 12/29/2025 08:00:00 | 2026-03-10T08:00:00Z |
| 2025-10-31 | MC How Affect | 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: Manage Microsoft 365 Copilot in Teams meetings and events | Microsoft Teams | Microsoft Learn Use Copilot without recording a Teams meeting | Copilot in Teams | Copilot | Microsoft Support Compliance considerations QuestionAnswer 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. | |
| 2025-09-06 | MC MessageTagNames | Feature update, User impact, Admin impact | Updated message, Feature update, User impact, Admin impact |
| 2025-09-06 | MC Summary | Microsoft Teams Copilot will default to running without transcription for new meetings starting mid-September 2025, with conversation history now 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. | 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. |
| 2025-09-06 | MC Last Updated | 08/22/2025 02:09:52 | 2025-09-05T19:18:58Z |
| 2025-09-06 | MC Messages | 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 mid-September 2025 and expect to complete by late September 2025. | 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. |
| 2025-09-06 | MC Title | Microsoft Teams Copilot without transcription becomes default for meetings - conversation history now persists | (Updated) Microsoft Teams Copilot without transcription becomes default for meetings - conversation history now persists |
| 2025-09-06 | MC End Time | 10/31/2025 08:00:00 | 2025-12-29T08:00:00Z |
Last updated 2 days ago ago
