Posted by imalerba 7 hours ago
> And obviously, the mobile app (your pocket spy).
Don't these ask for location permissions? This story is light on details.
I found a lot of news stories about this dating back to where it showed up on the roadmap in early 2025, but none of them with any more implementation details (ie - is it using _only_ WiFi network name, or some other data too?)
Is there anything more than the Wifi SSID stuff below?
> If you connect to a Wi-Fi network that isn't your company's, Teams will simply display the name of that network. So if you decide to take a "working lunch" and connect to "Starbucks_Guest_WiFi", your boss sees it instantly. You can’t hide behind a generic "Remote" status anymore.
So how exactly does this work? It'd be pretty trivial setup my access point to provide a work SSID? How much access does Teams really have to get info to discern your location?
It sounds far less than the diagnostics data I get from a small go binary.
If corporate policy is you can't connect to starbucks wifi, then enforce that at the MDM mangement layer - I assume things like SCCM can do it.
So it sounds like if you want to circumvent this: get a travel router that spoofs a work access point, and make sure any kind of identification requests that would reveal a public IP are either blocked or are going through your work VPN.
Hint: Bossware and most things the MBA's drool over.
Unfortunately, there's enough people out there that are fine with implementing said features if it means they get a paycheck; even if it ruins the world for everyone else.