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)
Teams will not recognise Bluetooth headphones when joining calls.
I have tried restarting, clearing cache, clearing storage and reinstalling. I have tried multiple different models of headphones from completely different manufacturers. I have tried different phones.
This is not a user issue. This is an issue with the application. Several posts have been made.
Please fix it.
EDIT: the 'Nearby Devices' permission will fix this issue in most cases. For me, it worked temporarily (for one call) and then reverted to the same issue. However, the issue does now seem to be fixed - I have had consistent success for about 2 months now. I am assuming that a recent update to the app has fixed an issue that was causing this.
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.
Hi Chris,
I had the same problem, and I noticed it was because of the permission setting of TEAMS.
I reinstalled Teams and accepted the "Nearby devices." access and it works now.
Sabrina
Jayzar
I have used Jabra Elite Active 65t and Google Pixel Buds Pro.
This issue doesn't occur on the iOS version of the Teams app at all, so it is not related to the headphones.
Warm regards
Chris
Hi Chris,
Thank you for the follow up.
I checked your headset and earbuds, and these are not yet compatible with MS Teams.
Since it only happens to a specific device, I suggest to this.
On your earbuds try to turn off one ear bud works for some users, with some ear buds.
Then
Source: https://answers.microsoft.com/en-us/msteams/for...
Lastly, if all the above steps still didn't work, I highly suggest submitting feedback at the portal link.
https://feedbackportal.microsoft.com/feedback/f...
Thank you for your time and collaboration.
Best,
Jayzar
Jayzar, thanks for the suggestion and your continued effort to help.
Whilst these suggestions may work in some scenarios (they didn't for me in this case), they are not really acceptable solutions and are only temporary workarounds at best.
These headphones work flawlessly with teams on windows and on ios.
Suggesting they are not compatible with MS Teams is misleading: the MS Teams android application is not compatible with these headphones, and if the list you have shared is accurate then the application does not even support basic airpods.
It is not a limitation of the headphones (which use the same bluetooth protocol as any other modern headset). This is a serious flaw. Android users are more than half of the mobile device user base. Competing apps like Zoom and Discord have no issue picking up the peripherals attached to a device. The resources available to these development teams would be a fraction of what Microsoft has available.
I have raised a support ticket already. Unfortunately as an end user that is the end of my ability to interact with a global conglomerate like Microsoft. Whilst this may be a community forum and you are not a microsoft employee, your profile suggests you are contracted and paid by them to provide this support service.
I would encourage you to raise a support ticket through mechanisms available to you which are more likely to be seen by someone.
In future I would also encourage you to think more critically about the advice and support you are giving, and try to avoid solutions that basically suggest the user should buy another device because application has an unresolved (and unacknowledged) issue. The issue lies with the application and you should be either escalating this through mechanisms available to you or directly acknowledging this known issue an pointing users to the feedback hub.
I think we are at an end here in relation to moving forward any further. I am hopeful, but not optimistic, that anyone will even read my feedback ticket, but it seems that is the only practical option available.
Hello Chris,
Thank you for the follow up.
I appreciate you for submitting feedback and I appreciate your time and understanding.
Best,
Jayzar