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 Premium customer), we are sending this message to you because this new setting will take effect automatically for any user assigned a Microsoft Teams Premium or Microsoft 365 Copilot license—even if your organization previously didn’t have these licenses. Therefore, we recommend all organizations review this message, regardless of your organization’s current license status.

This setting allows organizations to manage how speaker attribution is used in meetings where users join via personal devices, helping enhance the in-meeting and post-meeting experience with features like speaker labels (Speaker 1, Speaker 2, etc.) and Microsoft 365 Copilot in shared spaces. To access Copilot features, a Microsoft 365 Copilot license is required.

This message applies to Teams for Windows desktop and Teams for Mac desktop.

This message is associated with Microsoft 365 Roadmap ID 488301.

When this will happen:

General Availability (Worldwide, GCC): We will begin rolling out mid-July 2025 and expect to complete by late July 2025. 

How this will affect your organization:

Previously, speaker attribution was managed using the RoomAttributeUserOverrideparameter in CsTeamsMeetingPolicy. Going forward, SpeakerAttributionBYOD in csTeamsAIPolicy will determine whether attribution is used when users join from BYOD scenarios.

What you need to do to prepare:

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 setting will be enabled by default during the rollout in June 2025.

If you prefer to modify the setting before the rollout begins, you can do 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