Well they are just lying, it works fine with Firefox and has worked fine for years. I live in the EU though. Sucks to be american these days, I guess?

Just one more upside to Firefox, less interruptions during work~

This is not mildly infuriating this is the free internet being eroded through Google’s control of Chrome

Its cool how all these companies are allowed to just lie to you about their products functionality.

Try changing your user agent to a Chrome one (e.g. Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36). Works a treat!

This is likely legacy code. Firefox used to have a lot of issues with WebRTC, so practically all video conferencing systems blocked it. Teams probably has some "block Firefox because it doesn't work properly" check that was written 5+ years ago and none of the current developers are even aware of its existence.

Well-coded ones did feature detection instead of checking the user-agent, meaning they automatically started allowing Firefox as soon as it implemented all the required features.

Feature detection is usually the way to go. If your website / webapp depends on a particular feature, check if that specific feature exists, rather than checking for particular browsers. Browser checks are still needed in some cases, for example Safari sometimes reports that it supports particular features but it really doesn't (or they're so buggy to the point where they're unusable), but that's relatively rare.

Ms teams sucks in a big way

This team block is so agressive to firefox users that it's literaly hardcoded as if web browser firefox then deny.

You cam override that by changing a parameter in firefox to advertise itself as another we browser. I don't remeber how i did it but, once i had to use firefox and i just changed that stting in order to advertise me to the host as a edge browser. With that changed i could use teams as normal.

Epic drm.

I used to freelance for a big corp who used MS teams and provided me with separate credentials, while also having my private MS account, that I occasionally use for other corps I worked for.

It was a hell using it that way. I had to run each one in a private Brave window to be able to work on two different accounts.

I know they only use MS teams, bc their infra is all based on MS, and it probably works fine for them internally. But man, this shit needs to be fixed in some way to account for external people, especially the ones who chose their own stack and work simultaneously with others.

given the love Teams receives, it not working in [ insert browser ] is definitely a feature

Have you tried changing your user agent string to Chrome? I know it can sometimes sidestep these types of "errors". It can be changed manually through about:config under general.useragent.override, or there exists plenty of addons to switch it more easily.

Im sure if you swap user agent to chrome they wouldn't give a fuck

I works for me without a user agent change if I enter through the Microsoft 365 teams workspace and not a teams share link.

It really can't. If you spoof the user agent it'll crash immediately after a call starts.

I suspect they use something extra on top of normal WebRTC.

can't, or won't?

On a bullshit teams call right now. I'd call it not working a feature 😄

Remember when Internet Explorer/Edge was only used to download Chrome. Well, ironically these days I only use Chrome to make video calls.

Teams also doesn’t support multiple “work” accounts

Firefox lets you have completely separate profiles with separate accounts (URL: about:profiles, it can't be linked to for security reasons) and also an official extension to have another layer of profiles on a per-tab basis (containers).

yet

Pfft!

I'm in Linux, I had so much problem with FF and Teams that I installed Edge and Teams as a PWA, no more problem with calls and video