Why Microsoft Teams Shows You as Away (and How Status Really Works)
Microsoft Teams does not watch you work. It watches your operating system's idle timer. Almost every complaint about the status dot makes sense once you know that one detail.
How Teams decides your status
Teams presence comes from three inputs, in roughly this order of priority:
- Manually set status. If you pick "Available", "Busy", "Do not disturb" or "Appear away" yourself, that wins - though not forever, see below.
- Calendar. A meeting in your Outlook calendar sets you to "In a meeting". An out-of-office entry sets that.
- Activity. With nothing else overriding it, Teams reads the OS idle timer. Keyboard or mouse input in the last few minutes means "Available". No input means "Away".
That third rule is the source of the confusion. Teams is not measuring whether you are working, reading, thinking, or on a phone call. It is measuring whether a key was pressed or a mouse moved.
The timings
The exact thresholds have shifted between versions, but the behaviour is consistently:
| Situation | Result |
|---|---|
| Input in the last few minutes | Available (green) |
| Roughly 5 minutes without input | Away (yellow clock) |
| Machine locked or screen saver active | Away, immediately |
| Machine asleep or Teams closed | Offline after a short delay |
| Manual status set | Holds, then resets to automatic after a period |
| Calendar meeting in progress | In a meeting |
Note the third row. Locking your machine sets you to Away immediately, without waiting for any timer. If your organisation enforces a short auto-lock, your status will flip to Away every time you read something for more than a few minutes.
The mobile app complication
If Teams is installed on your phone as well, presence is computed across both. The desktop client going idle does not necessarily set you to Away if the mobile client reports activity, and vice versa. This is why people sometimes appear Available at times they know their laptop was asleep - the phone is answering for them.
It also explains a common annoyance: notifications going to your phone instead of your desktop, because Teams concluded the desktop was idle and routed accordingly.
Setting your status manually
Click your profile picture at the top right of Teams and pick a status. Two things to know:
- It expires. Manual status reverts to automatic after a period. You can control this with "Duration" in the same menu - set a status and specify how long it should hold, including "Today".
- "Do not disturb" is stronger than it looks. It suppresses notifications, but people can still mark a message as urgent to break through.
You can also add a status message under the same menu, with an option to show it to anyone who messages you. In practice, a status message saying "Deep work until 15:00, will reply after" prevents far more misunderstanding than any status colour does.
Why the green dot is a poor measure of work
This is worth stating plainly, because it is the root of the problem. Presence indicators were designed to answer one question: "is it a good moment to message this person?" They were never designed as a productivity measure, and they are bad at it in both directions.
A green dot can mean someone is deep in focused work, or that they left a video playing. A yellow clock can mean someone stepped out, or that they are reading a fifty-page specification with total concentration. Anyone drawing performance conclusions from the colour is measuring keyboard activity and calling it something else.
If you manage people, the useful signal is the work: shipped changes, resolved tickets, documents delivered. If you are managed by someone who watches status colours, that is a conversation about expectations rather than a technical problem - though it is a real and common one.
Legitimate reasons your status matters
There are situations where an accurate Available status genuinely matters and idleness misrepresents you:
- On-call and support rotas, where colleagues route work based on who appears reachable.
- Presenting or screen sharing, where you are talking rather than typing for an hour.
- Reviewing long documents during a window when you are expecting to be contacted.
- Waiting on a long job - a build, a render, a data load - while remaining at your desk.
In all of these, the honest position is that you are present and available, and the idle timer is giving a false negative. Keeping the machine active - by any of the methods in this guide, including a browser-based jiggler - makes the indicator match reality rather than mask it.
Worth being clear: using a tool to appear active while you are not working is a different thing, and it is a matter between you and your employer. We are not going to pretend that distinction does not exist. Check your organisation's policy if you are unsure.
Things that do not work
- Keeping Teams in the foreground. The idle timer is system-wide, not per-application. Teams being visible changes nothing.
- Playing a video in Teams. Media playback may prevent display sleep, but it does not generate input events, so the idle timer keeps counting.
- Setting "Available" and walking away for hours. It reverts to automatic.
- Disabling the status feature. There is no such setting - presence is core to the product.
Related: Slack works differently
If you use both, do not assume the rules carry over. Slack has a separate automatic presence system with a shorter, simpler set of rules and a manual away toggle that behaves quite differently from the Teams equivalent. We cover it in how Slack presence works.