Can you see someone's Teams status history?

No. Teams shows each person's status as it is right now, and Microsoft 365 doesn't keep a history of it that you can look up later. There's no built-in report, and Microsoft's presence API returns current status only. A status history exists only if something has been recording it, and it starts from the day recording starts. You can't get last month's back.

What does Teams actually keep?

Microsoft describes presence as showing "the user's current availability and status to other users", visible "in nearly real time" (Microsoft Learn: User presence in Teams). It's a live indicator. It isn't a log.

You'll see "Away Last Seen time" on some people, but that only tells you when they were last active. It isn't a record of the day.

Is there a report in the Microsoft 365 admin center?

Not for status. Microsoft 365 has a Teams user activity report that counts messages, calls and meetings, and gives each person's last activity date. None of its columns is Teams status or time online. We cover what it does give you in Microsoft Teams presence report: what Microsoft 365 gives you.

People have asked Microsoft this question for years. In a 2022 Microsoft Q&A thread, the accepted answer was: "There isn't any built-in report for this", and a forum moderator added that "getting User Presence Logs from Microsoft Teams is not available in Reports now" (Microsoft Q&A 735321).

Can IT pull it from Microsoft Graph or the audit log?

No. Microsoft Graph is how apps read Microsoft 365 data. Its presence resource lets an app get a person's presence, get it for several people at once, or subscribe to change notifications. Every one of those gives you the status now, or tells you when it changes. None of them returns past status.

In July 2026, a Microsoft representative confirmed this on Tech Community: "Microsoft Teams does not provide historical presence data out of the box through Microsoft Graph Presence APIs", and "Microsoft does not currently offer a built-in API to retrieve historical Teams presence records retrospectively" (Tech Community 4537007).

The audit log doesn't help either. Asked whether presence changes are auditable, a Microsoft MVP answered: "No, there is no audit log record for presence changes" (Microsoft Q&A 2260920). That's a community answer, not an official Microsoft statement, but it matches the Graph documentation.

So how do businesses get a status history?

Something has to record it. Microsoft's own suggestion in the Tech Community thread above is to poll presence on a schedule, or subscribe to change notifications, and store the results yourself.

In practice, a small business has three options:

Build it. Your IT provider writes a script or Power Automate flow that reads presence through Graph and saves it. It needs an app registration with admin consent, somewhere to store the data, and someone to maintain it.
Use an app that records it. A number of apps read Teams presence through Graph and keep the history for you. Clockless is one of them: it checks each person's status about every 5 minutes and turns it into weekly to yearly reports.
Don't record it. For many teams, the live dot in Teams is enough. If you're not going to use a history, don't collect one.

Whichever you choose, the history only starts on the day recording starts.

What does a status history tell you, and what doesn't it?

A status history tells you when someone was signed in to Teams and what Teams showed: Available, Busy, In a meeting, Away, Offline and so on. Over a week, that gives you a fair picture of when someone usually starts and finishes, and how their time was split across statuses.

It doesn't tell you what work was done. Teams sets status from computer activity, the state of the Teams app and the Outlook calendar (Microsoft Learn). Someone reading a long contract can show as Away. Someone on a phone call outside Teams can show as Available. Why that happens is covered in Why does Teams show me as Away when I'm working?

Honest limits

Presence isn't work. A status history shows when someone was active in Teams, not what they did or how well. Use it as an availability record, never as a timesheet or pay record.
No back-filling. Nothing (including Clockless) can recover status from before recording started. Microsoft doesn't keep it.
Tell staff first. Recording Teams status over time is a form of monitoring, so tell staff in writing first. Some states have workplace surveillance laws with notice rules; check what applies to you before you start. Clockless won't start recording until 14 days after you record the date you gave staff written notice. Our plain-English guide to the NSW staff notice is coming. This page isn't legal advice.
Phones and multiple devices blur the picture. Teams uses whichever device someone used most recently, and a phone with Teams in the background shows Away (Microsoft Learn).

How does Clockless handle this?

Clockless records each person's Teams status about every 5 minutes, read-only, with nothing installed on anyone's computer. It doesn't read messages, emails or files. It won't start recording until 14 days after you record the date you gave staff written notice. Detailed records are kept for 90 days and daily totals for about two years, all in Microsoft Azure, Australia East.

Each week you get a report of active hours, start and finish times, and how time was split across Teams statuses. Staff in other Australian states get their own state's public holidays, and their start and finish times are read on their own state's clock. Part-timers can have their own working days, hours and weekly target. We call it an availability record, because that's what it is.

Related guides

If you'd like to see what a recorded week looks like, open the sample report (made-up people and numbers). If it would help your business, book your free month.

Can you see someone's Microsoft Teams status history?