Microsoft is rolling out a new feature in Teams this December that’s raising important questions about workplace privacy and compliance. If you’re running a Microsoft-centric IT environment, particularly in the UK or EU, you need to understand both the technical implementation and the legal implications before this lands in your tenant.
What’s Changing?
Starting December 2025, Microsoft Teams will include the ability to automatically detect when employees connect to corporate Wi-Fi networks and update their presence location to show “in the office.” On the surface, it sounds like a helpful feature for hybrid work coordination. In practice, it can be seen as employee location monitoring, and that triggers a cascade of data protection obligations.
Microsoft has designed this as an opt-in feature, which is the right starting point.
The Pros and Cons: Who Actually Benefits?
Let’s be honest about who this feature serves and who it might burden.
The Potential Benefits
For the perpetually available (weird quirk alert): Some of us are so work-focused that location transparency is actually helpful. If you’re the type who’s constantly bouncing between the office, client sites, and travel, having your Teams status automatically reflect “at client site” or “in office” can reduce the number of “where are you?” messages. Clients looking for you in Teams get context without you needing to manually update your status seventeen times a day. It’s frictionless communication for people who genuinely don’t care about privacy boundaries—because work is the boundary.
For coordination in hybrid environments: When done right, knowing who’s physically in the office can help with spontaneous collaboration, booking meeting rooms that actually get used, or deciding whether to make the commute for an in-person meeting.
For field-based teams: If you have consultants, technicians, or sales teams who are rarely at headquarters, automatic location context helps managers and colleagues understand availability without constant check-ins.
The Very Real Downsides
Privacy erosion that employees can’t refuse: Even with opt-in, the social pressure to enable tracking in workplaces where “everyone else is doing it” can be immense. Employees who value boundaries may feel forced to comply.
Scope creep is inevitable: Today it’s “let’s coordinate better.” Six months from now, someone in management will ask why attendance data from location tracking can’t inform performance reviews. Features that start optional rarely stay that way.
False precision: Wi-Fi-based detection is crude. You connect to corporate Wi-Fi at a coffee shop down the street? You’re “in the office.” You’re in a three-hour meeting in a Wi-Fi dead zone? You’re “away.” The data isn’t as useful as it seems.
It enables surveillance culture: Once you can track location, the question becomes “why aren’t we tracking more?” The technology normalizes monitoring as a baseline expectation rather than an exceptional measure.
Compliance burden for IT: Every organization operating under GDPR now has to do DPIAs, update policies, manage retention schedules, and field employee questions—even if only 10% of staff actually use the feature.
The Weird Quirk Factor
Here’s my confession: I’d probably use it. I’m the kind of person who’s so embedded in work that I don’t particularly care if people know where I am. In fact, it might make my life easier when clients are hunting for me across time zones and locations. But I’m also aware this is a weird quirk, not a healthy workplace norm.
The problem with features like this is they’re designed for people like me, the ones who’ve blurred work-life boundaries to the point where “off” doesn’t really exist, and then applied to everyone else who might actually want to leave work at work. Just because I’d opt in doesn’t mean it’s good for workplace culture broadly.
If you’re reading this and thinking “yes, I’d use it too,” ask yourself: are you the person who should be setting the standard, or are you the edge case?
How to Enable or Disable the Feature
For IT Administrators
Microsoft Teams location tracking is controlled through the Teams Admin Center and requires tenant-level configuration before it becomes available to users.
To enable location tracking (after completing compliance requirements):
- Sign in to the Microsoft Teams Admin Center (admin.teams.microsoft.com)
- Navigate to Settings > Location-based presence
- Toggle the setting to On at the tenant level
- Configure which corporate Wi-Fi networks should trigger location updates by adding their SSIDs
- Set organizational policies around data retention and usage
To disable or prevent activation:
- In the Teams Admin Center, go to Settings > Location-based presence
- Ensure the toggle remains Off (this is the default state)
- Consider using conditional access policies to block the feature if needed
Even when enabled at the tenant level, individual users must still opt in through their Teams settings.
For End Users
If your IT admin has enabled location tracking at the organizational level, individual employees can control their participation.
To opt in to location tracking:
- Open Microsoft Teams (desktop or mobile app)
- Click your profile picture in the top right
- Go to Settings > Privacy
- Find Location-based presence and toggle it On
- Review which corporate networks will trigger location updates
To opt out or disable:
- Open Microsoft Teams
- Click your profile picture > Settings > Privacy
- Toggle Location-based presence to Off
Your location status will no longer automatically update based on Wi-Fi connection.
What You Should Do Before December
Don’t wait for Microsoft to flip the switch. Here’s your pre-launch checklist:
1. Conduct a formal Data Protection Impact Assessment
Document what data is being collected (Wi-Fi connection events, location status, timestamps), how it’s processed, who has access, and what the privacy risks are. Identify mitigation measures.
2. Complete a legitimate interests assessment
Can you articulate a genuine business need that outweighs employee privacy concerns? “It would be convenient” isn’t sufficient. “We need to coordinate limited meeting room resources in a hybrid environment” might be, but document your reasoning.
3. Update your employee privacy policies
Your workforce needs to know this capability exists before it’s enabled. Update privacy notices to cover what location data is collected, the legal basis for processing, retention periods, and employee rights.
4. Establish clear usage boundaries
Document explicitly that location data will not be used for performance management, attendance tracking, or disciplinary purposes. If you can’t commit to that, you likely don’t have a legitimate interest for processing this data.
5. Create retention and deletion schedules
How long will location data be kept? When will it be automatically purged? Make sure these align with your data minimization principles.
6. Communicate transparently with employees
Before asking anyone to opt in, explain what the feature does, why you’re offering it, how the data will and won’t be used, and confirm that opting out won’t have consequences.
The Bigger Picture
This feature is part of a broader trend toward ambient workplace monitoring. As Microsoft, Slack, and other platforms add more tracking capabilities, often with good intentions around collaboration and productivity, IT leaders need to become more sophisticated about the compliance implications.
The people who design these features and the people who enthusiastically adopt them early are often the ones who need boundaries the least. That’s not a reason to block useful technology, but it is a reason to be thoughtful about rolling it out organization-wide.
Technical controls matter. Individual choice matters. But organizational accountability matters most. You’re the data controller, which means the buck stops with you regardless of how Microsoft designs the feature or whether employees click “I agree.”
If you’re planning to enable Teams location tracking, do the compliance work first. If you’re not planning to enable it, make sure your technical controls prevent accidental activation down the line.
Why This Matters for Compliance
if you’re operating under GDPR (and you are if you have employees in the UK or EU), opt-in alone doesn’t satisfy your responsibilities as a data controller.The European Data Protection Board has been explicit about workplace monitoring: you cannot rely on employee consent when there’s an inherent power imbalance. An employee agreeing to location tracking because they fear career consequences isn’t freely given consent, it’s coerced compliance.
GDPR classifies this type of automated location detection as employee monitoring, which means:
- Data Protection Impact Assessments (DPIAs) are mandatory before you switch this on
- You need a legitimate interests assessment that genuinely balances business needs against employee privacy
- Your existing employee privacy policies almost certainly need updating
- You must establish clear data retention and deletion schedules
- Employees need transparent communication about what’s being tracked, why, and how it will (and won’t) be used
The feature being disabled by default and requiring both admin activation and individual opt-in is good design. But those technical safeguards don’t replace your legal obligations as the organization processing this data.
December will be here soon. Use the time wisely.
Need Help with DPIAs or Legitimate Interests Assessments?
If you’re uncertain about your GDPR obligations around workplace monitoring tools, consult with your Data Protection Officer or legal counsel before enabling new tracking features. The ICO (UK) and your national data protection authority provide guidance specifically on employee monitoring that’s worth reviewing.