Does My Employer Know When I Am Idle or Away on Teams?

Anyone in your organization can see the yellow dot the moment it appears. That is the whole of what Teams gives them. There is no report that says when you went Away, how long you stayed there, or how many times it happened this week, and Microsoft's own staff have confirmed that the presence API does not expose past presence history. If your employer has a timeline of your status, somebody built one, and that is a different and more deliberate thing than Teams.

That answer needs four qualifications, and this page gives all of them with the documentation behind each: what actually triggers Away and why the five minute figure is contested, what the admin reports and audit log contain, the one route by which a status history can be assembled, and how separate monitoring agents on a company laptop measure idle time in a way Teams never does.

What sets you to Away, and the five minute question

Microsoft's presence documentation for admins gives the rule in one sentence: "On a computer, a user's presence becomes Away automatically if they're inactive for a few minutes or if the computer is locked; and it becomes Offline when the computer enters sleep mode." On a phone, "a user's presence becomes Away whenever the Teams app is in the background, and then becomes Offline after 24 hours of inactivity." When you have Teams open on more than one device, "the device where they were active most recently determines their presence."

The five minute figure that every forum repeats comes from a different Microsoft page. The troubleshooting article, last updated in 2024, says "your presence status changes to Away if your desktop is inactive for more than five minutes," and defines inactive as locked, idle, asleep, or using the mobile app instead. The admin page, updated in July 2026, retreated to "a few minutes." A third Microsoft page, the Graph presence documentation, describes a session that times out after five minutes to an inactive state and after another five to Away, though that is written for presence set by applications rather than by the desktop client. Users on Reddit and X reported two minute flips in spring 2026, and Windows Central covered the complaints without a response from Microsoft.

The honest summary is that it is roughly five minutes of no keyboard or mouse input, Microsoft no longer commits to a number, and there is no setting anywhere that lets you or your IT department change it.

One detail that matters for the anxious: being in a call or meeting sets your status to In a call or In a meeting regardless of input. Reading a document for ten minutes without touching the keyboard sets Away. The dot measures input, not work.

Who sees the dot

Everyone. "By default, anyone in any organization using Teams can see (in nearly real time) if other users are available online," the admin page says, and "your presence status is visible to all users globally." The only admin control is a privacy mode that stops people outside your organization seeing it. Inside, there is no setting to hide presence from a manager, and no setting to show it to a manager that is not already on.

What everyone sees is the current state. The "Away Last Seen" indicator exists as a state in Microsoft's table, but the documentation only describes it as always on where the organization also runs Skype for Business, and it shows a time of day, not a log.

What the admin reports and audit log actually contain

The fear is a spreadsheet of your idle minutes. The reports do not contain one, and the column lists are public.

The Teams user activity report in the Microsoft 365 admin center, per its reference page, has these columns: user name, tenant name, is external, channel messages, posts, replies, urgent messages, chat messages, total meetings, 1:1 calls, last activity date, meetings participated and organized by type, is licensed, other activity, and audio, video and screen share duration. "Other activity" is a yes or no flag, and Microsoft's examples of what sets it include "when a user changes the Teams status or the Teams status message." So changing your status marks you active that day. It records nothing about which status or when.

The Teams admin center version, per the reporting reference, measures the same things: messages, calls, meetings, media time, last activity date. It is available to Teams administrators; a global reader gets only tenant level totals. Names in all these reports are concealed by default and have been since 1 September 2021, unless a global admin turns the concealment off.

The Purview audit log, which records around 110 kinds of Teams event, is where a presence record would live if one existed. The activity list includes messages sent, edited and deleted, meetings joined, members added, and "User signed in to Teams." It has no event for presence, status, Away or idle.

The one way a status history can exist

Presence can be read programmatically. The Microsoft Graph presence API returns a user's current availability and activity to an application that has been granted the Presence.Read.All permission, and change notifications can push each change to an app for up to an hour per subscription, renewable, for up to 650 users at a time. Neither returns history. A Microsoft employee answering a developer's question in July 2026 said it directly: Microsoft "does not currently offer a built-in API to retrieve historical Teams presence records retrospectively," and the recommended approach is to subscribe or poll and "store the status changes in your own database."

So a status log is possible. It requires an application registered in the tenant with admin consent, which is visible to whoever administers it, and either an in-house script or a product built for the purpose. If you are told your status history was reviewed, that is the mechanism, and it is a deliberate monitoring decision rather than a Teams feature. In New York, Connecticut and Delaware, it is the kind of decision that belongs in the written monitoring notice, which the law section below covers.

Viva Insights and workplace check-in

Two Microsoft features get blamed for status tracking and do not do it.

Viva Insights personal insights are, in Microsoft's words, "for your eyes only"; "neither your manager nor the system administration can see your insights." They are built from email, calendar, chat and call metadata, not presence. Manager and organization views are aggregated, and Microsoft's manager settings require a minimum group of five people before anything is shown. There is no presence or idle metric in any of it.

Workplace check-in, the feature that sets your work location from the office Wi-Fi, is "always off by default," needs admin setup and user consent, and Microsoft's documentation states that it "is not a tracking tool and can't be used to monitor employee attendance," and that it "doesn't provide admins with monitoring or reporting views, nor with historical location data." It also does not touch phones.

Monitoring agents are a different thing

If your laptop belongs to the company, the question is not really about Teams. Dedicated monitoring software measures idle time from keyboard and mouse input at a threshold the administrator sets, keeps a timeline, and produces reports. That is the capability people imagine Teams has.

The vendor documentation is specific. ActivTrak starts collecting passive time "after 2 minutes of the employee not actively using or providing input into their computer." Hubstaff's inactivity warning appears after five minutes by default and lets the user keep, reassign or discard the time. Insightful defaults to two minutes and shows idle blocks on the timesheet. Our reviews of employee monitoring software and productivity monitoring software cover what each captures beyond idle time. The guide to detecting monitoring software covers how to tell whether one is installed.

What you can and cannot change

Microsoft's rule for manual status is restrictive in one direction: "users can select any status that is less available than the automatically calculated status." You can make yourself look Busy when Teams thinks you are Available. You cannot make yourself look Available when Teams has decided you are Away, and Microsoft's support page says a more available manual status "will not override a less available status (like Away) even if its duration is set."

Manual statuses expire on their own: seven days for most, one day for Busy and Do not disturb, indefinitely for Appear offline, unless you set a duration. Teams on the web has one setting that helps, an opt-in toggle to keep your status while you are active in other browser tabs, which Microsoft describes as detecting only "whether the user is active or idle" and not "specific actions or content." The desktop app has nothing equivalent.

Mouse jigglers keep the dot green because Teams only sees input. They are also detectable by the monitoring agents above and by endpoint security, and people have been dismissed for using them. Our page on mouse jigglers covers that separately.

Slack, briefly

Slack's availability page says you are active when Slack is open on desktop or mobile and "set to away after ten minutes of desktop inactivity or if you navigate away or close the app on your mobile device." There is no setting for the threshold. The analytics dashboard, visible to owners and admins by default, shows days active and last active, both defined by reading or sending a message, plus message and reaction counts. No active or away duration, no history.

Does this count as monitoring in law?

No statute mentions presence, and we found no case or regulator guidance on it, so what follows is our reading rather than settled law.

Three states require written notice of electronic monitoring: New York under Civil Rights Law 52-c, Connecticut under General Statutes 31-48d, and Delaware under 19 Del. C. 705. Connecticut's definition is the widest, covering "the collection of information on an employer's premises concerning employees' activities or communications by any means other than direct observation." A manager glancing at a live dot is hard to describe as collecting information. A script that polls the presence API and stores the results, or an agent that logs idle minutes on a company laptop, is exactly that, and in those three states it belongs in the notice employees sign. Our guide to employee monitoring laws by state sets out what each notice must say.

The practical document is the monitoring notice or acceptable use policy you were given. If it lists activity or idle tracking, assume an agent exists. If it lists only email and internet use, the dot is probably all there is.

Key takeaways

• Teams sets Away after roughly five minutes without keyboard or mouse input, immediately on lock, and Offline on sleep. Microsoft no longer commits to a number and there is no setting to change it.
• Everyone in the organization sees your current status. Nobody sees a history, because Teams does not keep one.
• The admin reports contain message counts, meeting durations and a last activity date. The audit log has no presence event.
• A status history can only exist if the organization built or bought an application that polls the Graph presence API and stores the results, which needs admin consent in the tenant.
• Viva Insights is private to you and shows managers only aggregates of five or more people. Workplace check-in keeps no history and provides no reports.
• Monitoring agents on a company laptop are the real idle trackers: ActivTrak and Insightful default to two minutes, Hubstaff to five, with timelines and reports.
• You can set a status that is less available than Teams calculates, never more. Busy does not override Away.
• In New York, Connecticut and Delaware, systematic collection of presence or idle data belongs in the written monitoring notice.