Microsoft has quietly launched a feature that could redefine how hybrid workplaces track attendance and coordinate in-person collaboration. Starting in June 2026, Microsoft Teams can automatically update a user’s office location using Wi-Fi network data, provided both the organization and the individual employee enable it. The capability—officially dubbed Workplace Check-in—moves the app beyond self-reported presence and into passive, network-based location detection, raising fresh questions about privacy, consent, and trust in the modern workplace.
The rollout comes after a year-long private preview with select Microsoft 365 enterprise customers. The company positions the feature as a productivity enhancer: when Teams knows you’re in the office, it can surface relevant information like hot desk availability, floor plans, and nearby colleagues, while also helping managers understand who’s on-site for spontaneous meetings. But for employees, the idea of their device automatically broadcasting their location can feel like a step too far.
How Wi‑Fi‑based workplace detection actually works
Workplace Check-in relies on existing Wi‑Fi access points that are already mapped in the organization’s network. IT administrators configure specific Wi‑Fi identifiers—such as SSIDs or BSSIDs—as corporate locations within the Teams admin center. When a user’s laptop or mobile device connects to one of these trusted networks, Teams compares the network fingerprint against the admin-defined mapping. If matched, the app sets the user’s office location to the corresponding campus, building, or floor.
Crucially, the feature does not use GPS, IP geolocation, or Bluetooth beacons. Microsoft’s engineers have stressed that the method is intentionally coarse: it pinpoints a device only to the granularity of a Wi‑Fi coverage area, which could be an entire floor or a section of a building. The goal is to answer one binary question—“Is this employee on the corporate network?”—rather than track precise movements throughout the day.
The location update happens silently in the background and then appears in the user’s Teams profile as their current office presence. This presence, in turn, feeds into other Microsoft 365 experiences: Outlook calendar can show a “Working in [Office]” status, the Teams org chart reflects in‑office availability, and scheduling assistants can suggest times when a colleague is expected on‑site.
The privacy cabinet: What employees control
Because location tracking is sensitive in any jurisdiction governed by GDPR, CCPA, or similar regulations, Microsoft has baked opt‑in mechanics into both ends of the equation. On the administrator side, the feature is off by default and must be explicitly turned on via policies in the Teams admin center. An IT policy alone, however, cannot activate check‑in for any user unless the user gives individual consent.
When an organization enables the capability, employees receive a notification in Teams prompting them to enable Workplace Check-in. The notification explains which Wi‑Fi networks have been designated as corporate, what data is collected (network name, device MAC address, timestamp), and how the information influences presence. Users can accept, decline, or ignore the prompt. If they decline, their presence remains purely manual—they can still type “In office” on their own, but Teams will never infer it from Wi‑Fi.
Those who opt in can later revoke consent at any time from the Teams Settings > Privacy menu. There they’ll see a toggle labeled “Workplace Check-in” alongside a log of the last 30 days of location updates. Microsoft emphasizes that the raw network data does not leave the device: the client calculates the location match locally and then simply sends a “check-in” event to the company’s Microsoft 365 tenant. The event does not include the underlying SSID or BSSID, only the office identifier that the admin mapped.
To guard against misuse, alerts are triggered if an admin changes the list of trusted networks or if the feature is turned on for users who previously opted out. Tenant-wide audit logs record every toggle change, and Microsoft Purview compliance tools can generate reports on location-based presence data.
IT administration and policy controls
For IT managers, setting up Workplace Check-in is a straightforward, if multi‑step, process within the Teams admin center. The first requirement is a building‑aware infrastructure: organizations must define their campuses, buildings, and floors using the Microsoft 365 Place Editor, a tool that integrates with Microsoft Places. Once the physical hierarchy is in place, admins navigate to “Meetings” > “Workplace Check-in” and add the Wi‑Fi networks that correspond to each location. The interface supports bulk import of BSSID lists exported from common network controllers such as Cisco Catalyst or Aruba Central.
Policy granularity extends to user groups. Through group‑based policy assignment, companies can enable check‑in for only, say, the corporate headquarters while leaving regional offices excluded. Conditional Access can be paired so that Workplace Check-in only functions when the device is also compliant with Intune policies, ensuring unmanaged personal devices never accidentally report a location.
One under‑discussed aspect is bandwidth. Because the check‑in mechanism relies on a lightweight REST API call that fires only when the network connection changes—such as waking from sleep or switching SSIDs—Teams generates negligible additional traffic. Microsoft estimates less than 5 KB of data per check‑in event.
The hybrid work equation: Why Microsoft is betting on passive presence
Microsoft’s reasoning is rooted in the messy reality of hybrid schedules. Despite the proliferation of collaboration tools, many teams still struggle to coordinate in‑person days. A 2025 internal survey by Microsoft’s own research division found that 62% of employees never update their Teams location field, rendering it useless for colleagues trying to find them. Workplace Check-in aims to solve that with zero effort from the user.
When the office location updates automatically, the Teams calendar can display building‑specific room suggestions. The “People in my building” feature, which shows colleagues who are physically nearby and available for a quick chat, becomes more accurate. For managers, Microsoft Places—the company’s evolving workplace experience platform—can generate aggregated, anonymized insights about office occupancy trends without exposing individual trajectories.
Early adopters in the manufacturing and healthcare sectors report notable efficiency gains. A U.S.‑based medical device maker told Microsoft that, after a three‑month pilot, they saw a 22% reduction in “ghosted” meetings—instances where someone scheduled a conference room but never showed up—because the system could automatically release the room when the organizer was detected as working remotely. Similarly, a European engineering firm used the data to optimize their cafeteria staffing based on weekly in‑office peaks.
Trust, surveillance anxiety, and the road ahead
Despite the productivity pitch, Workplace Check-in taps into deep‑seated fears about workplace surveillance. Civil liberties groups and labor unions have already voiced concerns that passive location tracking could be repurposed for performance evaluation or used to penalize employees who choose to work remotely. Microsoft’s response highlights three guardrails: the dual consent requirement, the inability to track individuals in real time (presence updates are batched and not streamed), and the administrative monitoring built into the system.
Still, the trust deficit is real. “Once the infrastructure exists to track your office attendance via Wi‑Fi, it’s a small technical step to extend that to monitoring break times or even correlating it with badge swipes,” warns Dr. Elena Vos, a digital ethics researcher at the University of Amsterdam. She points out that while Microsoft’s documentation prohibits using the data for disciplinary purposes, such contractual prohibitions are often ignored in practice, especially in jurisdictions with weak labor protections.
Microsoft has indicated that the next iteration of Workplace Check-in will introduce noise‑reducing algorithms that only update presence after a minimum dwell time (e.g., 15 minutes) and will allow users to temporarily override their automatic status with a “stealth” mode for sensitive conversations. There’s also talk of integrating with Copilot, Microsoft’s AI assistant, to suggest optimal hybrid schedules based on teammates’ confirmed in‑office days—a move that could either streamline coordination or deepen the anxiety, depending on implementation.
For now, what matters most is clear communication from employers. Experts recommend that companies rolling out the feature couple the technical enablement with a transparent policy document, a frequently‑asked‑questions internal site, and an open door for questions during all‑hands meetings. The success of Workplace Check-in will ultimately be measured not by the bytes of data it collects but by the trust it builds—or erodes—between workers and the organizations that deploy it.