Skip to content
CSA Loom — the Microsoft Fabric experience for Azure tenants where Fabric isn't yet available: lakehouses, warehouses, notebooks, semantic models, Activator rules, Data Agents, across Commercial, GCC, GCC-High, and DoD IL5

Tutorial: KQL database editor

CSA Loom kql-database editor — verified working against a live console by the UAT harness on 2026-07-01.

Open the editor

  1. Sign in to your CSA Loom Console (for example https://<your-console-host>).
  2. Open or create a workspace from the Workspaces page.
  3. Click + New item and choose KQL database from the catalog.
  4. The editor opens at /items/kql-database/<id>:

KQL database editor

What this editor does

A KQL database is a Kusto store for high-volume, low-latency analytics over time-series, telemetry, and logs. In Loom it is Azure-native: it runs on the shared Loom Azure Data Explorer (ADX) cluster and is queried with KQL — no Microsoft Fabric or OneLake required.

Getting started

  1. Ingest data — Bring data in from an Eventstream, Event Hubs, or a direct REST POST.
  2. Query with KQL — Open a KQL queryset to run interactive queries and pin charts to a Real-Time dashboard.
  3. Wire an Activator rule — Attach an Activator on a KQL query to fire on a threshold breach such as failure rate over 5 percent.
  4. Detect anomalies / Forecast — Run native-KQL time-series ML over any table from the ribbon's Detect anomalies / Forecast actions — series_decompose_anomalies / series_decompose_forecast over a make-series — then Add as tile to pin the result to a Real-Time dashboard. No external ML service required.
  5. Make data available as Delta — Configure ADX continuous export (or an external table) to land the same data as Delta in ADLS Gen2, so it's queryable alongside lakehouses — no OneLake needed.

Learn more

Verified by the UAT harness