Microsoft is gearing up to introduce a new feature in Microsoft Teams that will automatically update an employee’s office location when their work device connects to a corporate Wi-Fi network. Dubbed “Workplace Check-in,” the feature is slated for general availability in June 2026, according to a newly surfaced entry on the Microsoft 365 public roadmap. While it aims to simplify hybrid work coordination, the passive tracking mechanism has already ignited a fierce debate over workplace surveillance and employee privacy.
The move comes as organizations worldwide continue to refine their hybrid work strategies, seeking tools that provide visibility into office attendance without reverting to manual processes or invasive monitoring. Workplace Check-in is not an isolated product tweak; it is part of Microsoft Places, an AI-powered workplace intelligence platform that leverages data from Outlook, Teams, and now Wi-Fi networks to optimize in-person collaboration. Yet the exact details of how it will function, what controls users will have, and how data will be handled remain largely undisclosed, leaving IT administrators and employees with more questions than answers.
How Workplace Check-in Works
At its core, the feature is straightforward. An organization’s IT department will designate trusted corporate Wi-Fi networks within the Microsoft Places or Teams admin center. Once configured, any Windows, macOS, iOS, or Android device running the Teams client will automatically detect when it connects to one of these networks. The device then sends a presence update to Teams, marking the user as “In the Office” on their status card and within the Places colleague finder. This status can then inform room booking systems, hot-desking assignments, and even provide aggregated occupancy analytics for facility managers.
This passive check-in eliminates the need for users to manually update their location in Teams or Outlook, a step many employees forget or find cumbersome. The roadmap description explicitly states that the feature “updates an employee’s office location when their work device connects to an organization’s configured Wi-Fi network,” suggesting a seamless, background process that requires no user interaction. While convenient, this very automation is what gives pause to privacy advocates.
For organizations using Microsoft Places, the check-in data feeds into a broader ecosystem that includes floor plans, wayfinding, and the ability to see which colleagues are on-site. It also integrates with Teams’ “People” card, potentially displaying a user’s physical workspace location to their entire team by default. This level of visibility, while useful for impromptu meetings, introduces new concerns about who can see location data and how it might be misused.
The Privacy and Security Thunderstorm
The instant a feature passively tracks your presence based on network connectivity, alarms go off. The primary issue is consent. While most employees accept that their corporate device connects to company Wi-Fi for security reasons, using that same connection to broadcast physical location represents a significant leap in inference. Roadmap details are silent on whether users will receive a clear opt-in prompt, if IT admins will have the ability to enforce the feature for all users, or if there will be a global toggle within the Teams client to disable it.
Given Microsoft 365’s typical model, it’s likely that this feature will be controllable through administrative policies. But the default setting—whether opt-in or opt-out—will be critical. If it’s on by default with no explicit notification, many employees may unknowingly broadcast their office presence. This could lead to a chilling effect where remote-first workers feel pressured to show up in person just to maintain a digital footprint, or conversely, where employees who work from a nearby coffee shop with a strong corporate Wi-Fi signal are mistakenly marked as present.
Accuracy is another technical hurdle. Wi-Fi location tracking is notoriously imprecise. A device connecting from a parking lot, an adjacent building, or even a VPN that routes through the corporate network could trigger a false office check-in. Conversely, areas with poor Wi-Fi coverage inside the office might fail to register, creating gaps in data. Microsoft has not clarified whether additional signals like GPS, Bluetooth beacons, or IP geolocation will augment Wi-Fi data to improve fidelity.
Data retention and access policies are equally opaque. If an employer can see a detailed log of when an employee was in the office and for how long, that data could feed into performance reviews, attendance tracking, or even disciplinary actions. While Microsoft’s own privacy documentation for Places emphasizes that location data is “private by default” and only shared with the user’s consent for room finding and people insights, it’s unclear whether Workplace Check-in will adhere to the same framework or operate outside it. The fact that the feature is being introduced via the Teams client rather than the dedicated Places app might signal different data-handling rules.
Microsoft Places and the Broader Push for Workplace Intelligence
To understand Workplace Check-in’s context, we must look at Microsoft Places. Revealed at the 2023 Ignite conference and gradually rolling out throughout 2024 and 2025, Places is Microsoft’s answer to the hybrid work puzzle. It uses AI to interpret calendar signals, Outlook RSVPs, and manual check-ins to help users decide which days to come into the office, find available desks, and see who else will be present. The platform is available as part of the Teams Premium license and integrates deeply with Exchange, SharePoint, and the Microsoft Graph.
Workplace Check-in adds a new, passive data stream to this engine. Instead of relying on employees to proactively mark their location, Places will now infer it from their network connection—a method that many large organizations have already been implementing with custom-built solutions. By building it directly into Teams, Microsoft is commoditizing an enterprise-grade presence detection system and making it available to any company with a Microsoft 365 subscription.
This aligns with a broader industry trend of workplace analytics tools that measure office utilization, often to inform real-estate decisions. Products like Cisco Spaces, Juniper Mist, and OEM solutions from HP and Dell already offer similar capabilities. Microsoft’s advantage is the seamless integration with its collaboration suite, potentially making Teams the single pane of glass for all things workplace. However, that integration also amplifies privacy risks because the same platform that hosts your private chats and performance reviews now also knows your physical comings and goings.
What We Know and What We Don’t
The roadmap entry for Workplace Check-in (feature ID yet to be assigned publicly) is sparse. It was added in early 2025, with a targeted release of June 2026 for General Availability across all Teams platforms—desktop, web, and mobile. The entry carries a simple tag of “Microsoft Teams” and “Microsoft Places,” indicating it will likely be controlled through the Places admin experience. No detailed documentation, Microsoft Learn articles, or message center posts have accompanied the listing, which is unusual for a feature that significantly alters the user’s relationship with their device.
From a technical standpoint, the feature likely relies on the existing network location awareness APIs available in Windows and mobile operating systems, which already allow Teams to know whether a user is on a domain-joined network for conditional access policies. The check-in capability may be an extension of those APIs, combined with the Places service running in the background. It’s also possible that the feature will require a specific update to the Teams client and backend services, which would explain the long lead time to June 2026.
For IT professionals, the most pressing unknown is administrative control. Will this feature be part of a new policy in the Teams admin center? Will it require a separate license for Places? Can it be scoped to specific user groups or network segments? Silence on these points is fueling organizational anxiety about potential shadow rollouts or surprise changes to the default configuration.
The User Perspective: Convenience vs. Surveillance
From an employee’s standpoint, the feature carries a duality. On one hand, automatically marking yourself as in the office saves a few clicks and ensures your colleagues can find you for last-minute whiteboard sessions. It also feeds into the “colleague finder” tool, which many find genuinely useful for building social connections in a distributed workforce. No one wants to walk to an empty floor only to discover everyone is remote that day, and this feature could reduce such frustration.
On the other hand, the shift from active to passive location sharing removes agency. When you manually set your location, you make a conscious decision about whether and when to broadcast your presence. A Wi-Fi check-in robs you of that moment of deliberation. If you are in the office but want deep-focus time and prefer not to be disturbed, the automatically updated presence might work against you. And for employees who value flexibility, the knowledge that their network connection is being monitored for attendance could feel intrusive, poisoning the trust between employer and employee that is essential for hybrid work to thrive.
This tension is not new. In 2020, Microsoft faced backlash over the “productivity score” in Microsoft 365, which critics said enabled workplace surveillance. The company quickly added privacy controls and emphasized that the tool was for organizational insights, not individual monitoring. With Workplace Check-in, Microsoft risks reopening that debate, especially because location data is inherently more sensitive than email metadata or document collaboration patterns.
What Organizations Should Consider Before June 2026
With more than a year until the targeted launch, businesses have time to deliberate. The first step should be a privacy impact assessment: what data will be collected, who will have access, and for what purpose? If the primary goal is office density measurement, then aggregated, anonymized data could suffice, and the individual-level check-in might be overkill. If the goal is enabling colleague coordination, then an opt-in model with clear consent would be appropriate.
Employee communication is key. Organizations intending to use this feature should start conversations early, involving workers in the decision-making process and drafting transparent policies. They should also pressure Microsoft to clarify technical and policy details well in advance, so that configuration can be tested and refined before the feature hits production tenants.
IT teams should also evaluate network infrastructure. If your company’s Wi-Fi coverage extends beyond office walls, you may need to reconfigure access points or implement signal-strength thresholds to avoid false check-ins. Integrating this feature with existing visitor management and security systems could add another layer of complexity, requiring cross-departmental collaboration between HR, facilities, and cybersecurity.
The Road Ahead
As the June 2026 deadline approaches, expect a flurry of documentation, message center notifications, and likely a few major announcements at Microsoft Ignite 2025 previewing the feature. Microsoft has a history of adjusting course based on early feedback—witness the rapid changes to the original Microsoft Places permissions model after tester input. Whether similar adjustments will be made to Workplace Check-in’s default settings or data scoping is an open question.
The feature sits at the intersection of two powerful currents: the push for efficient, data-driven facility management and the growing demand for digital privacy rights. How Microsoft navigates this divide will influence not only its own ecosystem but also the broader market for workplace analytics tools. For now, the roadmap entry serves as an early warning: the office of the future will know when you’re there, whether you tell it or not. The challenge for all stakeholders is to ensure that convenience does not come at the cost of trust.