Back to latest version

MC1052162 - Microsoft Teams Premium: New Speaker Attribution setting for BYOD in CsTeamsAIPolicy (enabled ON by default)

Message Center

Metadata at Apr 10, 2025

Published

Apr 10, 2025

Service

Microsoft Teams

Tag

Major change
Feature update
User impact
Admin impact

Metadata changes

Title
Microsoft Teams: Now available - new policy setting for Speaker Attribution in BYOD scenarios - Enabled ON by defaultMicrosoft Teams Premium: New Speaker Attribution setting for BYOD in CsTeamsAIPolicy (enabled ON by default)
Tags
Admin impact, Feature update, Updated message, User impactAdmin impact, Feature update, User impact

Body changes

removed textadded text

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—license, even if your organization previously didn’didn't have these licenses. Therefore, we recommend all organizations review this message, regardless of your organization’organization'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 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.spaces (meetings, chat). 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-Julyearly June 2025 and expect to complete by late Julymid-June 2025.

How this will affect your organization:

Previously,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 speaker attribution was managed usingfor their users.

After this rollout, the RoomAttributeUserOverrideparameter in CsTeamsMeetingPolicy. Going forward,new setting SpeakerAttributionBYOD infor csTeamsAIPolicy will determinecontrol whether speaker attribution is used whenenabled for meetings joined 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 BYOD scenarios.

    Teams Premium and Copilot licenses
  • Easier customizable configurations based on customer needs

What you need to do to prepare:

TheThis 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 impact on your organization.

After the new setting is available now, and adminsrolls out to your organization, you can begin configuring itmodify the setting using PowerShell based on their organization's preferences.

If no action is taken,if you prefer to disable the setting will be enabled by default during the rollout in June 2025. feature.

If you preferwish to modify the on by default setting before the rollout begins,it rolls out to your organization, you can do so at any time starting now.that in May. We will update this message to let you know when you can take this preemptive action.

Learn more