Table of contents
Teams Calls
Teams calls are one of the clearest signals of active collaboration in WorkSights. Call metadata is ingested directly from Microsoft's Unified Audit Log, giving teams precise visibility into when calls took place and how long they lasted without accessing any meeting content.
For connection steps, see Connecting Microsoft 365.
What WorkSights Receives
WorkSights processes Teams call metadata once a call ends. This includes call start time, end time, duration, call identifier, partial attendee metadata when Microsoft provides it, and IP-based location tied to the join event. Audio, video, transcripts, chat logs, screen share content, and meeting notes are never received.
How Teams Calls Appear
Teams calls appear as timeline entries with actual start and end timestamps and duration calculated automatically. WorkSights renders calls using the meeting-internal or meeting-external color depending on available attendee metadata. If the same call generates multiple audit records due to a user joining, leaving, and rejoining, WorkSights consolidates them into a single call block during nightly processing.
If a Teams meeting was also on the calendar, both entries coexist intentionally. The calendar event reflects scheduled time. The Teams call entry reflects what actually happened.
How WorkSights Classifies Teams Calls
WorkSights applies the same classification logic used across all integrations.
Internal call: All detected attendees share your Microsoft 365 domain.
External call: At least one detected attendee is outside your organization.
Because Microsoft's audit stream does not always supply a full attendee list, WorkSights may classify some calls as internal with incomplete metadata. This ensures consistency without making assumptions about who participated.
Data Notes
Some attendee lists may be incomplete because Microsoft does not expose full participant metadata for every call type. Multi-join scenarios such as connecting from both mobile and desktop are automatically condensed into a single call entry. If Microsoft delivers delayed audit entries, WorkSights adjusts call duration retroactively during nightly processing.
Troubleshooting
If Teams call activity is not appearing as expected:
- Confirm the Microsoft 365 tenant is connected and the affected user is mapped in WorkSights.
- Teams call activity is delivered through the Unified Audit Log. Confirm audit logging is active. See Microsoft 365 Audit Log Activation.
- Call entries appear after a call ends, not during. Calls in progress will not appear until they are completed and processed.
- Attendee lists may be incomplete or partially anonymized due to Microsoft API limits. This is expected behavior.
- For persistent issues, contact support via the in-app chat.