Control 1.7: Comprehensive Audit Logging - Troubleshooting
This playbook provides troubleshooting guidance for Control 1.7.
Common Issues
Issue: No Audit Events Appearing in Search
Symptoms: Audit search returns empty results despite known activity
Solutions:
- Verify unified audit logging is enabled (use
Get-AdminAuditLogConfig— see diagnostic script below) - Confirm you are searching UTC time range
- Check date range and ingestion latency (30 min to 24 hours)
- Verify you have appropriate permissions (Purview Compliance Admin)
- Try a broad search (no filters) to confirm any audit data exists
- Validate via PowerShell using
Search-UnifiedAuditLog
Diagnostic Script:
# Connect to Exchange Online (not IPPSSession) for config cmdlets
Connect-ExchangeOnline -UserPrincipalName admin@contoso.com
# Check if unified audit logging is enabled
Get-AdminAuditLogConfig | Select-Object UnifiedAuditLogIngestionEnabled
# Expected: True
# Check if mailbox auditing is enabled
Get-OrganizationConfig | Select-Object AuditDisabled
# Expected: False
# If audit logging is disabled, enable it:
# Set-AdminAuditLogConfig -UnifiedAuditLogIngestionEnabled $true
Disconnect-ExchangeOnline -Confirm:$false
Issue: Copilot Events Not Being Logged
Symptoms: Other audit events appear but no CopilotInteraction records
Solutions:
- Verify users have Microsoft 365 Copilot licenses assigned
- Confirm Copilot is actually being used (not just licensed)
- Search broadly first, then narrow to specific activities
- Wait longer - Copilot events may have additional latency
- Verify the activity is part of audited workloads for your tenant
Diagnostic Script:
# Connect to Security & Compliance for audit search
Connect-IPPSSession -UserPrincipalName admin@contoso.com
# Broad search to confirm any audit data exists
$allEvents = Search-UnifiedAuditLog -StartDate (Get-Date).AddDays(-7) -EndDate (Get-Date) -ResultSize 10
if ($null -eq $allEvents) {
Write-Warning "No audit events found at all - check if audit logging is enabled"
} else {
Write-Host "Audit logging is working. Checking for Copilot events..."
$copilotEvents = Search-UnifiedAuditLog -StartDate (Get-Date).AddDays(-7) -EndDate (Get-Date) `
-RecordType CopilotInteraction -ResultSize 10
if ($null -eq $copilotEvents) {
Write-Warning "No CopilotInteraction events - verify users have Copilot licenses and are actively using Copilot"
} else {
Write-Host "Found $(@($copilotEvents).Count) Copilot events"
}
}
Disconnect-ExchangeOnline -Confirm:$false
Issue: Expected Events Missing (Partial Results)
Symptoms: Some audit events appear but specific activities are missing
Solutions:
- Remove restrictive filters first and confirm time range returns results
- Confirm date/time range is in UTC
- Broaden search window to account for ingestion latency
- Validate the same query via PowerShell
- Check operation names match what your tenant emits
Issue: Audit Log Export Fails or Incomplete
Symptoms: Export times out or contains fewer records than expected
Solutions:
- Reduce date range to smaller chunks
- Add filters to reduce result set size
- Use PowerShell instead of portal for large exports
- Check for rate limiting (wait and retry)
- Verify network connectivity and session timeout
Issue: Extended Retention Not Working
Symptoms: Old audit events are missing despite retention policy
Solutions:
- Verify retention policy is properly configured and enabled
- Check policy priority if multiple policies exist
- Confirm users are assigned E5/E5 Compliance licenses
- Review policy scope (ensure it covers needed record types)
- Contact Microsoft Support for retention investigation
Issue: SIEM Integration Missing Events
Symptoms: Some audit events not appearing in Sentinel/SIEM
Solutions:
- Verify data connector is properly configured
- Check for ingestion delays (5-15 minutes)
- Review connector health in Sentinel
- Verify record types are included in connector config
- Validate end-to-end by correlating known audit records
Issue: Dataverse Environment Auditing Not Capturing Events
Symptoms: Dataverse entity changes or user sign-ins not appearing in audit logs
Solutions:
- Verify environment-level auditing is enabled: PPAC > Environments > select environment > Settings > Audit and logs > Audit settings > "Start Auditing" must be enabled
- Verify tenant-level auditing: PPAC > Security > Compliance > Auditing > both "User Sign-In" and "Activity" must be enabled
- Check audit log retention meets zone requirements (Zone 1: ≥180 days, Zone 2: ≥365 days, Zone 3: ≥730 days)
- Ensure auditing is enabled on the specific Dataverse tables/entities you expect to see
- Allow for ingestion latency (may take up to several hours for Dataverse events)
Issue: PowerShell Connection Failures
Symptoms: Connect-ExchangeOnline or Connect-IPPSSession fails with authentication or module errors
Common error messages:
"The term 'Connect-ExchangeOnline' is not recognized"— Module not installed"AADSTS50076: Due to a configuration change made by your administrator"— MFA required"New-ExoPSSession: Access is denied"— Insufficient permissions
Solutions:
- Install or update the module:
Install-Module ExchangeOnlineManagement -MinimumVersion 3.0.0 -Force - For MFA-enabled accounts, use
Connect-ExchangeOnlinewithout-Credential(opens browser prompt) - Verify your account has the required admin roles (Purview Audit Admin, Exchange Online Admin)
- If behind a proxy, configure PowerShell proxy settings before connecting
- Try
-ShowBanner:$falseto suppress banner output that may interfere with automation
Escalation Path
If issues persist:
- First tier: Purview Audit Admin - verify configuration
- Second tier: Security Operations - check SIEM integration
- Third tier: Microsoft Support - platform-level issues
Related Playbooks
- Portal Walkthrough — Step-by-step portal configuration
- PowerShell Setup — PowerShell scripts and automation
- Verification & Testing — Verification procedures and evidence collection
- Purview Audit Query Pack — Saved audit searches and evidence collection
Automated Validation Available
For automated audit configuration validation, drift detection, and approval-gated remediation, see the Audit Compliance Manager (ACM) solution.
Updated: February 2026 | Version: v1.3