How to know when your remote team is available

To know when your remote team is available, you need their Teams presence over time, not the live dot. You lead a remote or hybrid team, and the same question keeps coming back. Someone always shows green, yet replies take hours. Someone else always looks yellow when you check, and you have quietly filed them as "not around much."

A teammate in another time zone never seems to be online when you need them. The underlying question is simple: when are my people actually online, and how much?

Microsoft Teams seems like it should answer that. Every name has a colored dot. But the dot is built for one moment, not for the question you are really asking. This guide walks through what "available" means in Teams, the honest ways to see it over time, and how to track it openly and fairly.

First, what presence is and is not. Presence shows when someone was online in Teams and what their status said. It does not show what work they did, how hard they worked, or whether they were "productive."

Treat presence as a directional read on when people are online and how much: a starting point for a conversation, never the whole story. Everything below assumes that lens.

Why can't the green dot tell you who's available?

The green dot can't tell you because it shows only what this person's Teams status is right now. That is genuinely useful when you are about to message someone. It falls apart the moment your question involves time.

Four reasons:

• It is live only. The dot reflects this instant. There is no built-in way to ask what someone's status was yesterday at 2pm, or what the team looked like last Tuesday afternoon.
• It scrolls away. Even if you watch it, you are watching one frame. Glance away and the information is gone. Nothing is recorded.
• It is one person at a time. You cannot see the whole team, or a whole week, in a single view. You are checking dots one by one, in the moment, and reconstructing the picture in your head.
• It isn't the whole story. Someone can stay green all day and barely be around (a mouse jiggler or keep-alive app keeps Teams green). Someone who looks yellow every time you check might be doing their best work in the evening. A glance cannot tell the two apart.

So the green dot answers "can I reach Sam now." It does not answer "when is Sam usually online," "how much online time did the team put in this week," or "when do my US and APAC people actually overlap." Those are pattern questions, and a snapshot cannot answer a pattern question.

What does available mean in Teams?

In Teams, available (green) means the app is open and the person has been active recently. Before trusting presence over time, it helps to know what every state means. Teams blends a few inputs (device activity, app state, calendar, calls) into a single status:

Two things trip up leaders:

• Away does not mean gone. Per Microsoft, Teams on a computer shows Away when someone is inactive for a few minutes or the computer is locked. The person could be heads-down in another app, on a phone call, or reading. Yellow is a narrow signal, not "left the building."
• A single dot is a snapshot. One yellow at 2pm tells you almost nothing. Yellow every afternoon for two weeks tells you something worth discussing. The pattern over time is the signal, not the frame.

Presence becomes useful when you can see it as a timeline instead of a dot. If you want the deeper breakdown of each state and where the dots stop being reliable, we cover it in Teams away vs idle vs offline.

The honest options for seeing availability over time

There is no setting in Teams that hands you presence history. To see availability as a pattern, something has to capture each change as it happens and store it. There are three realistic ways to do that. None is wrong; they trade cost against effort and durability.

Option 1: Eyeball it manually

Watch the dots, keep a mental note, maybe jot times in a spreadsheet. For one person over one day, this is fine. As an operating approach it does not hold up.

Watching does not scale past a handful of people, and it produces no record you can look back at. It depends on you being at your desk at the right moments, and you cannot reconstruct last week, because nothing was saved. Good for a quick check, useless for seeing a pattern.

Option 2: A PowerShell script against the Graph presence API

Microsoft Graph exposes a presence endpoint. A modest PowerShell script can read it on a schedule and write results to a file or spreadsheet. This is the cheapest way to start collecting real history, and if you have someone comfortable with scripting it is a legitimate path.

Be clear-eyed about what you take on:

• It runs wherever you run it. If that machine sleeps or reboots, you get gaps in the data and may not notice.
• You own all the upkeep: the storage, the formatting, the charts, retention, and fixing it when Microsoft changes something.
• There is no access control or audit trail unless you build it.
• It is easy to point at the whole directory by accident, which is the over-collection you generally want to avoid.

A script is a real option with a real bill: cheap in dollars, paid in your time and attention. We lay out the trade-off in detail in Presify vs a PowerShell script.

Option 3: A maintained tool that polls and stores it

The third option is a service that reads the Graph presence API on a regular schedule, stores each change, and turns it into timelines and trends. The storage, retention, and access controls are handled for you. You trade a subscription for not owning the upkeep, the gaps, or the plumbing.

When you evaluate one, four questions matter. Is it read-only? Does it need anything installed on devices? What does it retain, and can you delete it? Who can see the data?

What good looks like for a leader

Once presence is captured over time, the view a leader actually needs is not a wall of live dots. It is a few specific things:

• Presence timelines per person. A readable strip of when someone was available, away, busy, or offline across a day, a week, or a month. You see their actual working rhythm instead of guessing.
• Online-time totals and trends. How much each person is online and how that is trending over weeks, per person and rolled up per team. A change shows up as a trend instead of a hunch.
• Flags for presence that looks gamed, each showing how it's calculated. A mouse jiggler or keep-alive script can hold a status green. Automatic flags surface the patterns those tend to leave: hours of unbroken Available, no idle time at all, status changes at robotically even intervals. The calculation is visible so you can judge it. A flag is a pattern worth a look, not proof of anything.
• Overlap across time zones. Where your regions line up and where they do not, so handoffs and meetings land in hours people are actually online.

The point of all of this is to replace the glance with the record, and often the record changes your mind. The person who always looked green can turn out to show hours of unbroken Available. The one you had written off as yellow can show steady online time in the evening. Either way, you are working from the pattern, and the next step is a conversation.

Doing this responsibly

Keeping presence history is reasonable, and it is also the kind of thing that erodes trust fast if you do it quietly. A few principles keep it on the right side:

• Tell your team that presence is kept. Openly, in plain language, ideally in a written policy. Some states also have electronic-monitoring notice laws, such as Connecticut's prior written notice requirement, so check with counsel whether one applies. Tracking quietly costs more trust than it could ever buy you.
• Use it as a starting point. Presence shows when someone was online, not what they did or why. A flag is a prompt to ask, not a conclusion, and it should never be the only basis for a decision about someone.
• Collect the minimum. Presence and basic directory fields, nothing more. No message content, no screen capture, no keystrokes. Keep it only as long as you need it.
• Remember what it is. Presence is not productivity. The instant you frame it as a productivity score, you are measuring the wrong thing and you will get the wrong behavior.

For the legal and notice side in plain English, see is it legal to track employee Teams status. It is general information, not legal advice, and your own counsel should confirm your specifics.

How Presify fits

Presify is a Microsoft Teams presence tracker built for exactly this question. It samples Teams presence (available, away, busy, offline) through the Microsoft Graph presence API on a short, regular interval, stores each change, and keeps the history. From that it builds presence timelines, online-time totals and trends, and six automatic flags for presence that looks gamed, per person and per team.

The result is the leader's view described above: who is online, when, and how much, seen as a pattern instead of a live dot. How much history is kept, which flags are included, and the team overlap view depend on your plan.

What we are deliberate about:

• Five-minute setup, nothing installed. One read-only Microsoft 365 admin sign-in, about five minutes. Nothing is installed on anyone's device, and there are no screenshots and no keystroke logging, ever.
• 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.
• Tenant-isolated and US-based. Your data is scoped to your Microsoft tenant and processed on US infrastructure, with bounded retention you control and per-user and workspace-wide deletion built in.
• Scoped responsibly. Guest accounts are never tracked, and Presify does not enroll users whose Microsoft 365 location is in the EEA, the UK, Switzerland, or Canada. Every flag shows how it's calculated, so you can check the pattern before you draw a conclusion.

If "when are my people actually online?" is the question you keep coming back to, the page for Presify for remote and hybrid teams walks through the use cases. When you are ready, see how Presify works or start with one Microsoft sign-in. Setup takes about five minutes.