Managing presence indicators such as Available, Busy, or Away to reflect user availability
Teams presence is designed to follow activity, calendar, and device state. When the computer is locked or idle, Teams automatically moves from Available to Away, and can later show Offline when there is no active connection/activity for a longer period. This behavior is automatic and cannot be fully overridden, but the impact can be reduced.
Key points and options:
- Automatic status behavior
On desktop, Teams automatically changes presence based on computer state:- Available → Away when the computer is locked or goes idle/sleep.
- Extended inactivity or loss of connectivity can lead to Offline.
This is by design and not controlled by cache or app reset.
- Adjust device idle/sleep behavior
Because status changes are tied to lock/idle, extending the time before the device is considered idle can help keep the account from going Offline as quickly:- Increase the time before the device sleeps or turns off the display.
- This aligns with guidance that changing the device’s sleep/idle settings can delay the switch from Available to Away.
- Manually set and time-bound statuses
Teams allows manually setting a status and a duration, but after the duration ends, Teams returns to automatic behavior based on activity, calendar, and device state:- Set Away and then set a Duration (for example, 1 hour).
- After the duration, Teams will again follow normal rules and may show Offline if the device remains locked and inactive.
- Multi-device considerations
If Teams is signed in on multiple devices (for example, desktop and mobile), presence can be influenced by the other device:- If another device (like mobile) remains active, its status can be reflected on desktop.
- To test behavior, sign out of Teams on other devices and observe whether the desktop still moves to Offline in the same way.
- Known macOS-specific presence behavior (if using Mac)
On macOS, there is a known issue where presence subscriptions can expire when the device is locked and not be recreated on resume, causing stale or incorrect presence. Workarounds include:- Manually resetting status after unlocking.
- Restarting the Teams client on macOS.
- Signing out of Teams on other devices if they are affecting presence.
- When to escalate
If presence is consistently incorrect (for example, showing Offline while actively using Teams, or not updating at all), and not just after long idle/lock periods, an administrator can:- Run the Teams Presence diagnostic in the Microsoft 365 admin center to verify presence requirements and follow the remediation links provided.
There is no supported setting to force Teams to remain permanently Away for long periods while the device is locked. The practical options are to extend device idle/sleep timers, use status duration for planned periods, and ensure no presence issues exist by using the admin diagnostic if behavior appears abnormal beyond the expected automatic changes.
References: