In 2023, Microsoft began rolling out "New Teams" — a rebuilt version of the Microsoft Teams desktop client with significantly improved performance, based on a new architecture. By 2024, New Teams became the default for most Microsoft 365 users, with Classic Teams officially retired for most plans. If you've noticed different presence behavior after an automatic update, this is why — and the differences matter for how you manage your status.
The Architecture Change That Changed Presence
Classic Teams was built on Electron — the same framework that powers Slack, VS Code, and many other desktop apps. Electron bundles a full Chromium browser alongside Node.js to run web applications as desktop apps. It works, but it's resource-heavy and has its own layer of abstraction between the app and OS APIs.
New Teams is built on Edge WebView2, a lighter Microsoft-developed approach that uses the system's existing Edge browser engine rather than bundling a separate one. The key difference for presence behavior: New Teams has deeper, more direct integration with Windows APIs and the Microsoft 365 ecosystem. It reads OS idle state more accurately, processes calendar events more reliably, and handles the transition between presence states more smoothly.
What Changed in Presence Detection
More Accurate OS Idle Reading
Classic Teams had a known issue where it would sometimes fail to pick up OS idle state changes promptly — meaning it might take 6–8 minutes to flip to Away after your computer went idle, rather than the intended 5 minutes. New Teams is more precise. The flip to Away happens closer to the 5-minute mark consistently. This sounds neutral or even negative, but in practice it means the behavior is more predictable and easier to address: prevent the 5-minute idle trigger reliably, and New Teams stays green reliably.
Improved Cross-Device Presence
New Teams handles multi-device presence significantly better than Classic. When you're active on Teams Mobile while your desktop is idle, New Teams on the desktop correctly shows you as Active based on mobile activity. Classic Teams had inconsistent behavior here — sometimes the mobile activity would propagate to desktop presence status, sometimes it wouldn't.
For remote workers who are on phone calls or away from their desk but still reachable via Teams Mobile, this improvement means the status is more likely to accurately reflect actual availability without manual intervention.
Calendar Integration Accuracy
New Teams' Microsoft 365 calendar integration is tighter. Meeting status changes — switching to "In a meeting" when a calendar event starts, returning to Available when it ends — happen with lower latency and higher reliability than in Classic Teams. The calendar-based status now also correctly handles back-to-back meetings, tentative meetings, and meetings you've declined.
The "Focus" Status and Windows Focus Assist
New Teams introduced deeper integration with Windows Focus Assist (now called "Do Not Disturb" in Windows 11). When Windows DND is active, New Teams can automatically mirror this with a Teams "Focusing" status. Conversely, setting Teams to "Do Not Disturb" can optionally enable Windows Focus Assist — suppressing system-level notifications simultaneously.
This integration is useful for remote workers who use Windows Focus Assist during deep work sessions: one setting propagates to both the OS notification layer and the Teams presence layer automatically.
The Idle Timer: Same Mechanism, More Reliable
The fundamental idle detection mechanism in New Teams is the same as Classic Teams — it reads Windows' GetLastInputInfo() API (or macOS equivalent) and transitions to Away after approximately 5 minutes of no hardware input. What changed is reliability and consistency, not the underlying mechanism.
This means the same solutions that worked for Classic Teams work for New Teams. A browser-based keep-awake tool using Wake Lock API prevents OS idle detection, which prevents New Teams from receiving the idle signal. The more precise idle detection in New Teams actually makes this solution more effective: prevent the 5-minute trigger accurately, and the status genuinely never changes.
Settings That Moved or Changed
Some presence-related settings moved between Classic and New Teams. If you configured settings in Classic Teams and then noticed they weren't carrying over:
- Privacy settings (who can see your presence): now under Settings → Privacy → Contacts. Behavior is the same, location changed.
- Notification settings: substantially reorganized in New Teams under Settings → Notifications & Activity. Per-app and per-channel notification controls are now more granular.
- Status duration: manual status with duration still works the same way — click your profile picture, click your status, set duration. The UI is slightly different but the functionality is identical.
What This Means Practically
If you recently moved to New Teams and noticed different idle behavior — either more precise Away transitions or improved cross-device syncing — the architecture change explains it. The solution remains the same: prevent OS-level idle detection during work hours, and your Teams status will accurately reflect your availability regardless of whether you're on Classic or New Teams.
For most remote workers, the New Teams upgrade is a net positive for presence accuracy. The improvements to cross-device syncing, calendar integration, and Focus Assist integration mean the status system works more correctly with less manual management. Pair it with a keep-awake tool during keyboard-inactive work periods, and the status stays accurate all day.