Table of contents
Teams Chats
Teams chat activity gives a lightweight signal of collaboration across the organization. WorkSights receives message metadata from Microsoft’s audit logs, keeping conversation fully private.
Teams chat requires audit logging to be active for your tenant. If chat activity is not appearing, see Microsoft 365 Audit Log Activation.
For connection steps, see Connecting Microsoft 365.
What WorkSights Receives
WorkSights captures message-sent events with the chat name and timestamp, appearing as Sent Teams Chat entries in the Chat category. Message text, images, attachments, reactions, and thread history are never received. Microsoft’s audit log is metadata-only, so chat content is never available to WorkSights.
How Teams Chat Appear
Chat events appear as short entries reflecting the moment of participation. Chat activity contributes to timeline visibility but does not affect scoring.
Because chat comes through Microsoft’s audit pipeline, activity lags hours rather than minutes. There is no backfill path for chat: activity accumulates from the point audit ingestion is active.
Troubleshooting
Chat activity is not appearing at all
Confirm audit logging is active for your tenant. Chat requires the Unified Audit Log; without it, no chat data arrives. See Microsoft 365 Audit Log Activation.
Chat activity is missing for one user
Confirm the user is mapped and the Teams Chat feature is enabled for them.
Activity appears late
This is expected. Chat arrives through the audit pipeline and lags hours, not minutes.