Microsoft Teams admin documentation: User presence in Teams
Documents Teams presence states including Available, Busy, In a meeting, In a call, Do not disturb, Away, Offline, Out of Office, automatic status calculation from activity, app state, calendar and devices, manual status duration, notification behavior for Do not disturb, last-seen indicators, and privacy settings for external sharing.
What this source can teach
Use this source to inspect a concrete implementation and the decisions visible in its context.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Presence | Choose presence when the user needs a transient availability, co-attendance, last-seen, or active-viewer signal attached to a person, group, file, channel, task, or conversation. | Presence badges identify the person or group, status label, recency, and source in text, not color alone. | Microsoft Teams documents rich presence states, automatic status from activity, app state, calendar and devices, manual status duration, notification behavior, last seen, and privacy settings. |
Comparisons supported by this source
- Presence vs mentions vs notification center vs activity log
Microsoft Teams documents rich presence states, automatic status from activity, app state, calendar and devices, manual status duration, notification behavior, last seen, and privacy settings.
Evidence Role
This source is treated as product-example evidence. Its value comes from the specific claims and setting described above.
Publisher: Microsoft Learn. Last checked: .