TeamScore captures Outlook email activity using Microsoft’s Unified Audit Log, which records high-level mailbox actions generated inside Exchange Online. These signals give organizations visibility into communication behavior without ever exposing message content or headers.

Microsoft does not provide APIs or audit fields that include subjects, recipients, or email bodies, and TeamScore is designed to operate fully within those privacy boundaries.

What TeamScore Tracks

TeamScore processes two types of Exchange audit signals:

Sent Email Events

When a mapped user sends an email through Outlook (desktop, web, or mobile), Exchange Online logs a Send action.

TeamScore receives:

• The user who sent the email
• The timestamp of the send action

This confirms outbound email activity without revealing message content, recipients, or subject lines.

Mailbox Access Events

When a user opens Outlook or loads their mailbox, Exchange generates a mailbox-access event.

TeamScore receives:

• That the mailbox was accessed
• When the access occurred

TeamScore does not receive any information about which emails were viewed, opened, or interacted with.

Both event types help illustrate communication workload while keeping all message content private.

How Email Activity Appears in TeamScore

TeamScore treats email activity as lightweight communication signals:

Sent Email events appear as short, scored contributions to the user’s workday.

Mailbox Access appears as a simple, non-scored email engagement marker, which is helpful for understanding workflow, but never implying content or duration.

Overnight consolidation removes noise from repeated or system-generated access events.

How Microsoft Sends Email Metadata

TeamScore receives audit notifications for:

• Send events
• Mailbox access events

These are delivered through the Microsoft Unified Audit Log, ensuring stable, enterprise-grade reliability.

TeamScore automatically filters out background system noise (e.g., sync pings, automated service checks) so the timeline reflects actual user activity, not machine behavior.

Data Notes and Privacy

These constraints come from Microsoft’s data model, not from limitations in TeamScore:

• No subject lines are ever provided
• No recipients or header metadata are included
• No email bodies or attachments are accessible
• Inbox access logs only confirm that the mailbox was opened, never what the user viewed
• Content privacy is absolute. TeamScore never ingests material from inside any email

Correct user mapping ensures all Outlook events are attributed to the right person.

Next Steps

For a platform-level explanation, see Microsoft 365 Overview.

For configuration details, see Connecting Microsoft 365.

For meeting and scheduling metadata, see Outlook Calendar.