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 (meetings, chat).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 early Junemid-July 2025 and expect to complete by mid-Junelate July 2025.
How this will affect your organization:
Before this rollout,Previously, speaker attribution was managed using the RoomAttributeUserOverrideparameter in CsTeamsMeetingPolicy has a parameter called RoomAttributeUserOverride that can be set to three values (OFF, Distinguish, and Attribute) to allow admins to manage speaker attribution for their users.
After this rollout, the new setting. 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 transcriptsEnables users to get the most out of intelligent recap and Copilot insightsEnhances meeting room experiences through intelligent audio and video capabilitiesHigher usage of speaker attribution by removing barriers for licensed usersImproved value realization from Teams Premium and Copilot licensesEasier 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 impact on your organization.
After theThe new setting rolls outis 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 your organization, you can modify the setting using PowerShell if you prefer to disablebefore the feature.
If you wish to modify the on by default setting before it rolls out to your organization,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