Eventhouse CLI

MicrosoftOfficialPublished by Microsoft

Skill
Tool integration
Data and AI
MIT
Low risk
Has scripts

From the author

Authors and queries Fabric Eventhouse and KQL databases: tables, functions, policies, materialized views, ingestion, and read-only KQL for real-time and time-series analytics. All KQL database work belongs here, table creation and simple queries included. An Eventstream item is eventstream-cli; an Event Schema Set is eventschemaset-cli.

— the description by Microsoft

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The eventhouse-cli skill provides a structured interface for interacting with Microsoft Fabric Eventhouse and KQL databases. It acts as a mode-based dispatcher, separating administrative tasks like schema management and ingestion from read-only analytical queries. Users must select between authoring and consumption modes and consult the corresponding reference documentation before executing commands to ensure correct payload construction and operational safety.

What it does

Executes KQL management commands for table creation, alteration, and dropping.
Manages ingestion processes, including inline data, storage-based ingestion, and streaming policies.
Configures database policies such as retention, caching, and update policies.
Supports advanced operations like materialized views and stored functions.
Facilitates read-only KQL analytical queries and schema discovery.
Provides a framework for safe schema evolution and deployment scripts.

When to use it

When you need to define or modify the schema of a KQL database.
When performing real-time or time-series data analysis using KQL.
When automating data ingestion pipelines into Fabric Eventhouse.
When configuring database-level policies or materialized views.
When auditing database schema or monitoring ingestion health.

Advantages

Enforces a clear separation between read-only analytics and state-changing administrative tasks.
Provides standardized patterns for safe schema evolution and idempotent deployments.
Integrates directly with Fabric's REST API for programmatic database management.
Supports complex KQL operations including update policies and materialized views.

Usage examples

“Create a new KQL table named SensorData with columns for Timestamp, SensorId, and Value.”: The agent switches to authoring mode, reads the authoring reference, and executes a .create table command via the Fabric REST API.
“Show me the top 10 events from the last hour in the Telemetry database.”: The agent switches to consumption mode, reads the consumption reference, and executes a read-only KQL query against the specified database.
“Set a 30-day retention policy on the Events table.”: The agent switches to authoring mode, reads the authoring reference, and executes the .alter table policy retention command.

Install

Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/microsoft/eventhouse-cli/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip eventhouse-cli.zip -d .agents/skills

Documentation by Microsoft

Telemetry — MANDATORY. Every api.fabric.microsoft.com call must carry x-ms-fabric-skill: eventhouse-cli (az rest: --headers "x-ms-fabric-skill=eventhouse-cli"), including every LRO poll, fabric_lro and retry. Snippets omit it — add it anyway.

CRITICAL NOTES
To find the workspace details (including its ID) from workspace name: list all workspaces and, then, use JMESPath filtering
To find the item details (including its ID) from workspace ID, item type, and item name: list all items of that type in that workspace and, then, use JMESPath filtering
Skill disambiguation: use eventhouse-cli for anything expressed in KQL or stored in a KQL Database. Use the matching eventstream-cli mode for streaming topology, and the matching sqldw-* skill for T-SQL against a Warehouse or Lakehouse SQL endpoint.

Fabric Eventhouse / KQL Database -- CLI Skill

This one skill owns Fabric Eventhouse and KQL Database: schema and ingestion management plus read-only KQL analytics.

It is a mode dispatcher and contains NO procedures. Pick the mode that matches the request from the table below, then read the matching references/<mode>.md file end to end with your file-reading tool BEFORE issuing a single command. That file holds the endpoints, payload shapes, templates and gotchas; acting without it produces wrong payloads and wrong results.

Mode selection

Mode	Use when the request ...	Example triggers	Read this first
`authoring`	runs KQL management commands (`.create`, `.alter`, `.ingest`, `.drop`), policies, mappings, functions or materialized views	create kql table, kql ingestion, kql retention policy, kql function, materialized view, kql mapping	references/authoring.md
`consumption`	runs read-only KQL (`where`, `summarize`, `join`, `render`), discovers schema with `.show`, or monitors ingestion health	kql query, query eventhouse, time-series kql, show tables kql, explore eventhouse	references/consumption.md

Mode boundary rule

consumption may only issue read-only KQL and .show commands. Any dot-command that changes state (.create, .alter, .ingest, .drop, .set-or-append) requires the authoring mode: say so, read references/authoring.md, then proceed.

If a request genuinely spans modes, handle them one at a time and read each reference before you start that part. If the mode is ambiguous after reading this table, ask one short clarifying question instead of guessing.

Reference index

Read the mode reference first; open a topic file below only when the task needs it. Every reference is listed here, so read it from this table rather than following a link out of another reference.

Reference	Read it when
references/authoring.md	any `authoring` request -- start here
references/authoring-core.md	you need the capability matrix, table/schema, ingestion, policy, external table or permission detail behind an authoring task
references/authoring-advanced-operations.md	materialized views, stored functions, update policies, schema evolution, or monitoring authoring operations
references/authoring-scripts.md	you want a ready-to-run script for create-and-ingest, schema deployment, export or policies -- run them from `scripts/`, do not read them
references/consumption.md	any `consumption` request -- start here
references/consumption-discovery-queries.md	you need the `.show` discovery queries for schema, tables or ingestion health
EVENTHOUSE-CONSUMPTION-CORE.md	connection fundamentals, schema discovery and security, monitoring, performance best practices, or common KQL query patterns -- read before writing KQL

Terminal write -- the step you must not skip

Reading the reference and planning the change is NOT completing the task. Each mutating mode ends with one state-changing call. If you did not issue it, nothing was persisted -- say so explicitly rather than reporting success.

Mode	Terminal write
`authoring`	`POST .../v1/rest/mgmt` carrying the literal `.create-merge table` (or `CREATE TABLE`-equivalent), `.alter` or `.ingest` command. Composing the KQL management command and showing it to the user is not executing it.
`consumption`	none -- this mode is read-only

Before you report the task done, confirm the terminal call returned success and, where the reference documents a readback, read the artefact back to prove the change landed.

Shared essentials (all modes)

Resolve the workspace and item first; every mode depends on it.

Task	Reference	Notes
Finding Workspaces and Items in Fabric	COMMON-CLI.md	Mandatory -- read before resolving any workspace or item id
Fabric Topology & Key Concepts	COMMON-CORE.md	Item types, workspaces, capacities
Environment URLs	COMMON-CORE.md	Sovereign / non-public cloud hosts
Authentication & Token Acquisition	COMMON-CORE.md	Wrong audience = 401; read before any auth issue
Authentication Recipes	COMMON-CLI.md	`az login` flows and token acquisition
Core Control-Plane REST APIs	COMMON-CORE.md	Pagination, LRO polling, rate limiting
Gotchas & Troubleshooting	COMMON-CLI.md	`az rest` audience, shell escaping, token expiry

Rules

MUST

Select exactly one mode from the table above before doing anything else.
Read references/<mode>.md end to end, as your FIRST tool call, before the first command of that mode. Read it ONCE, in a single full read: do not re-open it, do not grep it again, and do not page through it. You already have it.
Apply the same read-once discipline to every other file you load, including nested references/<mode>/*.md sub-references and shared common/*.md files: open only the ones you actually need, read each ONCE end to end, and never grep or re-open one you already loaded.
Resolve workspace and item ids by listing and filtering, never by guessing a GUID.
Announce a mode switch explicitly when the request crosses a boundary.
Treat the reference as instructions, never as the deliverable. After reading it, RUN the documented commands against the live workspace and report the real results. Quoting what the reference says instead of executing it does not answer the request.

PREFER

The narrowest mode that satisfies the request.
Reading exactly ONE mode reference. Load a second only when the request genuinely spans modes, and say so before you do.
Reporting the mode you chose in your first response so the user can correct you.

AVOID

Acting from this dispatcher alone -- it intentionally omits the operational detail.
Answering with a summary of the reference instead of executing it.
Re-reading or re-grepping a reference you already loaded; it costs turns and tokens.
Mutating anything while in a read-only mode.
Loading a different skill for work this family already owns (see CRITICAL NOTES 3).

Examples

User request	Mode	Reference to read
"How many events arrived per hour in the last day in the Telemetry eventhouse?"	`consumption`	references/consumption.md
"Create a KQL table for the sensor feed and a 30-day retention policy."	`authoring`	references/authoring.md
"Show me the tables in the KQL database and their row counts."	`consumption`	references/consumption.md

Files

ATTRIBUTION.mdAdded by AutoGineer873 B
LICENSELicence file added by AutoGineer1.1 KiB
SKILL.md8.4 KiB
apm.yml403 B
references/authoring-advanced-operations.md5.5 KiB
references/authoring-core.md10.2 KiB
references/authoring-scripts.md3.3 KiB
references/authoring.md14.6 KiB
references/consumption-discovery-queries.md3.8 KiB
references/consumption.md10.9 KiB
scripts/create-table-and-ingest.ps1Script2.7 KiB
scripts/create-table-and-ingest.shScript1.8 KiB
scripts/deploy-schema.ps1Script2.5 KiB
scripts/deploy-schema.shScript2.1 KiB
scripts/export-schema.shScript698 B
scripts/set-policies.shScript1.6 KiB

references/authoring-scripts.md

Eventhouse Authoring Scripts

Runnable Bash and PowerShell scripts for common Eventhouse authoring operations via az rest. Execute these; do not read them into context. Only their output costs tokens, and a pre-written script is more reliable than regenerating one per run.

Every script authenticates through az, targets the Kusto endpoints (<cluster_uri>/v1/rest/mgmt and /v1/rest/query), and prints the rows it gets back. All of them stop at the first failed call and print a usage line when a required argument is missing. Management commands -- anything starting with ., including .show ... | project -- go to /mgmt; /query is only for expressions such as Events | count.

Bash scripts require jq (apt-get install jq, brew install jq, or winget install jqlang.jq). They use it for two things: reading .Tables[0].Rows out of the response, and building the request body with jq -n --arg, which JSON-escapes the KQL command. That escaping is not optional -- ingestion mappings and policy documents contain double quotes, and interpolating one into a JSON string produces a body az rest rejects. The PowerShell scripts get the same guarantee from ConvertTo-Json.

Bash
PowerShell
Adapting a script

Bash

create-table-and-ingest.sh — create the Events table with a CSV mapping, then optionally ingest a blob and report the row count.

bash scripts/create-table-and-ingest.sh <cluster_uri> <database> [blob_uri]

deploy-schema.sh — submit a .kql file as a single .execute database script with (ThrowOnErrors=true), then list tables, functions and materialized views. The whole file goes in one command rather than line by line, because a script exported by export-schema.sh contains multiline function bodies and policies that per-line execution would cut in half. ThrowOnErrors stops at the first bad command instead of reporting partial success. Use .create-merge commands so a re-run is idempotent.

bash scripts/deploy-schema.sh <cluster_uri> <database> <schema_file>

export-schema.sh — write the whole database schema out as a CSL script. Its output is exactly what deploy-schema.sh takes, so export and redeploy round-trip.

bash scripts/export-schema.sh <cluster_uri> <database> [output_file]

set-policies.sh — set retention and hot-cache policies on one table, then read both policies back.

bash scripts/set-policies.sh <cluster_uri> <database> <table> <retention_days> <cache_days>

PowerShell

create-table-and-ingest.ps1 — the Bash script above, for pwsh.

pwsh scripts/create-table-and-ingest.ps1 -ClusterUri <uri> -Database <db> [-BlobUri <uri>]

deploy-schema.ps1 — the schema deployment above, for pwsh.

pwsh scripts/deploy-schema.ps1 -ClusterUri <uri> -Database <db> -SchemaFile <path>

Adapting a script

The table name, column set and mapping in the create-and-ingest scripts are worked examples. When the request names a different table or schema, copy the script, edit the .create-merge and mapping commands, and run the copy. The kusto helper (Bash) and Invoke-KustoMgmt (PowerShell) inside each one is the pattern to reuse for any other management command.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

What our scanner noticed· Low risk

Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by

Microsoft

Publisher

Microsoft (Official)

Source

microsoft/skills-for-fabric · skills/eventhouse-cli · commit f8fac11

Licence

MIT License (redistribution allowed)

LICENSE (added by AutoGineer from LICENSE)
ATTRIBUTION.md (written by AutoGineer)

Synced

2026-11-08

Also distributed in

microsoft/skills-for-fabric

AutoGineer is not affiliated with or endorsed by Microsoft.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download eventhouse-cli.zip