Share via

Microsoft Teams intelligent speaker attribution not working BYOD

Mario Marrese 0 Reputation points
2026-03-24T16:20:38.2566667+00:00

Hello

We are trying to use Microsoft Teams intelligent speaker in Teams meetings to generate a meeting Transcript attribution using the voice recognition feature.

We have a Yealink A20 Meeting Bar in our meeting room , that isn't in MTR mode, but BYOD.

This means that when a user connects their Laptop to the A20 meeting bar using a WPP30 dongle, the peripherals are mapped as separate devices (echo canncelling Mic, speaker and camera).

When I start a Teams meeting and turn on transcription, the transcript does not identify meeting participants separately when in the same room.

There appears to be mixed and confusing guidance online on how to achieve Speaker Attribution when hosting a teams call. Some guides suggest that dedicated Teams Certified speakers/mics are required (e.g. Yealink MSpeech) and some suggesting that laptop microphones / speakers can achieve this

Steps we have performed

  • Executed the powershell commands against our default "Global" policy

User's image

  • Waited 48hrs after executing the commands.
  • We have enrolled our voices.
  • Users who initiate the Teams call have Microsoft Business Premium with Copilot licenses.
    User's image
  • Selecting Room Audio will attempt to dial in the "Meeting Room" selected, however the meeting room isn't configured with Team Room pro lciense or linked to the Yealink A20 (UC provider e.g. Team Room) . The call will time out.

User's image

Links used

https://learn.microsoft.com/en-us/microsoftteams/rooms/voice-recognition#byod-

https://support.microsoft.com/en-gb/office/use-microsoft-teams-intelligent-speakers-to-identify-in-room-participants-in-a-meeting-transcription-a075d6c0-30b3-44b9-b218-556a87fadc00

Any help would be much appreciated.

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Audio and video
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ian-Ng 11,235 Reputation points Microsoft External Staff Moderator
    2026-03-24T19:03:39.1766667+00:00

    Hi @Mario Marrese,  

    Thank you for raising this issue. In Microsoft Teams, Intelligent Speaker attribution (showing each in-room person’s name in transcripts/captions instead of “Speaker 1/2/3”) is dependent on a few specific prerequisites—most commonly licensing, policy configuration, and voice profile enrollment.  

    1) Confirm the meeting room scenario is supported 

    Speaker attribution with Intelligent Speakers is supported in: 

    • Microsoft Teams Rooms (MTR) environments that are licensed with Teams Rooms Pro.  
    • BYOD (Bring Your Own Device) rooms where the meeting host has a Teams Premium or Copilot license. 

    2) Verify speaker attribution is not disabled by policy (admin-controlled) 

    Your Teams administrator can control whether speaker attribution is enabled via policy. Users may need to confirm the setting that allows Teams to automatically identify them in meeting captions and transcripts (if user override is enabled in your environment). 

    3) For BYOD scenarios, validate the Teams AI policy setting 

    In BYOD cases, speaker attribution can be governed by the Teams AI policy setting SpeakerAttributionBYOD (Enabled/Disabled) using PowerShell (Set-CsTeamsAIPolicy). If this is disabled, attribution may not work as expected in BYOD meetings. 

    4) Check known service limitations that can prevent attribution 

    Confirm that the meeting includes no more than 20 invitees with enrolled voice profiles, as this is the current capacity limit for attribution.

    User's image

    5) Open a Support request for deeper investigation 

    If the prerequisites above are confirmed (supported room scenario, voice profiles enrolled, and policies enabled) and attribution still does not work, I recommend opening a Microsoft Teams support request. A Teams support agent can review tenant policies, meeting settings, and relevant diagnostics to investigate further and provide configuration guidance tailored to your environment. For detailed instructions on how to get support, please refer to Get support - Microsoft 365 admin.  

    I hope these troubleshooting procedures help resolve the issue. Should you have any further questions, please feel free to reach out.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.