Microsoft this week quietly enabled a new Wi-Fi-based workplace check-in feature for Teams and Microsoft Places, the company’s hybrid-work coordination platform. With the update, the desktop app can now automatically update a worker’s office location whenever the device connects to a company-approved wireless network—ending the need for manual status changes each time you walk through the door.

What Actually Changed

The heart of the update is a background service that ties your physical presence in an office building directly to your Microsoft 365 profile. Teams has long allowed users to set their workplace location manually—a small card under your name that says “Office: Building 12.” But if you forgot to switch it after a remote day, your status would lie, and colleagues couldn’t reliably see when you were on-site.

The new feature, rolling out to general availability in early 2025, eliminates that friction. IT administrators can now define a list of approved corporate Wi-Fi networks in the Teams admin center. When the Teams desktop client (Windows and macOS) detects one of those networks, it automatically updates the user’s building location in both Teams and Places. The check-in triggers silently; there’s no prompt, no pop-up, just a small “Location updated” notification if you’ve opted to see it.

The mechanism is simple: Teams asks the operating system for the current Wi-Fi SSID. If it matches an admin-configured trusted network, the client sends a signal to the Microsoft cloud with the associated building label. The update then flows to colleagues’ Teams views, Outlook’s work-hours location hints, and the Places virtual floor plan—showing you as “In the office” without you lifting a finger.

Microsoft designed the feature with a clear privacy boundary. The system uses only the network name, never precise geolocation coordinates. No movement data is stored, and the location tag is strictly the building name assigned by IT. Users remain in control: the check-in can be disabled entirely from Settings > Privacy, and even when on, it only shares the office location during working hours as configured in Outlook.

What It Means for You

For Hybrid Workers

If your company turns this on, your office presence in Teams and Places becomes a true reflection of your actual whereabouts. You won’t need to remember to “check in” manually every morning—and you won’t forget to switch to “remote” when you’re working from home, because the system only updates on trusted office networks. Colleagues glancing at your contact card can trust that “Office: HQ” really means you’re at HQ. This small change reduces the scheduling friction that plagues hybrid teams. It’s one less excuse for missed in-person collaboration when you’re in the building but your profile says you’re remote.

There’s a privacy lens too. Some will welcome the automation; others will see it as overreach. The key nuance is that your employer cannot see your detailed location—just the name of the office you connected to. And because it’s opt-in at the user level (you can flip the toggle off globally), it’s not a surveillance tool by default. If you regularly work from a coffee shop next to the office, that’s safe: the system only reacts to the exact SSIDs your IT team defines, not to open or home networks.

For IT Administrators

This feature closes a long-standing gap in occupancy analytics. With Places’ existing capacity dashboards, IT could see how many desks were booked or how many people set their location to “Building X,” but the data was self-reported and often stale. Wi‑Fi check-in brings near real‑time accuracy without requiring badge swipes or Bluetooth beacons. You get a more honest picture of peak days and underused floors, which feeds into real‑estate decisions and catering orders.

Setup is done through the Teams admin center under Meetings > Meeting settings > Wi‑Fi check‑in. There, you upload a list of SSIDs paired with building names. You can scope the feature to specific users or groups, and you can set it to respect users’ working hours so it doesn’t update outside their schedule. Microsoft recommends using separate SSIDs per building (e.g., “Corp-West-WiFi”, “Corp-East-WiFi”) for the best accuracy, but you can map multiple SSIDs to the same location. A small PowerShell module also lets you export current network data for audit purposes.

One important note: the desktop client does not cache network fingerprints. It checks the current connection each time it initiates an update cycle, which Microsoft says happens sparingly to preserve battery life. So if you roam between buildings during the day, your location will eventually flip, but not instantly.

For Developers and ISVs

If your organization has built line-of-business tools on top of Teams presence or the Microsoft Graph, the location updates tie into the same API. The workplaceLocation property on a user’s presence card now reflects Wi‑Fi check-in data when available, giving you a more reliable signal for scheduling bots, floor-plan integrations, or visitor-management apps. No additional coding is required; the property simply becomes more accurate. For custom Places analytics, the data feeds into the existing Places occupancy model, meaning any dashboards you’ve built on that model automatically benefit.

How We Got Here

Hybrid work flipped the office into an optional destination, and the tools to coordinate it have been playing catch-up. When Microsoft Teams first added a “Set your work location” option in 2021, it was a manual control buried in settings. The idea was to signal availability for in-person collaboration, but real adoption suffered because people forgot to update it. Surveys inside Microsoft and among early Places customers showed that self-reported location was accurate only 60–70% of the time.

Microsoft Places, announced at Ignite 2022, was the strategic answer: a platform to manage hybrid scheduling, desk booking, and team coordination. But its location layer still depended on users manually setting their building. Competitors like Cisco Spaces and Aruba Meridian already used Wi‑Fi telemetry for presence, and third-party add-ons like Robin and Envoy did the same with badge scans. Microsoft needed to close that gap natively.

The engineering path to Wi‑Fi check-in became clearer after Windows 11’s improved location permissions allowed apps to query SSIDs without invasive GPS access. On the Mac side, Apple’s network privacy framework already permitted similar reads. By late 2024, Microsoft began testing the feature internally and among a small ring of early adopters. The public rollout, confirmed in the Microsoft 365 roadmap item 394351, marks the first time that Wi‑Fi-driven presence is directly integrated into a core Microsoft collaboration tool.

What to Do Now

If you’re an employee:
1. Check your Teams version. The feature requires at least the January 2025 update. Go to Settings > About to verify.
2. Review your privacy settings. In Teams, navigate to Settings > Privacy > Location. There’s a new toggle: “Automatically update my work location using Wi‑Fi.” It defaults to off. Turn it on if you want automated check-ins. If it’s grayed out, your admin hasn’t configured it yet.
3. Confirm your working hours. The update respects your Outlook work schedule, so ensure your calendar reflects your actual in-office days to avoid false updates during off-hours.

If you’re an IT admin:
1. Access the Teams admin center. Go to Meetings > Meeting settings > Wi‑Fi check‑in. (This blade may still be rolling out; if you don’t see it, check the message center for your tenant release date.)
2. Define your trusted networks. Add the SSIDs and associate each with the corresponding building name from your Places inventory. Use the bulk upload CSV template if you have many networks.
3. Configure the scope. Decide whether to enable for all users or a pilot group. Consider starting with a floor or department that actively uses Places desk booking.
4. Communicate to your users. Send a short email or Teams message explaining what’s changing, emphasizing that it’s opt-in and doesn’t track personal location.
5. Monitor accuracy. After a week, check the Places occupancy dashboard. If you see anomalies—like people constantly showing in the wrong building—double-check your SSID mappings.

Outlook

Wi‑Fi check‑in is a foundation piece. In upcoming releases, expect Microsoft to layer on more intelligence. The Places team has already hinted at AI-driven suggestions that could, for example, recommend which days to come in based on team patterns or automatically reserve your preferred desk when you arrive. Integration with Teams’ new location-based routing for calling could also follow—imagine your desk phone automatically forwarding to your mobile when you’re not on the office network.

But the bigger story is competition. Google is building similar connective tissue into its Workspace stack, and Zoom’s Workspace Reservation already ties into calendar presence. By embedding Wi‑Fi location directly into the communication client, Microsoft is betting that presence will become a core piece of the hybrid work OS—and that users will trust it enough to leave the toggle on. Whether that trust materializes will depend on how clearly the feature’s privacy boundaries are drawn and how consistently it works across campus networks.