Maybe some day people will understand that this "walled garden" is a good thing
https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&c...
I can't recall exactly what I did, it was a while back.
I think one way to combat things like this is to find the launch file disable it and make it unwritable.
chflags +simmutable <launchfile>
Other possibilities are: zero out files and make them immutable, or make the directory for updaters unreadable.Honestly, it's frustrating that installing a daemon doesn't require user consent. Apple doesn't have their priorities right — instead of this legitimately useful feature, they added these annoying runtime permissions for the subdirectories in your home directory.
I had a couple of interviews with a bank and they wanted me to use Teams. I fell through the trap of installing it. Then (by default) plugged itself on my start-up list. "Join by browser" is the best option.
As or the tool, I use from SysInternals the Autoruns.exe. I love this toolkit (for a couple of decades now), I always suggest people to download the SysInternals Suite, cool small exe tools.
Edit: adding the download site: https://docs.microsoft.com/en-us/sysinternals/downloads/sysi...
In your Teams profile settings, have you also unchecked Settings > General > Auto-start application?
(I'm not saying that Teams shouldn't use "Login Items" as the source of truth on this, just that Microsoft provides its own setting for this.)
I like the idea of running apps in their own sandbox, eg using docker container to run an instance.
For macOS, maybe second desktop login just for Teams and then use quick user switching.
Kludge, not a fix.
Working remotely, my SO has to agitate the mouse, like a dead person's switch, to prevent screensaver / lock screen, and to signal to micromanaging PHB continuous attention. Separate user login wouldn't help with that.
So I had a vague memory: go to your account icon > Settings > Auto-start application, and uncheck it.
How silly that people who don't have accounts — because they use Teams infrequently — are subjected to the spammiest behavior.
Maybe it's possible to restrict its access via flatpak or Snap? I have a messenger via flatpak that can't access anything outside the home/Downloads folder, but I can't say whether that restriction applies to other apps as well.
At first, I thought it just happened when I installed the application. But nope — any time I open Teams, it will re-insert itself in my list of login items. This happens no matter how many times I have manually removed it.
I think it even happens more than once per launch because I recently launched it to join a call and then immediately removed it from my login items before the call even started. But after the call, there it was again in my login items.
I have never seen an application behave this way that was not widely considered to be malware.