Microsoft 365 Unified Audit Log Not Enabled

Microsoft Purview audit is not recording user and administrator activity, so actions across Exchange Online, SharePoint, OneDrive, Teams and Entra ID leave no searchable trail.

SeverityMedium
CVSS 3.14.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N Open in the calculator
CVSS 4.05.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-778: Insufficient Logging
OWASP Top 10A09:2025 Security Logging and Alerting Failures
CategoryInsufficient Logging

Description

The Microsoft 365 unified audit log, searched through Microsoft Purview Audit, brings together records of user and administrator activity across the tenant's services: mailbox access and changes, file access, sharing and downloads in SharePoint and OneDrive, Teams activity, Microsoft Entra ID administration and changes to security settings. It is the main source of evidence when investigating a compromised account or a suspected data breach in Microsoft 365.

Audit recording is on by default for most organisations, but it can be switched off, and older tenants or tenants configured by scripts are sometimes found with it disabled. While it is off, the organisation cannot establish what an attacker did with a compromised account: which emails were read or forwarded, which files were downloaded or shared, which mailbox rules were created and which settings were changed. The log cannot be enabled retrospectively: activity that occurs before recording is switched on is never captured.

This hampers containment, prevents the organisation from scoping a breach accurately, and may leave it unable to show regulators or affected people what data was accessed. It also removes the data that alert policies and SIEM integrations depend on, so attacks in progress go unnoticed.

The finding is identified in Exchange Online PowerShell, where Get-AdminAuditLogConfig reports UnifiedAuditLogIngestionEnabled as False, or in the Purview portal, which offers to start recording user and admin activity while it is off. A related organisation-wide setting controls mailbox auditing, and individual mailboxes can be excluded from auditing: Get-OrganizationConfig shows through AuditDisabled whether mailbox auditing is disabled for the whole organisation.

Remediation

Turn on audit recording, either from the Audit page of the Microsoft Purview portal or in Exchange Online PowerShell, and make sure mailbox auditing is not disabled for the organisation:

Set-AdminAuditLogConfig -UnifiedAuditLogIngestionEnabled $true Set-OrganizationConfig -AuditDisabled $false
  • Review mailboxes excluded from auditing through mailbox audit bypass associations, and remove exclusions that are not justified.
  • Check that the retention period meets investigation and regulatory needs. Where it does not, use Audit (Premium) retention policies, or export the records to a SIEM through the Office 365 Management Activity API or the Microsoft Sentinel connector for longer retention and correlation.
  • Create alert policies or SIEM detections for high-risk activity, such as new forwarding rules, mailbox permission changes, mass downloads and changes to the audit configuration itself.
  • Restrict the roles that can change the audit configuration, and alert on any change to it.

Confirm the fix by running Get-AdminAuditLogConfig again and by searching the audit log for a test activity performed after the change, allowing time for records to appear.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Azure and Microsoft 365 Findings

Every Azure and Microsoft 365 finding