How to use
Four ways to build a query — each feeds the query editor below, which is parsed and validated against the eDiscovery catalog and run against a small synthetic corpus.
- Describe it in English — the natural-language box translates common phrases ("emails from Pilar last month about Tradewinds") into KeyQL.
- Use the condition builder — property/operator/value rows; synthetic samples built in.
- Pick a scenario — ready-made templates for common search shapes.
- Type directly in the editor — autocompletion for properties, operators, and enum values.
Describe a query in English
Experimental. Recognizes common eDiscovery phrasings — sender/recipient, date windows, file types, attachments, keywords. If a name isn't in the synthetic pool, it flags a warning rather than echo a real identity.
Condition builder
Mirrors the Purview condition builder. Each row is one property restriction — values come from the synthetic data palette so you don't type real names.
Operator reference — click to expand
Scenarios
Templates for the most common eDiscovery search shapes. All identities, project names, and domains are synthetic. Selecting one replaces the editor content below.
Query editor
Syntax-highlighted KeyQL. Ctrl/⌘ + space triggers autocomplete.
Diagnostics
Dry-run matches
Evaluates the parsed query against a small synthetic corpus of 11 items (mail, Teams, and documents). Useful for sanity-checking scope before filing a real eDiscovery collection.