This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Been using Teams since the start of lockdown with a headset. As of today I am getting a double-beep at about five second intervals (like a hold beep) in the headset when I am muted. This has not happened before and been using same headset for months.
Also note that when I mute / unmute in Teams, the headset now announces "mute on" and "mute off" to me.
This feels like a Teams update has created this "feature" - please turn it off!
Managing sound and video settings during Teams meetings and calls for optimal communication
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
OMG!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! It Works! I can't believe it! The Setting is in Teams.
Only using the browser version of Teams is working for me to avoid the issue, annoying but something. Hope a fix is coming soon.
That worked, thank you! How odd though as config hasn't changed, hopefully it won't reapper.
Same issue occurred recently to my headset Sennheiser HD 450 BT.
Why does it keep beeping when on mute? Is it just prompting you to buy MS certified headsets??
This is indeed a very annoying problem and making users upset against Teams.
Please fix this issue asap.
I was wondering the same thing (annoying beep for non-certified headsets).
I started having this issue this morning during a meeting, I simply turned it off and on again and that got rid of the double beep. At least during the call, I'll have to wait until the next one to see if the issue comes back.