Forum Discussion

JoshuaPalmer's avatar
JoshuaPalmer
Copper Contributor
Jul 29, 2025

eDiscovery keyword statistics.

Noticing with this roadmap item: https://admin.microsoft.com/AdminPortal/Home?#/MessageCenter/:/messages/MC1105008 specifically 

  • Expanded search condition builder with support for logical operators (AND, OR, NEAR) in the keywords field

That when running a new search that the statistics generated for keywords claims that "Query does not contain keywords" and doesn't generate the Statistics reports for keywords anymore. 

Tried with keywords on multiple lines as well as same line but separated with OR statements. 

 

Is this known issue? 

3 Replies

  • Alex409's avatar
    Alex409
    Copper Contributor

    Thanks for sharing! It looks like there might be a bug with keyword statistics in the new search. I haven't heard about it yet, but you should let Microsoft Support know. Hopefully, they'll fix it soon!

  • Hello JoshuaPalmer

    The particular roadmap item you mentioned is a work in progress and the roll out might go on till late September 2025. 

    Hence, it might not be related to what you are facing at the moment. 

    Having said that, refer to this for some troubleshooting tips on the same: Resolve Search Errors in eDiscovery (Standard) - Microsoft 365 | Microsoft Learn

    Also make sure you are building the right query with the right syntax, for example, 

    1. Boolean operator must be uppercase
    2. Keyword searches are not case sensitive
    3. Using quotes would stop wild cards or operations inside the quotes, etc.

    For a more detailed tips and tricks and general recommendations on Keyword search, refer to: Keyword queries and search conditions for eDiscovery | Microsoft Learn

    Hope this helps! 

    Regards, 

    PI

    Please mark as solution, if you find the answer helpful. This will assist others in the community who encounter a similar issue, enabling them to quickly find the solution and benefit from the guidance provided.

    • JoshuaPalmer's avatar
      JoshuaPalmer
      Copper Contributor

      This actually seemed to start working a bit over half a week later, so assuming rollout was incremental when it hit our tenant. 

Resources