Microsoft has quietly rolled out a new web presence setting for Teams that can monitor a user’s activity across their entire device—not just within the browser tab where Teams is open—to refine availability statuses. The feature, designed to prevent workers from appearing idle when they are actually active elsewhere, has sparked immediate privacy backlash from users who see it as an intrusive form of workplace surveillance.
The change, first spotted by keen-eyed users on Microsoft’s feedback forums, is part of the company’s ongoing effort to make hybrid work tools more adaptive. But for many, it crosses a red line in the delicate balance between productivity monitoring and employee privacy.
How Teams Presence Detection Currently Works
To understand the controversy, it’s important to grasp how presence status in Microsoft Teams has functioned until now. Teams uses a combination of signals: your calendar entries (Outlook integration), manual status changes, and device activity. In the desktop client, the app can detect mouse movements, keyboard strokes, and other system-level interactions to keep your status as “Available.” When you step away, the system eventually transitions you to “Away” after a period of inactivity—typically five minutes.
The web version of Teams, however, has been more restricted. Browsers limit background tabs’ access to system-level events, meaning the Teams web app could only detect activity that occurred within its own tab. Move to another browser tab to edit a document, and Teams might not register that as active work. After a few minutes, your presence would flip to “Away,” potentially giving colleagues the mistaken impression you were not at your desk. This discrepancy between the desktop and web experiences has been a long-standing complaint among hybrid workers who rely on browser-based tools.
The New Setting: Detecting Activity Outside the Tab
Microsoft’s solution is the new “Device activity” toggle, which expands the signal sources for presence to include actions taken anywhere on the device—even outside the active Teams browser tab. According to Microsoft’s documentation, when enabled, “Teams will use signals from your device to detect your activity and keep your presence status up to date. This includes activity in other apps and browser tabs.”
This likely leverages relatively new browser capabilities, such as the Idle Detection API, which allows a website to request permission to monitor the user’s idle state across the entire operating system. The API, supported in Chromium-based browsers like Edge and Chrome, can detect user interaction with the keyboard, mouse, screen saver activation, or lock screen—essentially determining if the user is physically present and active, regardless of which application has focus.
When a user grants permission—either explicitly or via an admin policy—Teams can register these system-wide events and update the availability indicator accordingly. No more unexpected “Away” statuses while you’re deep in a PowerPoint presentation in another tab.
Privacy Implications: Surveillance Creep or Smart Feature?
For all its technical elegance, the feature has landed badly with many users. On forums and social media, early reactions ranged from unease to outrage. Comments like “Why does Teams need to know what I’m doing in other apps?” and “This is just another way for management to spy on us” capture the sentiment.
The core concern is that “device activity” is a broad term that could be misinterpreted. Users fear that Microsoft—or their employers—could eventually expand the monitoring to include which specific applications are in use, how long they’re used, or even content of those applications. While Microsoft has not indicated any such plans, the slippery slope argument resonates in an era of increasingly sophisticated employee monitoring software.
Privacy advocates point out that the Idle Detection API, while requiring user permission, can be a powerful surveillance tool when combined with enterprise policies. Admins could theoretically force-enable the setting across an organization without individual consent, creating a scenario where every click and keystroke—even outside of work hours or on personal devices—could contribute to monitoring. Microsoft has not clarified the exact data collected, where it’s stored, or how long it’s retained.
Another angle is the blurring of work-life boundaries. Remote workers who use a single device for both personal and professional tasks might inadvertently share personal activity patterns with their employer. For example, if someone takes a break to browse social media or check personal email, that activity could register as “active” in Teams, preventing the status from going to “Away” and potentially leading to unrealistic expectations of constant availability.
Microsoft’s Justification and User Controls
Microsoft frames the feature as a user-driven improvement for accuracy and convenience. “We’re always looking to give people more control over their presence and to make the status more reflective of their actual availability,” a Microsoft spokesperson told windowsnews.ai. “The device activity detection—available only in the web experience—is designed to bridge the gap for those who don’t want to appear offline when they’re working elsewhere on their device.”
The setting can be accessed via Teams Settings > Privacy > Device activity detection. Users can toggle it off to revert to the tab-only behavior. For enterprise customers, IT administrators have the ability to manage this setting through the Teams admin center, allowing them to set a default for the organization or leave it to individual choice.
Nevertheless, the fact that the toggle is on by default in some configurations has drawn criticism. Users on forums report that the feature appeared without explicit notification, and only those who dug into settings discovered it. This lack of transparency feeds the distrust.
Industry Context: Microsoft Is Not Alone
Microsoft is not the first tech giant to flirt with cross-application activity tracking. Zoom, for instance, offers a “Presence” feature that integrates with Outlook and can detect activity across various apps. Google Workspace has long used signals from Gmail and Calendar to set availability in Google Chat. Apple’s Focus Modes span across the ecosystem, though they are user-controlled and not intended for employer monitoring.
What sets Teams apart is its deep integration with Microsoft 365 and the scale of its user base—over 320 million monthly active users, many in corporate environments where management has a vested interest in productivity metrics. The perception that Teams could become a productivity-surveillance hybrid is not entirely unfounded; Microsoft also sells Workplace Analytics and Viva Insights, tools that aggregate signals to measure employee work patterns. While those tools are anonymized and aggregate, the presence feature operates at the individual level, making it more personal.
A Brief History of Presence in Collaboration Tools
Presence indicators are not new. Instant messaging clients like AOL Instant Messenger and MSN Messenger popularized the basic “Online,” “Away,” and “Busy” statuses two decades ago. As unified communications evolved, presence became richer, incorporating calendar free/busy data and location. Microsoft’s own Skype for Business (formerly Lync) introduced intelligent presence based on meeting schedules and device activity in 2015.
Teams, launched in 2017, inherited and expanded that model. But it wasn’t until the pandemic-driven surge in remote work that presence accuracy became a hot-button issue. Managers relying heavily on green dots to gauge availability turned presence into a de facto monitoring tool. The new device activity detection is, in part, a response to users who felt penalized by the system when they were working diligently in other tabs.
The Technical Underpinnings: Idle Detection and Permissions
At a technical level, the feature relies on the Idle Detection API, proposed by Google and available in Chromium-based browsers since version 94. When a site requests access, the browser prompts the user with a permission dialog asking, “Allow [site] to know when you’re actively using this device?” If granted, the site can receive idle state changes—from active to idle, or to locked—allowing it to adjust behavior accordingly.
Teams adds a layer on top: the device activity signal triggers a presence update even when the browser tab is not focused. This requires the browser to run a background service worker, a capability that modern browsers support but is often invisible to the user. The data flow typically remains local: the browser informs Teams of an idle state change, and Teams updates its cloud-based presence service. In theory, no granular activity logs are transmitted, but the opacity of the process leaves room for doubt.
Enterprise Governance and GDPR Concerns
For organizations bound by regulations like GDPR, the feature raises serious questions. Under GDPR, employee monitoring must be transparent, have a lawful basis, and be proportionate. If an admin enables device activity detection organization-wide without clear communication, the data processing could violate the principle of transparency. Employers would need to conduct a Data Protection Impact Assessment (DPIA) to document the risks and mitigations.
Some European Works Councils have already expressed interest in scrutinizing the feature. “Any tool that can infer worker behavior across devices must be justified and consented,” said Klaus Meister, a data protection officer in Berlin. “The default should be off, not on, and the user must have a genuine choice.”
User Reactions and Community Feedback
Even though the news is fresh, community feedback has been swift. On Microsoft’s own feedback portal, a post titled “New device activity detection in Teams web—privacy overreach?” has gathered hundreds of votes and comments within days. Users expressed frustration over the lack of clear communication, with one commenter writing: “I don’t mind if Teams knows I’m active on my PC, but I want to know exactly what data is being sent and how it’s used. Right now, it feels like a black box.”
Some see the feature as a solution in search of a problem. “If managers are micromanaging presence status, the issue isn’t the technology—it’s the workplace culture,” another user noted. This speaks to a broader tension in hybrid work: the tools designed to enable flexibility often end up reinforcing presenteeism.
How to Disable the Feature and Protect Your Privacy
For individual users concerned about privacy, disabling the feature is straightforward:
- Open Teams on the web.
- Click your profile picture > Settings > Privacy.
- Under “Device activity detection,” toggle off “Detect activity on my device to keep my presence status accurate.”
For enterprise admins, the policy can be set via the Teams admin center under Teams settings > Presence. The policy name is DeviceActivityDetection and can be configured to UserChoice, Enabled, or Disabled.
Users should also check their browser’s site permissions. The Idle Detection API requires an explicit permission prompt; revoking it in the browser will block the feature regardless of the Teams setting. In Edge, go to Settings > Cookies and site permissions > Recent activity permissions, and remove the Teams site from allowed idle detection.
Broader Implications for Hybrid Work
The debate over device activity detection is a microcosm of the larger conversation about trust in remote and hybrid work. As companies invest in digital tools to mimic the office environment, the line between enabling collaboration and enabling surveillance becomes dangerously thin. Features that add convenience often come with a hidden cost to autonomy.
Microsoft, for its part, has a fine line to walk. It must serve its enterprise customers who demand better productivity insights while respecting the privacy expectations of the individuals using its software. The outcome of this particular feature rollout may set a precedent for how future AI-driven monitoring tools in Windows and Microsoft 365 are received.
Some industry analysts suggest that the way forward is radical transparency and opt-in design. “If Microsoft had launched this feature as an opt-in enhancement with a clear, plain-language explanation of the data flow, the reaction would be very different,” said Ravi Naik, a digital workplace consultant. “Instead, it feels like a stealth update that puts the burden on users to discover and disable.”
Conclusion: A Feature Outpacing Its Permission Slip
The new device activity detection in Microsoft Teams web is a technically clever solution to a genuine usability annoyance. But its delivery has exposed deeper fissures in the employer-employee relationship when it comes to digital monitoring. For now, users can reclaim control by turning the setting off—but the larger question lingers: as work tools become more ambient and alert to our behavior, who is really in charge?
Microsoft has an opportunity to refine this feature with better transparency and user education. Until then, the toggle will remain a litmus test for how we negotiate the boundaries of presence in an always-connected world.