Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

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 structured

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

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 the search query returns a more complete set behavior of search results, but the query may take a longer time Search-UnifiedAuditLog cmdlet, specific to finish. When set to false, the functioning of the query runs faster but only returns a subset of results. We recommended setting the HighCompleteness parameter. We had announced plans to deprecate support for this parameter to true in scenarios where a complete list of and enforce HighCompleteness on all search results was required.  To improve our customers’ visibility into their security logging queries submitted via the Search-UnifiedAuditLog cmdlet. Several customers and reduce instances of customers missing partners reached out on important audit records in their search results, we are now changing to us with concerns about the behaviorperformance of the HighCompleteness parameter. Previously, customers could toggle the parameter between true or false. With this change, the HighCompleteness parameter will always be set cmdlet in certain scenarios when HighCompleteness is enabled. Based on these concerns, we have decided to true.  When this will happen: General Availability (Worldwide, GCC, GCC-High, DoD): Starting late January 2025, for all search queries submitted via postpone the Search-UnifiedAuditLog cmdlet, the value deprecation of the HighCompleteness parameter will be set to true.  How thisto a future date. This postponement will affect 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 the cmdlet 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 search queries may take longer to finish.  What the audit log programmatically, you can do to prepare: You could 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 …

  1. · first version seen

Learn more

Links from the notice and their documentation checks

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.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 15 Nov 23:13 UTC · 274 of 275 readable · 250 fully read · 18 waiting for GitHub's hourly limit · documentation 461/469 current