08-09-2018 08:41 AM
08-09-2018 09:03 AM - edited 08-09-2018 09:15 AM
We don't have dates to share for video calling on chrome yet, but it is on our backlog.
09-05-2018 07:41 AM
FWIW, you can activate the Teams video in Chrome by simply changing the user agent to "Edge 13." I installed the "user agent switcher" Chrome extension. When I want to use video, I simply change the user agent, and it works perfectly. I use it on my Chromebook almost everyday.
The only issue I have seen is that the chat history is cut off in some cases, but I rarely need the chat history while on video.
10-10-2018 02:01 AM
Please priories this and don't try to force Edge on us.
Not having chrome support is a mayor deal breaker for us.
10-10-2018 10:32 AM
I can set the user-agent string in chrome on a physical pc to be"Edge - Windows" and Teams video calls in Chrome will work but this hack doesn't work when i try it on a citrix xendesktop vm where we also want the media to be redirected to the local endpoint instead of the datacenter hosting all the vms. Citrix has implemented the media redirection capability to the local endpoint called Browser Content Redirection (BCR), which can redirect an entire website to the endpoint for local rendering
through a combination of enhancements to their workspace app/citrix receiver which runs on the local endpoint and contains an embedded chrome browser and a new version of their VDA which runs on the vm but Teams video has to supported in the chrome browser for all of this to work without hacking the user agent string.
Can msft provide any more info since it's been 2 months since the last update in this thread saying it was in the backlog as Citrix was promoting this as one video solution for Teams media redirection on XenDesktop in 3Q2018 ?
10-11-2018 02:26 PM
10-11-2018 11:14 PM
Hi All.. since there's been some new comments I wanted to hop in... First off, no one is trying to force Edge on anyone. Certainly you can choose your own browser. I really wanted to ask what is the blocker from using the desktop client? If anything we believe this is the preferred experience. I'd love to know more about the use case for only using the web. Secure or virtual machines maybe? I myself frequently use the web experience but usually to view two conversations at once or to multi task, not for meetings. Thanx for your insight here.
10-11-2018 11:34 PM
10-12-2018 09:26 AM - edited 10-12-2018 09:27 AM
The "blocker" is that Teams will never become a replacement for Skype for Business if you force external guests to load the large Teams full client when they simply want to join a meeting and show video.
Unless you are saying that Microsoft is no longer competing with WebEx, Zoom, and GoToMeeting. Which one providers a better experience for the external guest today? Teams is dead last without an easy-to-use plugin or WebRTC support for major browsers.
10-15-2018 02:04 AM
The desktop client on Linux is rubbish, cant join meetings. Then try and use it in chrome and its just as bad...
10-25-2018 12:31 PM
@Karuana GatimuI can echo other users' concerns here:
When hosting meetings for external participants it is critical that we have easy-to-use, functional meeting solutions.
The former, "easy-to-use" part has been done fantastically; arrows pointing to different parts of the screen to direct permission grants, and no required download is an excellent user experience (a further improvement here would be to detect when audio is coming through a different device than selected, and point the user to the "select device" screen).
The functionality needs work. External participants, who are often far from tech-savvy, do not want to download a client and install it. They don't want to use a different browser (they often don't even know what a browser is). They want to click the "Join" button and be in the meeting. With the amount of work the Teams development team has done with making the "Join on Web" option user friendly, this should a no-brainer and shouldn't be surprising. Otherwise they will just punch some buttons on their phone, a familiar device, to join audio-only, where we will lose all of the collaborative edge that Teams offers.
Like others have stated, "Use Edge" is not an acceptable solution. Quite frankly, with market share numbers being what they are, work on the web client should have started with Chrome.
11-20-2018 06:45 PM
Hi Karuana - also wanted to chip in here that the need for us is really focused around external users - whether they don't want to (prefer not to install software) or can't (security settings block the launch of .exe that aren't whitelisted for example, or Windows Firewall kicks in and requires admin to allow access). This is particularly common in environment where users are on Windows 7, and the the only "modern tech" they are able to use happens to be a Chrome browser.
Thanks for the ask for feedback!
11-20-2018 07:38 PM
11-20-2018 08:27 PM
The deskop client is fine, but getting it set up for Guest access to a meeting is clunky and bug ridden for us in all of our testing. Guests are required to sign up for teams, they must have a microsoft account, then go through the process that can take up to an hour to activate.
This is hardly the user experience we want when inviting guests to meetings when we can just use Zoom or some other meeting system with far less friction that Teams.
11-29-2018 02:34 PM
Totally agree. Moreover even "Edge" isn't fully featured for Teams as apparently it can only "receive" a screen share, not initiate one. You completely missed the mark on this product Microsoft if the intention is to compete in the Collaborative Meeting space. Its especially frustrating when the MS sales people tell you that Edge and Chrome will provide you a full meeting experience for external meeting participants without having to install a client and then you find out that:
1. Edge cannot start a screen share, it can only receive one.
2. Chrome cannot start video or a screen share but it can receive them.
This seems very much like an intentional limitation meant to promote the use of the Edge browser as there is no technical, or logical reason that this cannot be done on Chrome.
12-03-2018 05:39 AM
Not everyone on my team chooses and can reasonably choose to work on Windows/Mac. No client for Linux.
Browser remains the only choice. Unfortunately, that is not a solution until we can voice chat in Chrome, without workarounds.
12-11-2018 08:26 PM
12-18-2018 09:25 AM
Got the same thing. Was so looking forward to a favorable experience in server 2016 but found that we still can't use the camera with chrome, Edge isn't an option in server 2016, and the desktop app doesn't work properly for us.
01-16-2019 07:05 AM - edited 01-16-2019 09:01 AM
Not the same thing, but I found that I can get Chrome to work if I spoof the User Agent string of Microsoft Edge.
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Edge/18.17763
02-12-2019 11:51 AM
The deal breaker for us with the desktop client is the lack of multiple signed in accounts. My group is a hodgepodge of consultants and we all have the Teams desktop client open + multiple browsers to be signed into all our organizations. When one of us needs a screen share or video conference we have to play this ridiculous game of logging in and out of the desktop and browsers. Having feature parity on browser video + screen share will be a welcome band-aid.
To be honest at this point it is just easier not to use teams at all. There are so many other headaches in addition to this one that we're having a very low user adoption rate. The consensus is that this is another half baked enterprise solution for collaboration that users are doubling down on all the services that teams was meant to replace.
03-04-2019 07:13 PM
03-15-2019 04:57 AM
This is a major shortcoming. We love Teams but need easy, clean and native browser support for external guests.
Without even so much as a date to point to, we are now forced outside of the Microsoft stack.
03-15-2019 05:27 AM
Microsoft: I do like where you are heading with Teams, and would like to embrace both internally in my company and recommend to all our clients, but as long as you are unable to deliver a friction-free all-browser user experience I cannot do that. I find it both surprising and frustrating that this is even a topic in 2019.
03-15-2019 08:42 AM
@Paal Berggreen Honestly, at this point, it seems intentional. Everyone expects online meetings to just work in a browser. We invite users from outside of our org to work in Teams with us. They should be able to use a browser. I've met with a member of the dev team and shared the same feedback. This has got to be the single biggest barrier to adoption for many organizations. In fact, if we don't have full web functionality for meetings by May, we're leaving the product (and we're a paying customer with an EA - not a free customer). I honestly just don't think this is a priority. It's a two-year-old product. We shouldn't be having this conversation at this point.
03-18-2019 04:00 AM
@Dwayne Alton Thanks for sharing. What was the comment from the dev-guy you met with? Is the problem that they don't really recognize that this issue is an issue at all, or more that they have too much technical debt and stuff to deal with that it's simply a challenging task? It would be nice to know their "official" take on this.
03-18-2019 09:24 AM
@Paal Berggreen He was clear that he doesn't speak for Microsoft's "official" position, and I got the impression that the dev team members are focused on specific areas and don't necessarily set the big-picture direction. That being said, it was apparent that it was not a priority. Regarding high-level direction, he expressed that they focus on a "single pane" philosophy and that they focus on the "richness" that can be delivered through a installed (fat-client) software, versus browser-based (thin-client) direction. I've heard the same response from other Teams team members when I've participated with online AMAs.
To add context, I was at an education event when we spoke (I work in EDU). In EDU, Teams is Microsoft's Learning Management System and has education-specific features that may not be apparent to most users. I add that info just to say that I believe this gentleman may have been better prepared to discuss the EDU features than overall priorities. But he did seem surprised at my focus on lack of browser support. I think a key issue is that Microsoft staff use Microsoft fat clients and see it from that perspective.
We recently had some MS staff (unrelated to Teams) at the office and we showed them the Teams web interface and the pretty awful tablet-based interface. The tablet version (the Android version can run on Chrome OS) made them cringe. We also showed the issues with meetings in the web version. Both of them used Teams daily and had never seen those UXs. We discussed how they used Teams and I posed a simple question. We currently use Google Hangouts Meet for things like remote bid meetings, interviews, etc. We send them a URL. They join in a browser. How would I accomplish this with Teams without the user installing software? They said . . . you can't. I think the MS staff need to get out of their bubble and embrace having "the best software on any platform" that Mr. Nadella set as their direction.
03-19-2019 01:59 AM
Thanks for the elaborate reply. This sadly confirms the impression we have at this point, official or not: browser-based UX is not a priority for MS. Meaning we are forced away from Teams for meetings with external parties. And when that works so well, internal meetings will follow.
The Chrome plugin is available now and has been since at least Dec 13: Microsoft Teams Screen sharing
We had mixed results within our company. When you click Share Screen in Teams web on Chrome, you should be prompted to insall that plugin. When done, you can then share your screen. However, some users are not prompted, they are told screen sharing is not supported in their browser (even though it is Chrome) and they are encouraged to install Teams desktop. We do not currently know the "secret" to making this work for all users.
yesterday - last edited yesterday
Sorry to hear it doesn't work with Chrome OS or Linux, I use neither so know zero about them.
I narrowed down the external user failures a bit more. I was investigating this not working for external users we invited via their email. I've concluded that users who do not have a Teams account cannot share their screen when using Teams web (it's possible there is an admin setting for this, I've asked our admins to check). I then created a Teams Free account using my personal email and the share button was now enabled, but the experience was diminished; i.e. it showed PPT and a files browse button, but not show screen 1 or show screen 2, which I generally use.