Many new laptops only have USB-C so they don't work with the traditional Jabra and Plantronics Teams/Skype compatible wireless USB-A dongles. Because of this, Bluetooth should be the way forward and it would be ideal if we could expect the same level of full-featured Bluetooth headset functionality across all platforms as what currently exists when using a Skype/Teams certified wireless USB dongle.
This should include the following at a minimum:
- HD call quality
It would be great if you the Teams Devices group could start certifying specific headsets that meet the criteria I mentioned above (no devices currently can do this as far as I'm aware).
This feature is on the backlog. We’ll update when we have more details to share.
Please solve this by incorporating the companion device functionality for 1:1 calls that already exists for Meetings. I regularly need this when I answer calls quickly on my Teams Desk Phone or Teams Mobile Device and then later realize that I want to switch to my headset that is connected to my computer or share/view a screen through my computer.
Back in the day with SfB this wasn't a problem from my desk phone because of BToE, but the companion device functionality would be superior to what we used to even have with BToE.
The feature team has this on their backlog officially now. We don’t have any timing to share at this point, but we will keep you posted.
Alex & the Teams team
Thanks to everyone who volunteered for testing the Office 365 group calendar. The TAP team will be reaching out as we are closer to being ready.
Hi — My apologies for the delay in updating this item. We rolled out a fix a year ago for a specific issue of status changing to away in Teams when you were still active on the device. We thought this had fixed the “incorrect status” issue. From comments below, it sounds like people are still seeing issues.
If you are still having issues, it would be super helpful if you can capture logs by typing Ctrl + Shift + Alt + 1, and send the file from your downloads folder along with device info and detailed repro steps to firstname.lastname@example.org.
Confirming as well that this is now present 👍
This is badly needed for PSTN calls. I needed this for the first time and could not believe that simple 3-way PSTN calling wasn't implemented. I'm hesitant to ever call anyone on Teams now because I always need this feature.
We had to all of our accounts back to Islands from Teams-only because of this.
The original 400+ vote request for this shouldn't have been closed until this was implemented for PSTN calls as well.
We know many of you are waiting for a Teams client for Linux, and we’re pleased to confirm we’re actively working on it. Stay tuned for more information.
The request for 1:1 calling Chrome support is still “on the backlog”.
1:1 calling works in Edge.
Group calling and meetings works for Edge & Chrome.
I hope to have more information to share soon.
Hate to share bad news, but this request was declined by the feature team.
Thanks for your feedback. The transfer to voicemail option is currently in testing and will be released soon.
Note: Direct calls to a users voicemail is a separate feature which is planned. We’ll update when we have more details to share on this one.
Screen share for Chrome is internal testing, and we are hoping to release it this quarter. We’ll keep you posted.
It seems like only contacts that have local tenant Guest Accounts are being migrated over. Please migrate over non-Guest Accounts as SfB contacts (a SfB logo next to them would be even better) to fulfill the promise of feature parity and SfB chat federation.