Open Bug 1623340 Opened 4 years ago Updated 9 days ago

Microsoft Teams: video not supported in Firefox

Categories

(Web Compatibility :: Site Reports, task, P1)

Desktop
Unspecified

Tracking

(firefox86 affected, firefox102 affected)

ASSIGNED
Future
Tracking Status
firefox86 --- affected
firefox102 --- affected

People

(Reporter: juergen.gmach, Assigned: denschub)

References

()

Details

(Keywords: webcompat:site-wait, Whiteboard: [wfh][see webcompat.com bug for dupes])

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36

Steps to reproduce:

I logged into https://teams.microsoft.com and tried to start a video call.

Actual results:

Video call button is greyed out and it reads "Video isn't supported in your browser yet".

Expected results:

Button should be active and clickable.

(I am aware that this is possible a bug/missing implementation by Microsoft, but I was asked on Twitter to report this as a bug here. https://twitter.com/hellosct1/status/1240236803275309056

Also, maybe you have better connections to Microsoft to get this going. These are the times of forced home office, and video conference is utterly important. Thanks!)

Thanks for the report! I agree this is important.

We were tracking this issue with our webcompat bugs, you can read about it here: https://github.com/webcompat/web-bugs/issues/25070

The short is: it more of a Microsoft support issue. They have indicated in the past that they might work on changing their code in the future, but so far have not done (it seems).

I have been trying to find the right contact for this decision at Microsoft, but haven't had luck yet.

Severity: normal → critical
Type: enhancement → task
Component: Untriaged → Desktop
Priority: -- → P1
Product: Firefox → Web Compatibility
Hardware: Unspecified → Desktop
Target Milestone: --- → Future
Version: 74 Branch → unspecified
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [wfh]

Is this because Teams uses h265 for video? Do they actively refuse any other codec? Or do they simply discriminate against Firefox? I noticed this in the SDP offer: o=mozilla...THIS_IS_SDPARTA-74.0.1

I also read on webcompat that the audio degrades to 722 (I have verified this is the case for me as well), even though Firefox offers Opus? What's the deal?

Would like to update that we are working with Microsoft now to get Teams support enabled in Firefox. There are no commitments on when that will be, but I can share that support is moving along in the right direction.

Summary: Microsoft Teams does not work with FireFox 74 on Ubuntu 18.04 → Microsoft Teams: video not supported in Firefox
Whiteboard: [wfh] → [wfh][see webcompat.com bug for dupes]

Tier-3 FreeBSD

I can get video but not audio.

From Teams meetings (camera and microphone) with Firefox on FreeBSD : teams:

Does the web interface to Teams require AudioWorklets? For Web Audio API …

A fix would be for Firefox to spoof its own user-agent string, so it represents itself as whatever the latest version of Edge is.

The functionality works, but Microsoft is blocking it through user-agent sniffing. Same applies to Skype.

Firefox could spoof the user-agent when any Microsoft site is visited (based on a list of primary domains, perhaps). This would also get rid of any messages persuading users to switch to Edge.

Microsoft are making another big push to make users switch to Edge, by deliberately crippling functionality of their own websites and web apps when accessed through a different browser.

In addition to the HTTP User-Agent, changes may also be needed to data in the window.navigator object to circumvent this.

A few months ago Teams video seemed to work OK with a UA override.

Would be interested to know what messages are in the dev console, particularly JavaScript errors - e.g. is it trying to use a Microsoft proprietary API (based on UA), or perhaps a newer standards-track API Firefox has yet to implement?

One possibility is it is detecting a UA mismatch between requests for different domains - do you get the same behaviour if you set the UA override for all domains?

Given that Teams supposedly works on Chrome, a useful test might be a Chrome UA - at least that would eliminate proprietary API usage.

Now, of course, the latest Edge is Chromium-based, whereas a few months ago it was still IE-based, so they will be completely different under the hood.

Obviosuly clicking Give feedback to Microsoft won't help a single iota.

jake, would you like to join me in Mozilla Discourse? Discussions of results of UA testing can become unexpectedly long; I hesitate before discussing in Bugzilla.

Thanks.

The issue still occurs.
https://prnt.sc/w3fnub

Tested with:
Browser / Version: Firefox Nightly 86.0a1 (2020-12-14)
Operating System: Windows 10 Pro

https://bugzilla.mozilla.org/describekeywords.cgi#webcompat:site-wait

Issues where we've done outreach and are waiting for the site to make a change

(In reply to Adam Stevenson [:adamopenweb] from comment #3)

… we are working with Microsoft …

∴ keyword webcompat:site-wait … yes?

https://bugzilla.mozilla.org/buglist.cgi?keywords=webcompat:site-wait&resolution=---

This extension https://addons.mozilla.org/en-US/firefox/addon/teams-phone-fix/ fix the issue, at least for me.

@pachainti Thnk You!
Although, this extension allows me to Join meetings. but it gets disconnected in few seconds.

Just a note here, that the duplicates list on https://github.com/webcompat/web-bugs/issues/25070 is huge.

And that Microsoft knows about it.

(In reply to pachainti from comment #11)

This extension https://addons.mozilla.org/en-US/firefox/addon/teams-phone-fix/ fix the issue, at least for me.

I just tried it, and video from me goes out but I only get audio from the other party, i.e. video doesn't work.

Please, let's avoid adding noise to this bug – essentially, it's webcompat:site-wait.

Instead: vote, then discussion of possible workarounds can be in the more generalised Mozilla discussion linked from (comment #6) above.

Thanks

Assignee: nobody → dschubert
Status: NEW → ASSIGNED

Sorry for the noise Graham, but doing Bugzilla clean-up on some issues, I must comment if the issue is still reproducible, as it is.

Tested with:

Browser / Version: Firefox Release 100.0.2 (64-bit)/ Firefox Nightly 102.0a1 (2022-05-24) (64-bit)
Operating System: Windows 10 PRO x64

Everyone is talking about video, but does audio calling actually work for anyone? I couldn't find a corresponding issue.

No audio for me as well :(

Using current Firefox Nightly (106.0a1 (2022-09-05) (64-bit)) and I can see the telephone symbol to make audio calls to colleagues via the web version of Teams, but when clicking on it I have the message "Try a different browser: This feature isn't available yet for your browser. Try the web app with Microsoft Edge or Google Chrome, or switch to the desktop app.". Then I can close the message or "Download the app". Hence, audio calling is not possible currently with Firefox (Nightly).
If I change the user agent to be Edge, I can make calls and all, except seeing the desktop sharing of others.

Can you tell me any progress? What about the roadmap of Microsoft and their rollout regarding Firefox (as also mentioned here: https://github.com/webcompat/web-bugs/issues/25070)?

I can confirm that video / audio calls and screen and windows share works on firefox 104.0.2 on Linux with UA WIndows/Edge 44
Incoming video / screenshare does NOT work

I am using 104.0.2 (64-bit) on Windows 10 and the video option is disabled. No video devices show up in the Device Settings section even though the corresponding Audio devices (mics) are present.

(In reply to d00d from comment #22)

I am using 104.0.2 (64-bit) on Windows 10 and the video option is disabled. No video devices show up in the Device Settings section even though the corresponding Audio devices (mics) are present.

Change User Agent to EDGE/Windows

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Severity: critical → --

UPDATE! I am using Firefox 107 with faking user agent to windows / Chrome 87 and EVERYTHING works like a charme

incoming audio/video
outgoing audio/video
screen share and outgoing

(In reply to eth from comment #25)

UPDATE! I am using Firefox 107 with faking user agent to windows / Chrome 87 and EVERYTHING works like a charme

incoming audio/video
outgoing audio/video
screen share and outgoing

@eth: Does directly calling someone work for you when faking UA? I am just curious, because without faking the UA it does not display the Call icon on my side. And sometimes faking the UA makes my Firefox go crazy about the sound settings (microphone and speakers, as I can choose from different sources for both).

I used it yesterday on Microsoft instance, on latest Firefox stable, without faking the user agent.

I can confirm that incoming video was working fine, at least for some of the participants (I believe the ones I couldn't see were facemuted)... despite that Teams showed a message explaining that if I want to see incoming videos I should switch to the app...

However I couldn't make my video work. Here is how it went:

  1. I clicked the invite link.
  2. I was on the "configuration" page (not sure what the official name is) where I can enter my name and configure audio/video. Firefox asked for permission for the camera and the mic.
  3. I accepted both permissions, but couldn't see my camera in the interface. The option was also greyed in the interface.
  4. I joined the meeting. The same happens then: no camera from me, and the option to choose a camera input is greyed.

Hope this helps, I also hope this can be solved soon.

I managed to make it work under Archlinux with the custom UA string:
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.3112.101 Safari/537.36
Audio and video work. I haven't checked screen share yet.

Video calls are working now on Firefox 109 on manjaro with no change of user agent. At some point in one call the video got choppy so I turned it off and on again and it was fine. Otherwise it works well.

I tested firefox 109 on openbsd with no change of user agent and video does not work. The video looks like it's working, but when you when people join the meeting, I can't see their video and they can't see mine. It also says "hold on" every few seconds.

I've also tested other firefox versions with various fake user agents and none of them work. Other webrtc meeting sites work with no issue.

When I joined a meeting the other day, it worked for me. Today, I noticed that video calls are not an option but you can start a meeting with video. However, while I could see my own video and they could see mine, I couldn't see theirs. Seems it works very unreliably.

110.0b7 (dev edition) abruptly exits meetings just after joining.
a "regular" 109 lets me participate in the meeting correctly.

Duplicate of this bug: 1815327

The new version of the Teams web client (as opposed to "classic Teams") appears to officially support Firefox, including video/voice calling - see https://learn.microsoft.com/en-us/microsoftteams/new-teams-desktop-admin#new-teams-client-availability

Video calling worked for me on latest Firefox Nightly (though I assume the latest release version would also work)

You need to log in before you can comment on or make changes to this bug.