Microsoft Teams Will Tell Your Boss When You Were in the Office

The Feature: Wi-Fi Joins In, Teams Posts the Attendance

PCWorld managing editor Hans-Christian Dirscherl reported on June 15, 2026 at 7:14 pm PDT that Microsoft Teams is launching a new "Workplace Check-in" feature in June 2026. The feature extends the existing Teams "check in at a building" and "check in at a reserved workspace" features. When an employee's phone or laptop joins the company Wi-Fi network, Teams updates that employee's work location to show the building in which they are working. The location update is then posted to a per-employee office-attendance record a manager can view.^[1]

Microsoft's own description of the feature, as quoted in the PCWorld piece, is direct. "Checking in at your workplace via Wi-Fi is an extension of the existing features for checking in at a building or a reserved workspace, offering greater flexibility and user-friendliness to facilitate coordination with colleagues. When users connect to their company's Wi-Fi, Teams will soon be able to update their work location to show the building in which they are working. This feature is disabled by default. Tenant administrators decide whether to enable this feature, and end users always have the choice to allow or decline the sharing of this information."^[1]

Microsoft also clarified what the feature does not do. The feature "does not track employees' movements with precise location data. Instead, it detects when a device connects to the company office's Wi-Fi." The signal is a binary in-or-out-of-the-building flag. The signal is not a continuous location trace. The qualifier matters for the technical scope of the feature, but it does not narrow the privacy posture. The posture is: a manager can see, on a per-employee record, on a per-day basis, whether the employee's device was on the company Wi-Fi that day. The posture is the same posture regardless of whether the underlying signal is precise or binary.^[1]

The rollout timing is what it is. Microsoft has been postponing the Workplace Check-in launch since late 2025. The current Microsoft 365 roadmap lists June 2026 as the rollout date. The PCWorld piece is the first English-language report on the feature. The piece was originally published on PC-WELT, the German sister publication of PCWorld, and was translated and localized for PCWorld's English-language audience.^[1]

The Wi-Fi Signal: Why the Building Is a Building

The signal the Workplace Check-in feature reads is the Wi-Fi probe request. A Wi-Fi probe request is a low-level network primitive that a phone or laptop emits automatically as it scans for the SSIDs of the networks it has previously joined. The probe is not a user gesture. The probe is not a tap on a "connect" button. The probe is emitted continuously by the device's Wi-Fi radio, in the background, even when the device is asleep, in a pocket, on a charger, in a meeting room down the hall.^[2]

The probe request is the technical primitive the entire employer-surveillance market sits on. The Hubstaff, ActivTrak, Time Doctor, and Microsoft Productivity Score features all read the same signal. The signal is what tells the platform that the device is on the office Wi-Fi, and the office Wi-Fi is the proxy for "the device is in the office building." The building-level inference is accurate enough for the attendance purpose the Workplace Check-in feature is designed for. The building-level inference is the entire reason the feature does not need precise location data. The building-level inference is the reason the feature is, technically, low-friction.

The building-level inference is also the reason the feature is high-friction on the privacy side. The Wi-Fi probe is emitted by the device continuously. The probe is emitted regardless of whether the user has opened Teams, signed into the company Wi-Fi portal, accepted any opt-in dialog, or in any other way consented to the data flow. The probe is a side effect of the device's normal Wi-Fi behavior. The only way to suppress the probe is to either turn off Wi-Fi entirely on the device, turn off the auto-join behavior for the company SSID, or carry a device that has never been told about the company SSID.

The privacy-relevant asymmetry is the asymmetry between the watcher and the watched. The watcher (the IT admin, the manager) is the one who configured the feature. The watched (the employee) is rarely the one who configured the feature, is rarely informed that the feature is enabled, and is rarely given a per-device opt-out that is prominent enough to be discovered. The structural posture is: a default-on data flow from the device, gated by a setting the employee does not control, surfaced to a viewer the employee may not have known was reading the data. The posture is the same posture that the Mott Poll measured on the family-surveillance side. The posture is the same posture that the police-surveillance side uses for ALPR data and the federal-surveillance side uses for location data. The posture is the surveillance-default posture. The Workplace Check-in feature is the workplace-surveillance version of the posture, deployed by the platform the entire office stack runs on.

The Tenant-Admin Opt-Out: Why the Structural Posture Is Surveillance-by-Default

Microsoft's three-part posture on the Workplace Check-in feature is, in order: (1) the feature is disabled by default at the org level, (2) the tenant administrator (the IT admin) decides whether to enable it for the organization, and (3) the end user can "always" choose to allow or decline to share. The three parts are all true. The three parts are also not symmetric. The first part gates the feature at the org level. The second part makes the IT admin the gatekeeper. The third part is the only part that is technically a user-side opt-out, and the third part is conditioned on the first part having been enabled at the org level.^[1]

The structural issue is what happens in practice. In a typical enterprise, the tenant admin is a member of the IT or workplace-experience team, and the IT or workplace-experience team is responsive to the management layer that is rolling out the return-to-office program. The return-to-office program is the program the Workplace Check-in feature is designed to support. The IT admin enables the feature because the management layer asked for the data. The end user is told, at most, that a new feature is available in Teams. The end user is not told the feature will surface the data to their manager. The end user is not told the feature is enabled by default once the IT admin flips the switch. The end user is not told the feature is reading a Wi-Fi signal that is emitted regardless of whether the user opens Teams.

The end-user opt-out is the third part of the three-part posture, and the third part is a switch in a settings menu most employees will not find. The end-user opt-out is not a consent dialog at device-pairing time. The end-user opt-out is not a per-day check-in that requires affirmative user action. The end-user opt-out is a toggle that, if the employee finds it and flips it, prevents Teams from updating the work location when the device joins the company Wi-Fi. The toggle does not stop the device from probing for the company SSID. The toggle does not stop the IT admin from reading the Wi-Fi association data at the access-point layer, if the IT admin wants to. The toggle stops the integration of the Wi-Fi data into the Teams office-attendance record.

The structural posture is the surveillance-default posture. The default is "the feature is on if the IT admin enabled it." The employee who wants the feature off has to (a) know the feature exists, (b) know where the toggle is in Teams settings, (c) know that flipping the toggle does not stop the Wi-Fi probe at the OS layer, and (d) take the action. The employee who does not know, does not find, or does not act is in the data set. The data set is the office-attendance record. The record is the manager's view. The manager's view is the return-to-office program. The return-to-office program is the program the feature was designed to support. The chain is the chain. The chain is the same chain the family-surveillance default sits on, the police-surveillance default sits on, and the federal-surveillance default sits on. The chain is the same chain. The chain is the default.

The Family-Surveillance Parallel: Mott Poll, June 15, 2026

The University of Michigan C.S. Mott Children's Hospital National Poll on Children's Health published "Safety or surveillance: Tracking of young adults" on June 15, 2026, the same day the PCWorld piece on the Teams Workplace Check-in feature ran.^[3] The poll is a national sample of parents of 18 to 25 year olds. The two central findings are the 52% tracking rate and the 54% opt-out rate. 52% of parents report tracking their young adult child's location using a cell phone or similar device. 71% of tracking parents say the feature is always on. 96% of tracking parents say their child is aware of the tracking. Only 54% gave their child the option to opt out. 23% say the tracking sometimes makes them more anxious than reassured.^[3]

The structural shape of the family-surveillance default is the structural shape of the workplace-surveillance default. In both cases, the data flows from the watched to the watcher on a default-on basis. In both cases, the watched party is rarely the one who configured the feature. In both cases, awareness is not consent. In both cases, the opt-out rate is the gap between "told the watched party" and "asked the watched party for permission." In the Mott Poll, the gap is 42 percentage points. In the Teams Workplace Check-in posture, the gap is the distance between the IT admin enabling the feature and the employee finding the toggle in Teams settings.

The Mott Poll measurement is the family-privacy case. The Teams Workplace Check-in feature is the employer-privacy case. The two cases share the location-tracking technology. The two cases share the default-on posture. The two cases share the gap between awareness and consent. The two cases share the positive-feedback loop: the watcher reaches for the data, the data either reassures the watcher or does not, the watcher reaches for the data again. The Mott Poll measured the loop on the family side. The Teams feature institutionalizes the loop on the employer side. The same loop. The same shape. The same default. The same posture.

The Mott Poll is the under-noticed data point of the week. The Teams Workplace Check-in feature is the platform story of the week. The two are the same story at two different layers. The layer is the actor. The actor is the family or the employer. The actor is the parent or the IT admin. The actor is the surveillance-operator. The actor is the same shape of actor. The actor is the surveillance-default actor.

The Employer-Surveillance Market: Where the Wi-Fi Signal Already Lives

The Teams Workplace Check-in feature lands the same week as the broader 2026 employer-surveillance market. The market has been growing on the back of three categories of vendor. The first category is the time-tracking category: Hubstaff, Time Doctor, ClickTime, and the rest of the screenshot-cadence and activity-monitoring stack.^[4] The second category is the employee-experience category: ActivTrak, Microsoft Productivity Score (the 2020 to 2021 controversy that has not gone away), and the rest of the manager-dashboard stack.^[5] The third category is the AI-coaching category: the Amazon "rate my manager" tools, the AI productivity-scoring rollouts, the generative-AI summarization of manager one-on-ones. The Teams Workplace Check-in feature is the platform layer, the surveillance vendors are the application layer, and the Wi-Fi probe is the network primitive both layers sit on top of.

The Microsoft Productivity Score controversy of 2020 to 2021 is the closest historical parallel. Microsoft 365 Productivity Score was a feature that surfaced per-employee telemetry to the tenant admin, with the stated purpose of helping IT teams understand aggregate usage patterns. The controversy was that the same telemetry could be drilled down to the per-employee level, and that the per-employee view was being used by some managers to evaluate individual employees. Microsoft added a setting to disable the per-employee view. The setting is the same posture the Workplace Check-in feature is taking: a tenant-admin opt-out, an end-user opt-out, and a default that the tenant admin sets. The Productivity Score controversy is the warning. The Workplace Check-in feature is the same posture on a different feature, with the same defaults, with the same warnings unaddressed.^[6]

The structural read is that the Wi-Fi probe is the network primitive the entire employer-surveillance market has been sitting on. The Hubstaff, ActivTrak, Time Doctor, and Microsoft Productivity Score features all read the same primitive. The new entrant is the platform itself. The platform is the layer the entire office stack runs on. The platform is the layer the entire surveillance stack runs on. The posture of the platform matters more than the posture of any single surveillance vendor, because the posture of the platform is the posture every other layer inherits.

The Microsoft Track Record: Productivity Score, ICE Azure, Voiceprint, Defender

The Teams Workplace Check-in feature is the latest in a 2026 sequence of Microsoft decisions on the surveillance side. The sequence starts with the Microsoft Productivity Score controversy of 2020 to 2021, runs through the Microsoft Defender for Endpoint three-zero-day Bluehammer and Redsun disclosures of 2026, runs through the Microsoft ICE Azure data-tripling story of 2026, and runs through the Microsoft Teams voiceprint BIPA lawsuit out of Illinois. The sequence is the track record. The track record is the context the Workplace Check-in feature lands in.^[7][8]

The Microsoft ICE Azure story is the most direct parallel. Microsoft is the cloud provider for the ICE surveillance infrastructure. The data flowing through the infrastructure tripled in 2026. The tripling is the kind of growth that requires platform-side cooperation. The cooperation is the posture. The posture is the platform cooperating with the federal surveillance apparatus. The Workplace Check-in feature is the platform cooperating with the enterprise surveillance apparatus. The cooperation is the same cooperation. The actor is the federal agency in the ICE case, the IT admin in the Workplace Check-in case. The actor is the surveillance-operator. The actor is the same shape of actor at two different layers.

The Microsoft Teams voiceprint BIPA lawsuit out of Illinois is the prior workforce-surveillance case on Microsoft's track record. The lawsuit is about Teams voiceprint biometric data, not about Wi-Fi. The lawsuit is the proof that Microsoft collects biometric data on its workforce customers, and the lawsuit is the proof that the workforce customers have not always consented. The lawsuit is the warning. The Workplace Check-in feature is the same posture on a different feature. The posture is: a feature that reads a low-level signal from the device, surfaces the signal to the platform, and surfaces the platform's reading of the signal to a viewer the user may not have known was reading. The posture is the Microsoft posture. The posture is the platform posture. The posture is the surveillance posture.

What It Means for You Today

Three groups are affected, and the consequences diverge.

If you are a Microsoft Teams-using employee whose IT admin has enabled Workplace Check-in. The structural posture is opt-out at the device level. The opt-out is in the Teams settings. The opt-out is not in the Wi-Fi settings. The opt-out does not stop the Wi-Fi probe at the OS layer. The opt-out stops the integration of the Wi-Fi data into the Teams office-attendance record. To take the opt-out: open Teams / Settings / Privacy / Workplace Check-in, and decline. The setting may not be in that menu. The setting may be under a different name. The setting may be controlled by the IT admin, in which case the IT-admin setting is the only setting that matters. If you cannot find the setting, ask the IT admin. The ask is the consent conversation. The ask is the structural step the Workplace Check-in posture does not require the IT admin to surface.

If you are a Microsoft 365 tenant admin evaluating Workplace Check-in. The three-part posture is opt-in at the org layer. The default is off. The posture is the one Microsoft has been using since the Productivity Score controversy: a setting at the tenant level, with a per-user toggle underneath, and a default the tenant admin sets. The default is the question. The default is the question every other surveillance default in the market is asking. The default is the question the Mott Poll is asking on the family side. The default is the question the EFF, the unions, and the state-level workforce-privacy legislation are going to ask on the employer side. The default is the question. The default is yours to set.

If you are a state legislator, AG, or member of Congress working on workforce-privacy legislation. The 2026 legislative response to the deepfake crisis, the AI chatbot crisis, the kids-online-safety crisis, and the family-tracking crisis has been significant. The legislative response to the Wi-Fi-based employer attendance tracking crisis is not yet on the public record. The Mott Poll measurement of 52% of parents tracking their young adult children, and the 54% opt-out rate, is the family-privacy data point. The Teams Workplace Check-in feature is the employer-privacy data point. The legislative gap is the gap between the family-privacy data point and the employer-privacy data point. The gap is the gap the legislation is going to have to close.

The Bottom Line

PCWorld reported on June 15, 2026 that Microsoft Teams is rolling out a new "Workplace Check-in" feature in June 2026 that detects an employee's office presence by reading the company Wi-Fi network their phone or laptop joins, and posts the result to a per-employee office-attendance record a manager can view. Microsoft says the feature is disabled by default, the tenant admin decides whether to enable it, and the end user can "always" choose to allow or decline to share.^[1]

The privacy story is the structural posture. The same Wi-Fi probe-request signal a growing fleet of corporate-surveillance vendors already use is now deployed by the platform the entire office stack runs on, with the only advertised opt-out at the IT admin layer rather than at the employee device. The Mott Poll measurement of 52% of parents tracking their young adult children, the 71% always-on rate, and the 54% opt-out rate is the family-privacy case in the same structural posture. The Microsoft Productivity Score controversy of 2020 to 2021 is the prior platform case in the same posture. The Microsoft ICE Azure data tripling of 2026 is the federal-surveillance case in the same posture. The posture is the surveillance-default posture. The posture is the same posture at four different layers.

Watch for five things over the next 30 days. First, the first enterprise IT shop to publish a tenant-level policy on Workplace Check-in. The Microsoft 365 roadmap lists June 2026 as the rollout month. The first IT-shop policy will set the precedent for the rest. Second, the first major employer to enable Workplace Check-in org-wide. The org-wide enablement is the move that tests the posture. The move is the data point the workforce-privacy legislation is going to be built around. Third, the first EFF, union, or workforce-privacy-coalition public statement on the tenant-admin-only opt-out posture. The posture is the question. The statement is the answer. Fourth, the first state-level bill or state AG guidance document specifically addressing Wi-Fi-based employer attendance tracking. The Mott Poll measurement is the family-privacy data point. The Teams Workplace Check-in feature is the employer-privacy data point. The legislative gap is the gap the bill is going to have to close. Fifth, the first peer-reviewed paper on the Wi-Fi probe as a workplace-surveillance primitive. The primitive is the network primitive the entire employer-surveillance market sits on. The primitive is the question the academic literature is going to have to answer.

Sources

1. PCWorld: "Microsoft Teams introduces office attendance tracking via Wi-Fi" (Hans-Christian Dirscherl, June 15, 2026, 7:14 pm PDT, the Workplace Check-in rollout month, the Wi-Fi-based detection method, Microsoft's verbatim "This feature is disabled by default. Tenant administrators decide whether to enable this feature, and end users always have the choice to allow or decline the sharing of this information" statement, the "does not track employees' movements with precise location data" qualifier, the postponement-since-late-2025 detail, the June 2026 roadmap date, and the PC-WELT sister-publication origin)
2. Microsoft Learn: "Wi-Fi Direct" and "WLAN_probe_request" technical references (the Wi-Fi probe-request primitive, the OS-level scan, the SSID-list caching, and the no-user-gesture emission)
3. C.S. Mott Children's Hospital National Poll on Children's Health: "Safety or surveillance: Tracking of young adults" (June 15, 2026, Volume 49, Issue 4, primary source for the 52% tracking rate, the 71% always-on rate, the 96% awareness rate, the 54% opt-out rate, the 23% more-anxious rate, the 48% mutual-tracking rate, and the family-surveillance parallel)
4. Hubstaff: "AI Productivity Scoring" product page (the Hubstaff 2026 AI productivity scoring rollout, the cadence and aggregation model, the manager-dashboard posture)
5. ActivTrak: "Employee Experience" platform page (the ActivTrak 2026 employee experience product, the manager dashboard, the opt-out posture, the application-layer employer-surveillance market context)
6. The Verge: "Microsoft Productivity Score feature is being used to spy on employees" (the 2020-2021 Microsoft 365 Productivity Score controversy, the per-employee drill-down, the opt-out posture, the warning case for the Workplace Check-in feature)
7. State of Surveillance: "Microsoft Defender Three Zero Days: Bluehammer and Redsun" (the 2026 Microsoft Defender for Endpoint three-zero-day disclosure, the Bluehammer and Redsun zero-days, and the undefended posture)
8. State of Surveillance: "Microsoft ICE Azure Data Tripled AI Surveillance" (the 2026 Microsoft ICE Azure data tripling, the AI-surveillance integration, and the Microsoft-as-government-surveillance-infrastructure posture)
9. State of Surveillance: "Microsoft Teams Voiceprint BIPA Lawsuit in Illinois" (the Microsoft Teams voiceprint biometric data case, the BIPA class action, the prior workforce-surveillance case on Microsoft's track record)

Related Coverage

• Mott Poll: Half of Parents Track Their Young Adult's Location. Half Don't Even Ask First. The State of Surveillance June 15, 2026 piece on the C.S. Mott poll, the 52% tracking rate, the 71% always-on rate, the 96% awareness rate, the 54% opt-out rate, and the family-privacy parallel. The Teams Workplace Check-in feature is the employer-privacy case in the same structural posture as the family-surveillance case the Mott Poll measured. The posture is the same posture at two different layers.
• Microsoft ICE Azure Data Tripled, AI Surveillance Integration Follows The State of Surveillance piece on the 2026 Microsoft ICE Azure data tripling, the AI-surveillance integration, and the Microsoft-as-government-surveillance-infrastructure posture. The Workplace Check-in feature is the same platform-cooperation posture on the enterprise side. The posture is the same posture at two different customer segments.
• Microsoft Teams Voiceprint BIPA Lawsuit in Illinois The State of Surveillance piece on the Microsoft Teams voiceprint biometric data case, the BIPA class action, and the prior workforce-surveillance case on Microsoft's track record. The Workplace Check-in feature is the same posture on a different feature, with the same defaults, with the same warnings unaddressed.
• Wi-Fi Router Surveillance: Identification by Beamforming in Karlsruhe The State of Surveillance piece on the Karlsruhe wi-fi-router beamforming identification research, the same Wi-Fi-signal primitive the employer-surveillance market sits on, and the technical layer the Workplace Check-in feature is built on. The primitive is the same primitive.
• California AB 1898: Workplace AI Surveillance Disclosure The State of Surveillance piece on the California AB 1898 workplace AI surveillance disclosure bill, the first state-level workforce-privacy disclosure bill, and the legislative parallel the Teams Workplace Check-in feature is going to have to address. The bill is the bill. The feature is the feature. The legislative gap is the gap.