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.
Update: Our IT noticed this works in Edge and IE, I don't know how long this has been the case? But it doesn't work in Firefox or Chrome so no use to use as we use Linux (and the electron wrapper to use teams on linux).
I'm still surprised there hasn't been more people bringing up this issue.
Just want to ping this again as i still see the option in the webinterface but it just says 'Comming soon"
Either remove the option or please provide an update to what is happing with it.
The Web UI has has the buttons for Video and Call however these are still not available and have been "Coming Soon" for months.
Given there is no Linux client this is critical to ours teams adoption and would be a suitable stop gap until a Linux client is available with video and calling.
I'm posting this in a hopeful attempt that it moves up the list and gathers a response from the Teams support so we can see the progress of this feature.
2 votesElric Hindy shared this idea ·
Hey guys, thanks for the feedback – we hear you loud and clear. After talking this over with the Engineering team, I confirmed this will remain on the backlog and we are actively considering how to accelerate.
Tweet me if you have any questions! @skprufo
This is a majorly disappointing to be put on the backlog.
At least please complete the Web UI with Video and Call support so our linux based teams can use the full features of teams until a native linux client is ready.
Maybe unfortunately for MS, however most companies working in development, which have a major uptake of Teams, are on both linux and MS envs and this really inhibits our ability to put this forward over Slack.
A big requirement for our team, the web app works well for the moment but is missing the key feature of voice and video chat that are marked as 'coming soon'. However local clients always win out.
The feature team is still reviewing, there is lots of discussion about this item and I hope to have a decision soon.
Although the concept seems good, I think it would pollute the idea of teams as a way to get rid of almost all but external e-mail. I Find E-Mail an distraction compared to the teams workflow and communications and think it would limit proper adoption of this great communications platform.
I wouldn't be against an e-mail notification system in teams that allows you to open it in the i.e office365 web page to reply and possible to add e-mail body to a channel for discussion but not to edit, send and create e-mails. This is a chat app not an email client, Say no to E-Mail :)
This should be working via the web client.
Can users confirm if you are still having this issue? Please let me know in the comments below.
I am surprised there is not more noise on this feature.
We have a large proportion of our team on Linux and a fully functionally web app would be ideal.
AS well as the bonus of being able to work completely through the web for all other MS products would complete the solution.
At lease adding a call feature would be the minimal ideal
Thanks for all of the feedback on this. The feature team is taking a look at this request again, and I hope to have good news to share soon.
The slash command changes are still in the works. I hope to have more details to share soon.
Hate to be the bearer of bad news. This item has been declined. There will be no work to hide or remove the reply button.
As many people have commented, a big ask is to help improve how people distinguish between giving a reply and starting a new message.
For that the focus will be on this item. “Better visual delineation between `Reply` and `Start a new conversation`”