Microsoft Teams: Now available - new policy setting for Speaker Attribution in BYOD scenarios - Enabled ON by default

• https://www.microsoft.com/microsoft-365/roadmap?searchterms=488301
• https://learn.microsoft.com/powershell/module/teams/set-csteamsaipolicy?view=teams-ps
• https://learn.microsoft.com/powershell/module/teams/get-csteamsaipolicy?view=teams-ps
• https://learn.microsoft.com/microsoftteams/rooms/voice-and-face-recognition

1. 29 May 2025
   • Tags Feature update, User impact, Admin impact → Updated message, Feature update, User impact, Admin impact

   … this will happen: General Availability (Worldwide, GCC): We will begin rolling out early June mid-July 2025 and expect to complete by late June 2025 (previously mid-June). July 2025.  How this will affect your organization: Previously, speaker attribution was managed using …

2. 29 Apr 2025
   • Title Microsoft Teams Premium: New Speaker Attribution setting for BYOD in CsTeamsAIPolicy (enabled ON by default) → Microsoft Teams: Now available - new policy setting for Speaker Attribution in BYOD scenarios - Enabled ON by default

   Updated April 29, 2025: We have updated the title, timeline, and content. Thank you for your patience. Available now: The new SpeakerAttributionBYOD setting is now available in csTeamsAIPolicy for Microsoft Teams Premium users. This gives IT admins more control over speaker attribution when users join meetings from personal (BYOD) devices. Admins can now configure this setting using PowerShell. If no action is taken, it will be enabled by default starting in early June 2025. NOTE: If you are a Microsoft Teams customer (not a Microsoft Teams … for any user assigned a Microsoft Teams Premium or Microsoft 365 Copilot license, even license—even if your organization previously didn'tdidn’t have these licenses. Therefore, we recommend all organizations review this message, regardless of your organization'sorganization’s current license status. Coming soon: We will add a new Microsoft PowerShell policy setting called SpeakerAttributionBYOD to csTeamsAIPolicy for Microsoft Teams Premium users. This setting gives IT admins more control over speaker attribution in BYOD (bring your own device) scenarios. NOTE: This setting will be enabled by default when the feature rolls out. This setting allows organizations to manage how speaker attribution is used in meetings where … labels (Speaker 1, Speaker 2, etc.) and Microsoft 365 Copilot in shared spaces (meetings, chat). spaces. To access Copilot features, a Microsoft 365 Copilot license is required. This … will begin rolling out early June 2025 and expect to complete by mid-June 2025.late June 2025 (previously mid-June). How this will affect your organization: Before this rollout, the CsTeamsMeetingPolicy has a parameter called RoomAttributeUserOverride that can be set to three values (OFF, Distinguish, and Attribute) to allow admins to manage Previously, speaker attribution for their users. After this rollout, the new settingwas managed using the RoomAttributeUserOverrideparameter in CsTeamsMeetingPolicy. Going forward, SpeakerAttributionBYOD forin csTeamsAIPolicy will controldetermine whether speaker attribution is enabled for meetings joinedused when users join from BYOD scenarios. The new policy setting enables voice-based speaker attribution in shared meeting scenarios where users join using their personal devices Key benefits of this change include: Ensures all participants in the room are recognized and attributed in transcripts Enables users to get the most out of intelligent recap and Copilot insights Enhances meeting room experiences through intelligent audio and video capabilities Higher usage of speaker attribution by removing barriers for licensed users Improved value realization from Teams Premium and Copilot licenses Easier customizable configurations based on customer needs What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before or after the rollout. Review your current configuration to assess The new setting is available now, and admins can begin configuring it using PowerShell based on their organization's preferences. If no action is taken, the impact on your organization. After the new setting rolls out to your organization, you can modify will be enabled by default during the setting using PowerShell if you prefer to disable the feature. rollout in June 2025. If you wishprefer to modify the on by default setting before it rolls out to your organization, the rollout begins, you can do that in May. We will update this message to let you know when you can take this preemptive action. so at any time starting now. Learn more Set-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn Get-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn Overview of voice and face enrollment - Microsoft Teams | Microsoft Learn Learn more about setting up voice enrollment for end users

3. 10 Apr 2025 · first version seen

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.

• Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.