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 removedWhat changed
Between archive captures, newest firstUpdated May
7,11, 2026: We haveupdated the timeline. Thank youdecided not to move forward with this change at this time. We apologize foryour 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): Wewill begin rolling out in mid-July 2026 (previously late April) and expecthave decided not tocomplete 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 …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 inlate Aprilmid-July 2026 (previously lateMarch)April) and expect to complete bymid-Mayend of July 2026 (previouslyearly April).mid-May). What's changing? Who is affected: Affected tenants: If your TeamsMeetingPolicy was created …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 lateMarchApril 2026 (previouslymid-January)late March) and expect to complete byearly Aprilmid-May 2026 (previously earlyFebruary).April). What's changing? Who is affected: Affected tenants: If your TeamsMeetingPolicy was created …Updated
October 30, 2025:January 14, 2026: We have updated thetimeline 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 inmid-Januarylate March 2026 (previouslyearly November 2025)mid-January) and expect to complete by earlyFebruaryApril 2026 (previouslymid-November 2025).early February). What's changing? Who is affected: Affected tenants: If your TeamsMeetingPolicy was created …Updated
September 5,October 30, 2025: We have updated thetimeline.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 November20252025) and expect to complete by early February 2026 (previously mid-November2025. How this affects2025). What's changing? Who is affected: Affected tenants: If yourorganizationTeamsMeetingPolicy was created or modified before the Copilot without transcriptionbecomes 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 thehost configuration and receive this new default. Custom policiesCopilot without transcription option was introduced, your tenant willremain unchanged. In Teams meeting policy, thenot be affected. What will happen: The defaultproperty value for “Copilot”Copilot policy will change from EnabledWithTranscript toEnabled. This affects how Copilot behaves in newly scheduledEnabled for both new and existing Teams meetingsunless overridden by custom policy. Startingwhere Copilot is allowed. Copilotduring a meetingand Facilitator will no longer automatically starttranscription. Transcriptiontranscription for meetings in affected tenants. Users mustbe manually enabled in Meeting Optionsmanually enable transcription to use post-meeting Copilot or Facilitator queries. Conversation history will persist duringthe meeting if users want post-meeting insightsmeetings for Copilot without transcription. Tenants with TeamsMeetingPolicy created oraccessmodified after June 2024 are not affected. What you can do toCopilot 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 toall 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 Teamsmeeting 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 thenewcurrent defaultbehaviorvalue is desired, update it to a different value, then set it back. Please ensure both TeamsMeetingPolicy andconversation history persistence. Communicateall Custom Policies are updated. PowerShell example tousers howset Copilot policy tomanually 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 bylate Septembermid-November 2025. How this affects your organization Copilot without transcription becomes default: Applies …- Tags
- · first version seen
Linked documentation
Microsoft pages the notice links toThe notice links to no Microsoft Learn or Support page that this installation reads.
Related public evidence
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.