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.
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.
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!
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.
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.
I just had to switch to New Teams last week because Classic teams just continued to have more and more call drops and connection problems. The New Teams doesn't even have an option to change the notification sound, and now I can't move the banner that appears in the top center of the screen when screen sharing that covers up tabs in browsers and the main preferences/search dialog in VS Code...also a Microsoft product. Apparently no one at Microsoft noticed that one of their most used products used in the most normal way blocks out important functionality from another one of them.
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).
The other issue I have with conferencing apps on browsers is that they request access to your microphone even if it's a one-way audio session (i.e. webinar). It should be set in a way where you can separately join a meeting with audio without allowing access to your microphone.
You can use multiple work accounts in the app, have some clients that have their clients give them accounts to communicate internally with them. Just have to keep switching.
Microsoft made their minecraft website complete in functional for Firefox. You can't even download the launcher without chrome.... And I don't understand why. What in the world do they need chrome features that Firefox hasn't?
It's never worked on FF for me. I installed Chromium just to be able to log into several Teams accounts. And tabs are still not working. Classic Microsoft mess.
Yeah, as far as I know it's not some browser chauvinism, but Firefox not supporting some multimedia protocols, that doesn't mean it's Firefox fault though, I'd install some chrome fork just for this kind of interactions