Teams presence tracking, answered.

Teams presence: the status your team already shows in Teams (Available, Busy, Away, Offline) and the activity behind it, such as In a call or Presenting, sampled on a short, regular interval. Presify keeps that history and turns it into a timeline per person and per team, online-time totals and trends, a 24-hour view of each person’s day, status by status, exportable reports, and flags for presence that looks gamed (reports and flags depend on your plan). Guest accounts are never tracked.

History starts when you connect, and for each person from the moment they’re added to tracking. Teams keeps no presence history of its own, so there is nothing to backfill; from that point Presify keeps the record for your plan’s retention period, from 7 days up to 360 days. You can delete a person’s history, or your whole account’s data, at any time from Settings.

app.presify.io/users/8c2e41d7-5b1a-4f7e-9d3c-2a6b0e19f4c8

Not directly: presence isn’t productivity, and Presify doesn’t see the work itself. The green dot isn’t the whole story either. Someone can stay green all day and barely be around (a mouse jiggler keeps Teams green), and someone who always looks yellow might be doing their best work at 11pm.

What Presify gives you is a directional read on the part you can’t see today: when each person is online in Teams and how much, day after day, plus flags for presence that looks gamed. Use the pattern to ask better questions: who is consistently around in the hours you rely on, whose online time has changed, and who is putting in more time than you knew. What you do with it starts with a conversation.

No. A status only tells you what Teams showed at that moment, not whether the person was working, so one glance at the dot tells you very little. That’s why Presify keeps the history: your read on your team comes from the pattern over days and weeks, not a snapshot.

Not with certainty, because presence data can’t prove how an account stayed green. What Presify does is flag six unusual presence patterns and show how each one is calculated. The first four are the patterns a mouse jiggler or keep-alive script tends to leave; the last two mark unusual hours:

• Unbroken Available: one Available status that runs for hours without a single change.Pro and Scale
• Idle suppression: a long online stretch with no idle time at all, although Teams normally goes idle after a few minutes without keyboard or mouse input.Standard and up
• Robotic regularity: status changes spaced at unusually even intervals.Pro and Scale
• No activity variation: online most of the day with no change in Teams activity (no calls, no presenting).Pro and Scale
• Overnight presence: online time between midnight and 5 a.m.Pro and Scale
• Weekend uniformity: weekends that look statistically like weekdays.Pro and Scale

A flag is a pattern worth a look, not proof. The same late-night hours a keep-alive script fills can be someone genuinely working late, so check the timeline and talk to the person before you draw a conclusion, and never make a decision about someone on a flag alone.

Not every plan runs flags: Basic and the free trial run none, Standard runs one (Idle suppression), and Pro and Scale run all six. See pricing for everything each plan includes.

As patterns worth a look, never as conclusions. Each flag marks presence that differs from typical interactive use and shows exactly what was measured. Detection is probabilistic: a flag says what Presify observed, not why it happened or what anyone intended.

Open the person’s timeline around it, add the context you have, and use it to start a conversation. A flag should never be the sole basis for a decision about someone.

Presence is sampled by polling Microsoft Graph on a short, regular interval, so the timeline reflects each person’s status at each sample rather than every momentary change. It is built for the pattern over days and weeks, not a live feed of where someone is this second.

Yes. Every Presify plan includes a read-only connector for AI assistants that support the Model Context Protocol (MCP), such as Claude, ChatGPT, and Microsoft Copilot (through Copilot Studio). Connect one and ask in plain language: when someone was online last week and for how long, how a person’s or the team’s online time is trending, which presence patterns were flagged, or when the team overlaps across time zones. Flags and coverage answers follow your plan, the same as in the app.

The connector can only read: an assistant can never change settings, add people, or write anything. It sees only what you can already see in Presify, so someone with the Monitor role gets answers about the people assigned to them and nobody else.

You can see and revoke your connections at any time under Settings, then Connections, and connections and revocations are recorded in the workspace audit log (viewable on Pro and up). Answers go to the AI provider you connected, under that provider’s terms. See how to connect an AI assistant.

No. Productivity Score is a separate Microsoft 365 feature, and Presify does not use it. Presify reads each tracked person’s Teams presence through the Microsoft Graph presence API and keeps a per-person history of it, which Teams itself does not keep.

Presify reads presence from Microsoft Graph, so when Microsoft has an outage there is nothing for us to read. You’ll see a clearly marked “No data” gap for that span, never a wrong status. Collection resumes automatically once Microsoft recovers, and you can review your workspace’s Microsoft connection history any time in Settings → Data management. Live Microsoft connectivity is also on our status page.

No. Nothing goes on anyone’s laptop or phone: no agent, no browser extension, no rollout. Presify reads the presence Teams already has through Microsoft Graph, once a Microsoft 365 admin approves read-only access. Because it reads Teams rather than the device, it works on any device people use Teams on.

For one step. A Microsoft 365 admin approves Presify’s read-only access once. After that, owners and admins run the reports, and a team lead with the Monitor role reads their own people’s timelines, all with no technical work. In a small business the owner is often the admin too, so one person can do the whole setup.

There’s no set upper limit. We’ve tested Presify on a Microsoft 365 tenant of about 2,000 users, and we can support tenants many times larger.

You can buy up to 2,000 Scale seats at checkout. For anything bigger, just reach out first: tell us how many people you plan to track and we’ll set it up with you.

It means your Microsoft sign-in worked, but your organization hasn’t added you to Presify yet. Signing in confirms who you are; access to Presify is granted per person by your organization’s Presify owner or an admin, not automatically to everyone in the company.

Ask whoever set Presify up at your organization (the owner) to add you. In Presify they go to Settings, then Roles, pick you from your Microsoft directory, and give you a role (admin or monitor). Once you’ve been added, sign in again and you’re in. Nothing is wrong with your Microsoft account, and there’s nothing for you to install.

Microsoft Graph application permissions are granted at the tenant level. Microsoft provides no way to consent to presence for only a subset of users, so the grant is tenant-wide. A broad grant is not broad access: Presify only ever collects presence for the specific people you enroll, and scope is enforced inside the product, not by the permission itself.

• You choose who is monitored. Presify collects presence only for the users you explicitly enroll (or a group you select). Everyone else in your directory is left out, even though the permission could technically read them.
• Tenant isolation. Every record is scoped to your Microsoft tenant and enforced at the database layer, with cross-tenant access tested in our CI on every change.
• Audit trail. Enrollment and every monitoring change are written to an append-only audit log naming the actor, the action, and the target.
• Least privilege, read-only. The permissions are read-only and limited to presence, the directory fields needed to label and scope users, and each person’s time zone and working hours. None of them can write to your tenant.

Presify is built and hosted in the US: your workspace data is stored and processed on US-based cloud infrastructure, wherever the people you track are located. Every record is scoped to your tenant and encrypted. Retention depends on your plan, and you can delete a user’s presence history, or your whole account’s data, at any time from Settings.

See history kept by plan, and the security page for how data is protected.

The notice should come from you. Presify doesn’t notify anyone itself: Microsoft shows no user-facing prompt when a tenant admin approves Graph access, so we recommend telling your team their Teams presence is tracked before you start tracking them, and Presify includes a ready-to-adapt employee-notice template to help. Providing any employee notice required by law or policy is your responsibility (see the next question and our Terms, Section 6).

Beyond that, nothing changes for them. Presify reads Teams presence from the Microsoft Graph API on the server side, so there is no software on their device, no pop-up, and no extra sign-in, and Teams works exactly as it did before.

Tell your team before you start tracking. A short written notice is the safest default, and Presify includes an employee-notice template you can adapt. If you rely on an existing handbook or computer-use policy instead, check that it covers Teams presence tracking, online-time reporting, automated pattern flags, and the evenings and weekends Presify records.

Some US states (Connecticut, New York, and Delaware among them) require advance written notice before electronic monitoring begins. Other countries have their own rules for the people you track there, and requirements vary by jurisdiction and change over time. Presify records presence at every hour of the day, evenings and weekends included, so your notice should cover those hours too. Some state laws also limit monitoring outside working hours.

We always recommend confirming your obligations with your HR team and your legal counsel. Presify reports Microsoft Teams presence; deciding what notice your organization needs, and giving it, is your responsibility (see our Terms of Service, Section 6).

If you upgrade to a paid plan before day 7, nothing breaks: monitoring expands from just you to your whole team and collection keeps running. If you don’t upgrade, the workspace turns read-only on day 7, collection stops, and your data is kept.

A 30-day grace period follows, with a deletion countdown shown in the app, during which you can still sign in, view, and export. Upgrade any time before deletion to keep your history and lift the monitor-yourself limit.

If you still haven’t upgraded, the workspace data is deleted at the end of the grace period, and you can delete it sooner from Settings. One free trial is available per Microsoft organization every 12 months.

1. First 7 daysTrial runsTracks just you. Upgrade any time to add your team.
2. Day 7Read-onlyCollection stops. Your data is kept.
3. Next 30 daysGrace periodSign in, view and export.
4. End of graceData deletedUnless you upgrade first. You can delete it sooner.

Any time, from Settings → Billing & plan. No email required. Your subscription stays active through the end of the current billing period, after which monitoring stops and data is removed per the retention terms.