Microsoft Teams will strengthen its integration with Microsoft Places through a feature that may seem minor from a technical standpoint but touches a sensitive area of hybrid work: actual work location. Workplace check-in will allow Teams to automatically update whether a person is in the office, remote, or at a specific building when their device connects to a corporate Wi-Fi network or a configured peripheral at a workstation.
The feature is introduced with a reasonable explanation. In companies with flexible offices, multiple sites, reservable desks, and distributed teams, knowing who is physically available can facilitate in-person meetings, coordination among colleagues, and space planning. Microsoft presents it as an extension of presence in Teams and work hours in Microsoft 365, not as a control tool.
Nevertheless, the debate is inevitable. When a corporate platform can automatically infer that an employee is at a specific office, the line between collaboration and surveillance depends less on technology and more on each company’s internal policies. Teams may not be a punch-in system, but an integrated presence signal in workflow could end up being an informal proxy for attendance if not properly governed.
How Workplace check-in works
Microsoft differentiates between planned location and actual location. The first is what the user sets in Outlook or Teams to indicate their intended workspace: office, remote, or other. The second is updated via check-in, either manually or through signals detected in the corporate environment.
Workplace check-in operates on this actual location. If the user is within their work hours and Teams detects a connection to a configured Wi-Fi network, it can update their location to “in the office.” If the company has mapped BSSID identifiers of access points to buildings defined in Microsoft Places, the location can be refined down to the building level. If only SSID is configured, the signal will be more generic.
The feature can also rely on desktop peripherals. If a laptop connects to a monitor or device associated with a reservable workspace, Teams can interpret that the user is in that space or building. According to Microsoft, check-in via peripherals is now generally available, while Wi-Fi-based detection remains in preview and is expected to be widely rolled out soon.
| Technical Element | Function |
|---|---|
| Microsoft Places | Defines buildings, floors, workstations, and work location |
| Teams desktop | Detects network or peripheral changes |
| Corporate SSID | Indicates if the user is on an office network |
| BSSID | Associates access points with specific buildings |
| Desktop peripherals | Confirm presence at configured spots or zones |
| Work hours | Limit automatic location updates to working times |
The most important technical requirement is that Workplace check-in functions with Teams desktop app on Windows or macOS. It is not supported in Teams web or mobile. Additionally, it requires device-level location permissions, so Teams must be authorized in Windows or macOS to access the relevant API.
What Microsoft states it does not do
Microsoft emphasizes several limitations. Workplace check-in does not provide administrators with monitoring dashboards, attendance reports, or real-time location history. It does not track movement nor functions as continuous tracking. Location data is cleared at the end of the user’s defined work schedule and does not update if the connection occurs outside those hours.
Documentation also highlights that users can manually set, change, or delete their work location. They can mark themselves as remote while inside the office or present at a site even if outside. Microsoft argues this is intentional, as the feature aims for coordination, not enforcement of compliance.
Therefore, the architecture does not equate to company GPS or access control systems. It doesn’t display real-time maps, detect office movement, or operate outside configured networks or peripherals. If a user connects via a different company’s network, that signal is ignored.
| Microsoft’s Statement | Implication |
| Not a tracking tool | No real-time movement monitoring |
| No real location history stored | No accessible historical record for admins |
| No attendance reports | Not designed as a punch-in system |
| Cleared after work hours | Real-time signals don’t persist indefinitely |
| Requires OS permissions | Teams must be granted location access | Users can modify their location | Location signal isn’t an absolute proof of presence |
The nuance lies in perception. Even if technically not surveillance, it can feel that way if activated without clear communication or if managers start to use the visible Teams location to pressure for in-office presence.
Situations: Inform, Ask, and Off — three ways to activate a sensitive feature
Workplace check-in is disabled by default at the tenant level. The company must explicitly enable it via policies. For Wi-Fi detection, Microsoft considers three modes.
In Inform mode, users receive a notice when the feature is active and can turn it off. In this mode, location is shared unless the user opts out. It’s the most convenient model for corporate deployment but also the most privacy-sensitive, since it’s activated by default.
In Ask mode, users must actively consent before sharing their location. This approach aligns better with consent principles, as location isn’t shared unless the employee agrees.
In Off mode, the feature is disabled. Users do not receive notices nor can they activate it themselves. The organization can also enforce policies across the entire company or specific groups, such as by geography, site, or department.
| Mode | What Happens | Perception Risk |
| Inform | Enabled with opt-out | May seem imposed |
| Ask | Requires active acceptance | More privacy-respectful |
| Off | Disabled | No automatic signal |
| Manual | User updates location | Less automation, more individual control |
For European companies, Ask appears to be the most cautious option if the goal is to minimize friction with privacy and labor relations. Inform can be suitable in certain environments but requires very clear internal communication, especially if tensions about returning to the office exist.
A challenge for administrators, security, and HR
From an IT perspective, configuring this is not trivial. Administrators need Microsoft Places properly deployed, buildings and floors configured, SSID and BSSID lists associated, workstations or pools defined, and Teams policies applied to users or groups. Different roles are involved: Teams for policy deployment and Exchange for managing SSID/BSSID lists.
This detail matters because a poorly configured deployment can generate unreliable signals. Only configuring the SSID, for example, might cause Teams to indicate someone is “in the office” without specifying the building. Incorrect BSSID mapping could show the wrong building. Mixing guest networks, outdated corporate networks, or poorly documented access points could also reduce accuracy.
For security, the challenge resides in data governance. While Microsoft states that the work location isn’t visible to Microsoft and can only be shared within the organization, the company must define who sees this signal, for what purpose, how employees are informed, and what internal limits are in place.
For HR, the risk is cultural. Workplace check-in can assist in managing hybrid work, but it can also create tension if perceived as a tool for monitoring attendance compliance. Company policies should precede the tool’s deployment, not follow it.
Presence doesn’t measure productivity
This feature arrives at a time when many companies are still redefining their hybrid models. Some have set mandatory in-office days; others maintain flexibility by team; some combine desk reservations, occasional in-person collaboration, and remote work. In all cases, presence technology can be helpful but not a substitute for clear policies.
Knowing someone is in a building helps coordinate meetings. It doesn’t prove they are working better. Seeing someone as remote doesn’t mean lower productivity. Turning location into a proxy for performance would be a management mistake and likely cause conflicts.
The real value of Workplace check-in lies in specific tasks: finding colleagues, planning in-person days, optimizing shared spaces, avoiding unnecessary commutes, and improving team coordination. If used for those purposes, it can provide convenience. If used for surveillance, it will erode trust.
Microsoft has implemented technical limits but cannot control how the tool is socially used within each organization. Therefore, deployment should be accompanied by internal policies: don’t use signals for attendance, avoid creating rankings, don’t link to performance appraisals, and don’t activate it without a clear rationale.
A glimpse into Microsoft 365’s future
Workplace check-in reflects a broader trend in Microsoft 365: integrating digital presence, calendars, physical spaces, and collaboration experiences into a single layer. Microsoft Places aims not just to reserve rooms but to organize hybrid work by combining location, schedules, availability, and spaces.
This approach makes sense for large companies with flexible offices but also increases the amount of work signals within the platform. Teams no longer just show if someone is available, busy, or in a meeting; they might soon indicate where someone is actually working, at least within the boundaries set by the organization.
Adoption is not neutral. A feature designed to reduce manual effort could influence behavior expectations. Regular presence status might lead colleagues to assume that someone not in the office isn’t available for certain tasks. Managers might interpret absence as lack of engagement. Organizations could create pressure without formal reports.
Therefore, the key question isn’t just if Teams can do this, but whether the company needs it, how it will communicate it, and what protections it offers employees. In-person collaboration enhances with good information and trust. If the tool sacrifices trust for data, the overall impact is negative.
Workplace check-in can be a useful feature in well-managed hybrid environments. It can also become another symbol of corporate surveillance if mishandled. The deciding factor will be governance, not Wi-Fi.
Frequently Asked Questions
What is Workplace check-in in Microsoft Teams?
A feature in Microsoft Places that allows manual check-in or detection via corporate Wi-Fi or configured peripherals to update a user’s actual work location in Teams.
Can it show the building where an employee works?
Yes, if the company has set up buildings in Microsoft Places and associated BSSID data with those buildings. If only SSID is configured, the location will be more general.
Does it work on Teams mobile or web?
No. Microsoft states that Workplace check-in requires the Teams desktop app on Windows or macOS.
Can it be used as a punch-in system?
Microsoft clarifies that it is not designed to monitor attendance, does not provide attendance reports to admins, and does not store real location history. However, actual use will depend on each company’s policies.
