Microsoft is preparing a change to Microsoft Teams that will automatically set an employee’s “work location” when they connect to an organization’s office Wi‑Fi or a configured desk peripheral. The capability, built on Microsoft Places, is designed to reduce manual check‑ins and make it easier to know who is in the office and where collaboration can happen. Microsoft’s documentation confirms the feature, the signals it relies on, and the administrative controls needed to enable it. The company says users are opted out by default and must consent in the Teams desktop app on Windows or macOS before any automatic updates occur. Administrators cannot provide consent on a user’s behalf.
According to Microsoft’s Message Center update associated with Microsoft 365 Roadmap ID 488800, general availability is scheduled to begin in December 2025. Microsoft’s public guidance also notes that automatic updates occur only during defined working hours and that the location status is cleared at the end of the workday. In hybrid environments, Places features require an Exchange Online mailbox to function fully. These safeguards and prerequisites aim to balance utility with privacy and compliance expectations. See Microsoft’s configuration guidance and user controls on Learn for the latest official details.
How the work location detection actually works
The feature does not use camera data, video backgrounds, or GPS. Instead, it relies on two enterprise‑managed signals: connection to a mapped office Wi‑Fi network and connection to a registered desk peripheral such as a monitor or dock. IT administrators create a directory of buildings and floors in Microsoft Places, then map office Wi‑Fi identifiers (SSID and BSSID lists) and peripherals to those locations. When a consenting user signs into Teams on a supported desktop client and connects to an in‑scope network or peripheral, Teams automatically updates their work location to “In the office” or to a specific building. If building‑level sharing is not consented to by the user, the status remains general (“In the office”) rather than precise to a building. Microsoft’s Learn article details the PowerShell policy required (New-CsTeamsWorkLocationDetectionPolicy) and the Wi‑Fi mapping steps (including BSSID-to-building CSV uploads) administrators must complete.
Microsoft states that updates only occur during the user’s set working hours; connections after hours do not change the status. As of Microsoft’s March 2025 public sector roadmap note, the capability targets Teams desktop on Windows (version 24H2 or later) and macOS, with virtual desktop infrastructure clients not supported at that time. This architecture and scope make the feature an enterprise facility signal rather than a continuous, device‑level location tracker.
Privacy, consent, and controls
Microsoft emphasizes a layered permission model. First, users must enable operating system location sharing where relevant and then consent in Teams to automatic work location detection. Second, tenant administrators must explicitly enable the detection policy and configure Places with the organization’s buildings and Wi‑Fi details. Microsoft states plainly that “by default, users are opted out of work location detection,” and that admins cannot consent on users’ behalf. The design also limits visibility to colleagues inside the tenant, surfacing the status on profile cards and chat rosters to inform scheduling, wayfinding, and space planning. Official documentation underscores that the feature is about workplace presence—building or office—rather than real‑time tracking.
Industry context and competitive landscape
Hybrid work tools increasingly expose “working location” to streamline coordination. Google introduced working location in Google Calendar in 2021 and later added support for specifying an office building and different locations within a day. Those features, however, generally rely on users to declare where they are working. Microsoft’s approach goes further for managed environments by automating updates based on enterprise signals like Wi‑Fi and peripherals configured in Places, reducing the gap between actual and reported presence. Microsoft outlines the vision for “workplace presence” across Teams and Places in an official blog focused on modernizing flexible work, including a roadmap for Wi‑Fi‑based updates and “nearby” collaboration experiences.
The update also lands as Microsoft reshapes Teams’ positioning amid regulatory scrutiny. In April 2024, Microsoft began selling Teams separately from Office globally following a European Union antitrust investigation into bundling practices, a shift intended to give customers more choice and address competitive concerns. Reuters reported the unbundling and its regulatory backdrop, while subsequent coverage has detailed how the company’s commitments continue to shape Teams and Microsoft 365 offers. These moves contextualize why Microsoft is investing in workplace coordination features that demonstrate product value independent of bundling. For broader background, see reporting from Reuters Technology.
Business impact for hybrid workplaces
For large organizations, a reliable “who’s in which building today” signal can improve meeting planning, desk booking, and facilities management. Automated updates can reduce “are you in the office?” messages, make room suggestions more accurate, and support ad‑hoc collaboration when colleagues are co‑located. Because the status is time‑bounded to working hours and cleared daily, it also minimizes data accumulation. Equally important, the opt‑in requirement and app‑level consent give employees a measure of control that aligns with common privacy regimes and workplace policies. CIOs should review local notice and consent obligations before enabling automatic detection and ensure change management communications are explicit about what is—and is not—being shared.
What IT needs to do to enable it
Organizations planning to use the feature should: set up buildings and floors in Microsoft Places; map SSIDs and BSSIDs to those buildings; register desk peripherals where applicable; enable the Teams work location detection policy; and test on supported Windows and macOS clients. Microsoft notes that without the BSSID mapping, users will see a general “In the office” status when connected to corporate Wi‑Fi; building‑level precision requires the BSSID‑to‑building association. In hybrid Exchange deployments, Places features are limited to users with an Exchange Online mailbox. Microsoft provides step‑by‑step configuration guidance on Learn, including prerequisites, policy settings, and Wi‑Fi mapping commands.
What happens next
Microsoft’s Message Center indicates general availability begins in December 2025, with rollouts governed by tenant configuration and user consent. Enterprises that want the benefit of accurate workplace presence should prepare their Places directory, review privacy notices, and train users on consent and visibility. For official setup details, see Microsoft’s documentation on configuring automatic detection of work location in Teams. For more reporting on the technologies reshaping work—AI assistants, collaboration suites, and digital policy—visit Globally Pulse Technology.
