Just had a chat with friends about the possibility and how it would likely be introduced.

Paraphrased into the following;

2.99$/Month
OEM installs have a 2 year license
Upgrades are free for the first year (from 11 to the new)
Comes with Office 365 and AI functionality to soften the blow

What are your thoughts on this?

Teams is down or was down for pretty much everyone I know (work context).

Thinking in terms of business continuity, what is your fallback plan. Is your fallback a managed, enterprise class service?

Might get everyone internally to install Signal since it's end-to-end encrypted, has a desktop client and can handle file transfers. That's just off the cuff.

Thoughts?

Hey! So I used to be fairly warm to MS Teams but I utterly despise its call handling. I have three Bluetooth audio devices that I used regularly - a set of Edifier earbuds, my expensive Sony WH-1000XM5 pair, my CX-5 audio, and my Bluebus that integrates into my old BMW's hands free system. All of these work perfectly fine when I call someone via regular-ass phone calls. When I use Teams, all hell breaks loose. The edifiers work perfectly fine, so I know Teams is QUITE capable of handling these all ok. My CX-5 system won't do microphone audio when Android Auto is connected, but works fine on Mazda's infotainment call handling. In my BMW it won't handle the microphone but plays audio. On my Sony pair of headphones, it works great... And then about every ten minutes it disconnects, consistently, so I can't use them.

In theme with the other ongoing thread, nothing gets my gears moving like tech not doing what I'm asking it to. Teams barely has any options on Android for audio, so there isn't much of anything to tweak. Does anyone have any ideas of where to start? Is there something similar to Windows solutions like Virtual Audio Cable which could set up a virtual BT device to pipe audio through and simulate it being something else for Teams? Thanks all!

Edit2: I'm a mac user who doesn't understand how windows explorer works. Leaving the post for some hapless mac user who may come along. Windows explorer doesn't report how it is traversing the directory tree, leading to some confusion about where the search result is, which happens to be waaaay down in a zip of a mac application installer I had inadvertantly archived on the Windows disk. I would ask any windows users, how do I make powershell ls | select-string "text" behave like ls | grep "text" on unix?

edit3: Also, why the fudge would windows explorer search find <weird characters>net but not dotnet when typing 'net' into the search box?

So I download the occasional, um, linux distro installation video. I use a vpn and private firefox windows for most.

I'm doing some clean up today, and find a file with a bunch of strange characters, including the text characters, "net." "M⌐⌐v├▒├┼⌐▒net" is the filename listed in the properties window. Inside are a series of .ase files with mostly unrecognizable names.

I don't see the filename when doing an ls in powershell of the directory reported in explorer.

doing ls | select-string "net" in powershell results in an unending peristalsis of weird text like you might get from a binary file viewed in a text editor. I do notice, however, that some of the text might be from inside a zip file. But why is select-string searching inside the zip file? ls seems to ouptut only filepath information. Upon further investigation, the zip file is several directories down, it appears adding | select-string to ls makes ls travel the full tree. Wut?

And when I say undending, I mean it kept going until I hit ctrl-c.

Any ideas to what is happening here?

Incidentally, I opened one of the ASE files by right-click->view file in notepad+, which never launched.

Edit: lots of edits.