Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 02:30 UTC Customize Public modeDiscuss ChangeIntel on Discord

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

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Roadmap
478611

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions this installation saw
  • Seen 11 May 2026 mid-July 2026, end of July 2026
  • Seen 7 May 2026 late April 2026, mid-May 2026 → mid-July 2026, end of July 2026
  • Seen 6 Mar 2026 late March 2026, early April 2026 → late April 2026, mid-May 2026
  • Seen 14 Jan 2026 mid-January 2026, early February 2026 → late March 2026, early April 2026
  • Seen 31 Oct 2025 early November 2025, mid-November 2025 → mid-January 2026, early February 2026, June 2024
  • Seen 5 Sep 2025 mid-September 2025, late September 2025 → early November 2025, mid-November 2025

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, with source markup removed
Updated May 11, 2026: We have decided not to move forward with this change at this time. We apologize for any inconvenience. 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 have decided not to move forward with this change at this time.  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. What you can do to prepare: 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 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.

What changed

Between archive captures, newest first
  1. Updated May 7,11, 2026: We have updated the timeline. Thank youdecided not to move forward with this change at this time. We apologize for your patience.any inconvenience. Introduction We’re updating the default behavior of Microsoft Teams Copilot in meetings. … 365 Roadmap ID 478611. When this will happen General Availability (Worldwide): We will begin rolling out in mid-July 2026 (previously late April) and expect have decided not to complete by end of July 2026 (previously mid-May). move forward with this change at this time.  What's changing? Who is affected: Affected tenants: If your TeamsMeetingPolicy was created …

  2. Updated March 6,May 7, 2026: We have updated the timeline. Thank you for your patience. Introduction … this will happen General Availability (Worldwide): We will begin rolling out in late April mid-July 2026 (previously late March)April) and expect to complete by mid-Mayend of July 2026 (previously early April).mid-May). What's changing? Who is affected: Affected tenants: If your TeamsMeetingPolicy was created …

  3. Updated January 14,March 6, 2026: We have updated the timeline. Thank you for your patience. Introduction … will happen General Availability (Worldwide): We will begin rolling out in late MarchApril 2026 (previously mid-January)late March) and expect to complete by early April mid-May 2026 (previously early February).April). What's changing? Who is affected: Affected tenants: If your TeamsMeetingPolicy was created …

  4. Updated October 30, 2025:January 14, 2026: We have updated the timeline and the content. timeline. Thank you for your patience. Introduction We’re updating the default behavior of … this will happen General Availability (Worldwide): We will begin rolling out in mid-Januarylate March 2026 (previously early November 2025) mid-January) and expect to complete by early FebruaryApril 2026 (previously mid-November 2025).early February). What's changing? Who is affected: Affected tenants: If your TeamsMeetingPolicy was created …

  5. Updated September 5,October 30, 2025: We have updated the timeline.timeline and the content. Thank you for your patience. Introduction We’re updating the default behavior of … this will happen General Availability (Worldwide): We will begin rolling out in mid-January 2026 (previously early November 20252025) and expect to complete by early February 2026 (previously mid-November 2025. How this affects2025). What's changing? Who is affected: Affected tenants: If your organizationTeamsMeetingPolicy was created or modified before the Copilot without transcription becomes default: Applies to new tenants and new users. Existing users without a set policy will inheritpolicy 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 host configuration and receive this new default. Custom policies Copilot without transcription option was introduced, your tenant will remain unchanged. In Teams meeting policy, thenot be affected. What will happen: The default property value for “Copilot” Copilot policy will change from EnabledWithTranscript to Enabled. This affects how Copilot behaves in newly scheduled Enabled for both new and existing Teams meetings unless overridden by custom policy. Starting where Copilot is allowed. Copilot during a meeting and Facilitator will no longer automatically start transcription. Transcriptiontranscription for meetings in affected tenants. Users must be manually enabled in Meeting Optionsmanually enable transcription to use post-meeting Copilot or Facilitator queries. Conversation history will persist during the meeting if users want post-meeting insightsmeetings for Copilot without transcription. Tenants with TeamsMeetingPolicy created or accessmodified after June 2024 are not affected. What you can do 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 appliesprepare: 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 all users using Copilot without transcription. What you can do to prepare Review your organization’sretain current behavior: Update Global and Custom TeamsMeetingPolicy settings via TAC or PowerShell. TAC UI Portal: Navigate to Teams meeting policies for dependencies on transcription defaults. Update internal documentation and training to reflectAdmin Center and set the Copilot policy default value as required. For example, if the newcurrent default behaviorvalue is desired, update it to a different value, then set it back. Please ensure both TeamsMeetingPolicy and conversation history persistence. Communicateall Custom Policies are updated. PowerShell example to users howset Copilot policy to manually enable transcription when needed, especially if they want to retain Copilot insights after the meeting.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 | …

    • Tags Feature update, User impact, Admin impact → Updated message, Feature update, User impact, Admin impact

    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. … this will happen General Availability (Worldwide): We will begin rolling out in mid-Septemberearly November 2025 and expect to complete by late Septembermid-November 2025. How this affects your organization Copilot without transcription becomes default: Applies …

  6. · first version seen

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 27 Oct 02:30 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current