That doesn’t at all match the documentation.

The organization will configure a list of Wi-Fi SSIDs. When your device connects to one of those, the Teams location would be updated to “in the office”.

That’s it. No complex triangulation, no pinpoint locating. Just “are you connected to the office network or not”.

Also, if you don’t want to be tracked in this way, just don’t participate. If your organization sets a policy to opt you in automatically, click the option to opt out. If they give the offer to opt in, just don’t.

I know it’s hip to hate on Microsoft, but we should at least discuss things based on the truth, not wild assumptions and misinformation.

Oh, that. If you read the article, you’ll see that the “toxic waste” was really just used water from the deluge system. Think of it like rinsing off your car and the runoff getting into a river. A good chunk of the water was collected too, so the actual discharge was much less. On top of that, it was later clarified that SpaceX could continue the operations while the permit process was sorted out, which happened a few months after that article IIRC. It was basically a nothingburger that a few commentators tried to blow up.

I’m gonna need a source for that. I follow SpaceX fairly closely (as a fan of the engineering, not Musk), and I can’t think of where this could possibly be happening, even through a wild misunderstanding of a situation.

The lack of a source in that article led me to go looking for something official. Here’s the MS article on the feature: https://learn.microsoft.com/en-us/microsoft-365/places/configure-auto-detect-work-location

What jumped out at me (called out twice in dedicated boxes):

By default, users are opted out of work location detection. Users are prompted to provide consent for automatic location detection in the Teams desktop client on Windows or macOS. It is not possible for admins to consent on users’ behalf.

This just doesn’t seem like as big of a deal as some are making it sound.

They probably replaced HR with AI too, and it messed up the org chart.