How to enable Speaker Recognition in BYOD Teams meetings

Question

I am trying to use a Microsoft Teams intelligent speaker (Yeaklink MSpeech) in Teams meetings to generate a meeting Transcript with Speaker Recognition .

The MSpeech is plugged into my PC USB. I have a M365 Copilot (Premium) Licence (which I assume is what you need for BYOD). My IT Support confirm that Microsoft Teams Set-CsTeamsAIPolicy is set with -Identity Global -SpeakerAttributionBYOD Enabled

When I start a Teams meeting and turn on transcription, the transcript does not identify meeting participants seperately when in the same room. Can anyone help?

Answer 1

Hi @Sam Wardill, 

Welcome to the Microsoft Q&A forum. 

Thank you very much for reaching out regarding the issue with speaker identification when using your Yealink MSpeech Intelligent Speaker in Microsoft Teams meetings. I appreciate your detailed explanation and the troubleshooting steps you have already taken. 

I understand how important accurate speaker attribution is for your meeting transcripts, especially when multiple participants are in the same room. I’d be happy to clarify what’s happening and guide you in the right direction. 

1/ About the AI‑generated suggestion you received 

The recommendation provided by the AI is valid within certain meeting policy configurations. 
However, in your specific BYOD scenario using an Intelligent Speaker, Microsoft now manages speaker attribution primarily through the CsTeamsAIPolicy specifically the SpeakerAttributionBYOD setting.  

Because of this change in how BYOD scenarios are handled, adjusting SpeakerAttributionMode in the Meeting Policy may not impact your setup. 

2/ What actually controls speaker recognition in your scenario 

For BYOD setups using devices like Yealink MSpeech, Microsoft requires: 

• SpeakerAttributionBYOD = Enabled (Your IT team has already confirmed this is set correctly.) 
• Transcription must be enabled in Meeting Policy 
• Without a voice profile, Teams will display “Speaker 1/2/3” instead of real names. 
• Participants must select the MSpeech as the meeting microphone. This helps ensure the device audio is used for best recognition accuracy. 

3/ Why your PowerShell command failed 

The error: 

The term 'Set-CsTeamsMeetingPolicy' is not recognized…  

means your local PowerShell session does not yet have the MicrosoftTeams module imported or connected. 
You would first need to install/import the module and run Connect-MicrosoftTeams before the cmdlet becomes available. 

4/ Recommended next steps 

To ensure accurate speaker attribution in your transcripts, please verify the following with your IT admin: 

• Transcription is enabled in Teams Meeting Policy: 

Set-CsTeamsMeetingPolicy -Identity Global -AllowTranscription $True 

• All participants in the room have created their Voice Profile in Teams: 
  Teams > Settings > Recognition > Create voice profile 
• Participants select MSpeech as their audio device when joining the meeting. 
• When joining the meeting, make sure to choose Room Audio instead of Computer Audio, so the Intelligent Speaker features can activate correctly.

Once these items are complete, Teams should correctly identify each in‑room speaker by name. 

For additional information, you can refer to these articles: 

• Use Microsoft Teams Intelligent Speakers to identify in-room participants in a meeting transcriptio… 
• New Teams policy setting for Speaker Attribution on personal devices | Topedia Blog 
• Fixing Connect-MicrosoftTeams Not Recognized: A PowerShell Survival Guide (Basic Expert) - DEV Co… 

Please note that this information is being provided by the moderator solely for your convenience. The referenced sites are not managed or overseen by the moderator, and therefore we cannot guarantee the accuracy, security, or suitability of any software or content available there. We recommend reviewing all information carefully and ensuring you understand any associated risks before following suggestions from the provided link.  

5/ Contact Microsoft Support   

In case you require more in-depth guidance or support for these steps. I strongly recommend contacting your organization's IT administrator, who can submit a support request to Microsoft through the Microsoft 365 Admin Center. They’ll be able to access system-level information to investigate the issue thoroughly and provide assistance. At the very least, they can offer the most effective workaround to ensure your experience remains smooth and secure.      

We kindly ask for your understanding that, as moderators, we do not have access to the administrative tools or permissions required to investigate or modify these configurations. We also do not have the capability to initiate remote sessions for direct assistance. Our role is to guide users to the appropriate resources and support channels.     

I hope this information is helpful. Should you have any further questions or need additional assistance, feel free to reach out.   

I look forward to hearing your thoughts on this. 

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have any extra questions about this answer, please click "Comment".  

Note: Follow the steps in our documentation to enable email notifications if you want to receive email notifications related to this topic.   

Answer 2

@chris duong I accepted your answer. However, it would be useful for you to edit the answer to add the bit about joining the meeting with Room Audio instead of Computer Audio.

Answer 3

Hi. Your comments helped a bit. The key thing that got it working for me is when I realised that the pc with the speakerphone needs to join the meeting with Room Audio and NOT with Computer Audio!