Published Dec 12, 2024
The HighCompleteness parameter in the Search-UnifiedAuditLog cmdlet will be permanently set to true starting late January 2025, ensuring more complete search results at the expense of longer query times. Users are advised to prepare and consider using the Audit Search Graph API.
Updated January 27, 2025: We have updated the content. Thank you for your patience.
The Search-UnifiedAuditLog cmdlet gives administrators in your organization access to critical audit log event data to gain insights and further investigate user activities. Microsoft had introduced a new HighCompleteness parameter in this cmdlet in April 2024 that allowed customers to toggle between prioritizing completeness of search results and performance.
We previously announced a change in the behavior of the Search-UnifiedAuditLog cmdlet, specific to the functioning of the HighCompleteness parameter. We had announced plans to deprecate support for this parameter and enforce HighCompleteness on all search queries submitted via the Search-UnifiedAuditLog cmdlet.
Several customers and partners reached out to us with concerns about the performance of the cmdlet in certain scenarios when HighCompleteness is enabled. Based on these concerns, we have decided to postpone the deprecation of the HighCompleteness parameter to a future date. This postponement will allow us to address these concerns before making any lasting changes in the behavior of the cmdlet, and to minimize any impact on customers relying on this cmdlet.
To search the audit log programmatically, you could also consider using our new Audit Search Graph API for programmatic access to audit logs.
Learn more about Purview Audit: Learn about auditing solutions in Microsoft Purview | Microsoft Learn
Learn more about the Search-UnifiedAuditLog cmdlet: Search-UnifiedAuditLog (ExchangePowerShell) | Microsoft Learn