
Table of contents
Microsoft 365 Audit Log Activation
Teams chat, OneDrive and SharePoint file activity, and login events reach WorkSights only when Microsoft 365 audit logging is active for your tenant. Outlook email, Outlook Calendar, and Teams calls work whether or not it is on.
This guide shows you how to check whether audit logging is active and how to turn it on if it is not.
What Audit Logs Enable
Once audit logging is active, WorkSights can process SharePoint and OneDrive file interactions, Teams chat message events, login events with timestamp and network metadata, and additional Exchange metadata that improves email coverage. Audit logs contain metadata only. Message bodies, file contents, chat text, and attachments are never received.
Before You Begin
Only a Microsoft 365 admin can enable audit log ingestion. You need an admin account and the Exchange Online PowerShell module installed.
The Microsoft Purview interface may show audit logging as On while ingestion is still inactive. This is common. PowerShell is the authoritative check.
Verifying and Enabling Audit Logging
Step 1: Connect to Exchange Online PowerShell
Connect-ExchangeOnline -UserPrincipalName <[email protected]>
Step 2: Check audit log ingestion status
Get-AdminAuditLogConfig | Format-List UnifiedAuditLogIngestionEnabled
True means ingestion is active and nothing more is needed. False means audit logging is not producing events for WorkSights, even if Purview shows otherwise.
Step 3: Enable audit log ingestion if False
Set-AdminAuditLogConfig -UnifiedAuditLogIngestionEnabled $true
Microsoft may show a warning about a 60-minute delay. In practice, propagation can take several hours.
Step 4: Re-verify after propagation
Run the Step 2 command again. The value must return True before WorkSights can retrieve audit data.
What Happens Next
Once your tenant begins producing audit content, WorkSights starts retrieving it automatically. No further configuration is needed. System-generated noise is filtered so only user-initiated activity appears on timelines.
During Microsoft's activation period, WorkSights may temporarily show empty audit feeds or missing file and chat activity. This resolves on its own once Microsoft finishes activating ingestion.
Troubleshooting
Purview shows audit logging as On but no data appears
Run the PowerShell check in Step 2. If it returns False, enable ingestion with Step 3 and allow propagation time. The Purview interface is not the authoritative indicator.
No SharePoint or OneDrive file activity
Some tenants begin producing file audit output later than others. Allow more propagation time after enabling ingestion.
No Teams chat activity
Teams chat requires audit logs. Only message events appear, and chat content is never transmitted.
No login activity
Login events depend on audit ingestion. Allow more propagation time after enabling.