> Microsoft confirmed that starting March 2026 (delayed from January), managers will be able to see your real-time location. And no, disconnecting from the office Wi-Fi won't save you.
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?
> SSID, signal strength, BSSID, private IP, public IP, ipv6, all trivially available to a binary running on a machine.
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.
If it's only just the teams app that's doing it, but I'm not sure if that's a safe assumption. There's a crap ton of Microsoft stuff installed on my laptop by default, and the IT admins install stuff all the time.
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?