Change in behavior of the HighCompleteness parameter in the Search-UnifiedAuditLog cmdlet
From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Rollout
Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
Schedule dates changed in the text
Date phrases in schedule sentences differ between the versions we saw- Seen 27 Jan 2025
late January 2025
Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.
What the notice says
Microsoft’s text, safely structuredUpdated 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
What changed
Between archive captures, newest first- Tags
Feature update, Admin impact→ Updated message, Feature update, Admin impact
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 … allowed customers to toggle between prioritizing completeness of search results and performance.
When the HighCompleteness parameter is set to true,We previously announced a change in thesearch query returns a more complete setbehavior ofsearch results, butthequery may take a longer timeSearch-UnifiedAuditLog cmdlet, specific tofinish. When set to false,the functioning of thequery runs faster but only returns a subset of results. We recommended setting theHighCompleteness parameter. We had announced plans to deprecate support for this parameterto true in scenarios where a complete list ofand enforce HighCompleteness on all searchresults was required. To improve our customers’ visibility into their security loggingqueries submitted via the Search-UnifiedAuditLog cmdlet. Several customers andreduce instances of customers missingpartners reached outon important audit records in their search results, we are now changingto us with concerns about thebehaviorperformance of theHighCompleteness parameter. Previously, customers could toggle the parameter between true or false. With this change, the HighCompleteness parameter will always be setcmdlet in certain scenarios when HighCompleteness is enabled. Based on these concerns, we have decided totrue. When this will happen: General Availability (Worldwide, GCC, GCC-High, DoD): Starting late January 2025, for all search queries submitted viapostpone theSearch-UnifiedAuditLog cmdlet, the valuedeprecation of the HighCompleteness parameterwill be set to true. How thisto a future date. This postponement willaffect your organization: The HighCompleteness parameter in the Search-UnifiedAuditLog cmdlet will now be set to true for all queries. With this change,allow us to address these concerns before making any lasting changes in the behavior of thecmdlet will now prioritize completeness of search results over performance. As a result,cmdlet, and to minimize any impact on customers relying on this cmdlet. To searchqueries may take longer to finish. Whatthe audit log programmatically, youcan do to prepare: Youcould also consider using our new Audit Search Graph API for programmatic access to audit logs.This API is now Generally Available to all our Worldwide and Gov customers.Learn more about Purview Audit: Learn about auditing solutions in Microsoft Purview …- Tags
- · first version seen
Learn more
Links from the notice and their documentation checks- Search-UnifiedAuditLog cmdletNot read yet
- HighCompleteness parameterNot read yet
- Learn about auditing solutions in Microsoft Purview | Microsoft LearnChecked 15 Nov 2026
Related public changes
- Official documentation · 13 Oct 2026Audit solutions Shared reference: https://learn.microsoft.com/en-us/purview/audit-solutions-overview
- Public source · 12 Oct 2026MC1505599: Microsoft Purview Audit: AuditLogQuery API generally available and Search-UnifiedAuditLog retiring Microsoft 365 Message Center Archive by Merill FernandoShared reference: https://learn.microsoft.com/en-us/purview/audit-solutions-overview
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
- 1 linked page has not been read yet.