Teams away vs idle vs offline: what each means

Microsoft Teams puts a small colored dot next to every name. Green, yellow, red, gray. Most people read those dots dozens of times a day and assume they know what each one means. The truth is more nuanced. A yellow dot does not tell you someone walked away from their desk, and a gray dot does not tell you someone logged off for the day.

This is a plain-English guide to what each Teams presence state means, how Teams decides which one to show, and where the dots stop being reliable.

The main Teams presence states

Teams computes presence from a few inputs: your activity on the device (keyboard and mouse), your Teams app state, your calendar, and whether you are on a call or in a meeting. It blends those into a single status. Here are the ones you see most.

A few of these are computed automatically. Others you set by hand. That difference is the first thing the dot does not tell you.

Away vs idle: the 5-minute rule

"Away" and "idle" describe the same thing in Teams. After about 5 minutes with no keyboard or mouse activity on the device running Teams, your status flips from green to yellow on its own. Lock your screen and the same thing happens.

So yellow means one specific, narrow fact: Teams has not seen input on that device for a few minutes. It does not mean the person left, stopped working, or is unreachable. Yellow can be any of these:

• Heads-down work in another application (a document, the IDE, a design tool) where Teams sees no input.
• A meeting or call running in a different app, so Teams itself looks idle.
• Reading, thinking, or on a phone call away from the keyboard.
• Actually away from the desk.

All four look identical from the outside. The dot cannot distinguish them.

Busy vs do not disturb

Red usually means a call, a meeting, or a calendar event in progress. Teams pulls this from your calendar and from active calls, so Busy is one of the more trustworthy automatic states. Do not disturb is a close cousin: it shows red too, but it is normally something the person chose, often while presenting or in focus time. Both say "do not expect a fast reply," but only one implies an actual meeting.

Offline vs appears offline

Gray is the most misread state of all. It has two completely different causes that look the same:

• Offline is automatic. Teams is closed, the device is off, or the session ended.
• Appears offline is manual. The person is signed in and may be working, but chose to show gray.

You cannot tell which one you are looking at. Someone showing gray might be deep in work with the dot set deliberately, and someone showing green might have left Teams open on an unattended machine. The dot is a setting as much as a sensor.

Why a single snapshot misleads

Put all of this together and one conclusion follows: a status is a signal, not proof. Any single glance at the dot captures one moment, mixes automatic and manual states, and gives you no idea whether it is typical.

Yellow at 2pm tells you almost nothing. Yellow every afternoon for two weeks, when the same person was green every morning, tells you something worth a conversation. The value is in the pattern over time, not the snapshot. History is what turns a dot into context: it shows the baseline, so you can see when today actually departs from it instead of guessing from one frame.

Teams itself does not keep that history. The dot is live only. If you want to see how status changed across a day, a week, or a month, something has to record each change as it happens. We cover the ways to do that in how to see Teams status history.

How Presify reads these states

Presify reads Teams presence through the Microsoft Graph presence API on a short, regular interval, stores each change, and turns the result into presence timelines, online-time trends, and anomaly flags. It captures the same states described above, available, away, busy, offline, and lays them out over time so the pattern is visible instead of a single dot.

What Presify is careful about:

• It records what the status showed, not why. Presify cannot see whether yellow was focused work or a walk, and it never pretends to. Anomaly flags always show the math behind them so a person makes the call, not the tool.
• Read-only and minimal. Presify reads presence plus the basic directory fields it needs to label and scope users. It never touches message content, chats, calls, files, or calendars, and there is no agent on anyone's device.
• Tenant-isolated and US-based. Your data is scoped to your Microsoft tenant and processed on US infrastructure, with bounded retention you control. Guest accounts are not monitored, and Presify does not enroll users in the EEA, the UK, Switzerland, or Canada.

The dots were never meant to carry this much weight on their own. Seen as a timeline, with the limits stated plainly, they become useful.

If presence history is something you need on an ongoing basis, see how Presify works, compare plans, or start with one Microsoft sign-in.