Teams is written using web technologies so you're getting the same experience as the app.
Besides, there is a very satisfactory feeling when something doesn't work for whatever reason, you do a quick search and see that apparently you must edit some awfully named HKEY_LOCAL_MACHINE register or rename some <username>/AppData to .old (just had to do this yesterday, wild), and then, when the quick fix doesn't work, instead of trying to look for more fixes you just give up and start cussing until the VM is restored to a working backup.
Then they do absolutely crazy weird things!
I recently got a new laptop. My account is `adavis@<domain>.com`, my user name on my old laptop using that account is `adavis`.
What did Windows 11 do when I create my user on laptop. Oh it makes my user name `adavi`, yes it truncated my username.
After scouring the internet, trying a few different things to rename my account to no avail, nothing worked! Until I found a command to bring up an account management window that looked dated to the win 2k era ish (and can't be found via any settings window). It allowed me to create a local account with the name `adavis`. I then logged into it, deleted my `adavi` account then was able to associate my new local account with my Microsoft account.
Only "proper" solution is to /not/ sign into your MS account when seeting up the new machine for the first time. Create a local account with the name as you want it, and then only afterwards link it with your MS account (if you have to).
Only problem is, latest Win11 installer does not allow you to create a local account anymore at all. So you need to install Win10, do the work-around-dance, and then upgrade to Win11. I only relaized this after halway through my most recent format.
Every time when I ssh into one of my other boxen, I have to remember now to go 'SSH myname@ip' else windows helpfully defaults to 'mynam@IP'
In the "Let's connect you to a network" page, use these steps:
* Use the Shift + F10 keyboard shortcut to open Command Prompt.
* Type the following command to release the current network configuration and press Enter: oobe\bypassnro
Note: The command is a single phrase without spaces.
Note2: This will reboot the machine and restart the installer again (why?? because fu for not wanting a MS account that's why)
You can create a file ".ssh/config" in your user directory, just like under linux, and inside of it put "User myname", and ssh will use that as a default and you won't have to specify it with @ everytime.
Thankfully I only use it for some cross-platform testing and occasional gaming.
"The New Goliaths: How Corporations Use Software to Dominate Industries, Kill Innovation, and Undermine Regulation"[1] looks like a good book on the subject that I plan on reading.
[1]: https://www.amazon.com/New-Goliaths-Corporations-Industries-...
It is not quite a requirement, I have my Windows 11 Pro running just fine with no Microsoft account. They do attempt really hard to make it look like it's required though. Even going as far as showing a fullscreen app after Windows update that only has options for registering or login, but luckily Alt+F4 closes that abomination.
Install flight simulator on a Win10 PC with local login only and launch -> sign into an xbox account -> after you enter your name and password, you get a dialog box where you have to agree to sign your Microsoft Account on that PC with two dark pattern options that lead to the same result.
I couldn't find any combination of group policy editor, registry, and services.msc around it. You can either close it and lose access to the game you just paid for, or proceed and then you get your account signed into email and a bunch of other crap you dont want and have to spend hours getting rid of all traces of that account in your system(but it's never 100% gone). Only way to bypass it is to buy the game through Steam.
Between MacOs Linux and Microsoft, Microsoft has the last respect for you as a user and nobody should use it if they don't have to.
I suppose they might make it mandatory unless you have some special version of Windows which is hard to buy (like LTSC). But make it too hard they risk that market. Anyway, now bypassing it involves opening a command prompt window, only the more technical users will do so, and that’s a small enough minority they probably aren’t missing much.
During the pandemic, a key security component of our remote work architecture was to use Azure AD Conditional Access to restrict users to login in M365 apps from AD joined laptops + some Inutne compliance rules.
A weird situation was that, for a new laptop, we could not login using a domain account, as it was not joined in our domain. We also could not create a local account to join it. Not sure how IT solved that.
They can either remove that policy from their azure AD, or remove the machine from the azure ad.
Or update their policies to allow for azureAD joined machines.
Multi-accounts are really painful with most chat clients I have encountered. It sometimes makes me miss e-mail where the inside/outside distinction doesn’t exist.
Desktop Teams allows you to join multiple calls at once, and switch between them is easy.
Web browser teams disconnects you from one meeting to join another. The only solution is to open multiple browser profiles, each for different call, and then manage the 'mute tab' manually. Additionally, web browser edition has something to detect if tab is active, and will downscale / delay video stream if tab is not active. This is extremely annoying when you have meeting active on one monitor, and want to double check what is being discussed on another.
Saying all this, web browser teams at least works. Desktop one stops working because as the whole discussion here points out, accounts get mixed up. I can't join team meetings anonymously because desktop edition thinks I have an account, but when I try to login it tells me my account doesn't have Teams enabled.
