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 |
1---2name: eventhouse-cli3description: 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.4---5
6> **Telemetry — MANDATORY.** Every `api.fabric.microsoft.com` call must carry
7> `x-ms-fabric-skill: eventhouse-cli` (`az rest`: `--headers "x-ms-fabric-skill=eventhouse-cli"`),
8> including every LRO poll, `fabric_lro` and retry. Snippets omit it — add it anyway.
9
10> **CRITICAL NOTES**
11> 1. To find the workspace details (including its ID) from workspace name: list all workspaces and, then, use JMESPath filtering
12> 2. 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
13> 3. **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.
14
15# Fabric Eventhouse / KQL Database -- CLI Skill
16
17This one skill owns Fabric Eventhouse and KQL Database: schema and ingestion management plus read-only KQL analytics.
18
19It 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.
20
21## Mode selection
22
23| Mode | Use when the request ... | Example triggers | Read this first |
24|---|---|---|---|
25| `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](references/authoring.md) |
26| `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](references/consumption.md) |
27
28### Mode boundary rule
29
30`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.
31
32If 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.
33
34## Reference index
35
36Read the mode reference first; open a topic file below only when the task needs it. Every
37reference is listed here, so read it from this table rather than following a link out of
38another reference.
39
40| Reference | Read it when |
41|---|---|
42| [references/authoring.md](references/authoring.md) | any `authoring` request -- start here |
43| [references/authoring-core.md](references/authoring-core.md) | you need the capability matrix, table/schema, ingestion, policy, external table or permission detail behind an authoring task |
44| [references/authoring-advanced-operations.md](references/authoring-advanced-operations.md) | materialized views, stored functions, update policies, schema evolution, or monitoring authoring operations |
45| [references/authoring-scripts.md](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** |
46| [references/consumption.md](references/consumption.md) | any `consumption` request -- start here |
47| [references/consumption-discovery-queries.md](references/consumption-discovery-queries.md) | you need the `.show` discovery queries for schema, tables or ingestion health |
48| [EVENTHOUSE-CONSUMPTION-CORE.md](../../common/EVENTHOUSE-CONSUMPTION-CORE.md) | connection fundamentals, schema discovery and security, monitoring, performance best practices, or common KQL query patterns -- **read before writing KQL** |
49
50## Terminal write -- the step you must not skip
51
52Reading 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.
53
54| Mode | Terminal write |
55|---|---|
56| `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. |
57| `consumption` | none -- this mode is read-only |
58
59Before 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.
60
61## Shared essentials (all modes)
62
63Resolve the workspace and item first; every mode depends on it.
64
65| Task | Reference | Notes |
66|---|---|---|
67| Finding Workspaces and Items in Fabric | [COMMON-CLI.md](../../common/COMMON-CLI.md#finding-workspaces-and-items-in-fabric) | **Mandatory** -- read before resolving any workspace or item id |
68| Fabric Topology & Key Concepts | [COMMON-CORE.md](../../common/COMMON-CORE.md#fabric-topology--key-concepts) | Item types, workspaces, capacities |
69| Environment URLs | [COMMON-CORE.md](../../common/COMMON-CORE.md#environment-urls) | Sovereign / non-public cloud hosts |
70| Authentication & Token Acquisition | [COMMON-CORE.md](../../common/COMMON-CORE.md#authentication--token-acquisition) | Wrong audience = 401; read before any auth issue |
71| Authentication Recipes | [COMMON-CLI.md](../../common/COMMON-CLI.md#authentication-recipes) | `az login` flows and token acquisition |
72| Core Control-Plane REST APIs | [COMMON-CORE.md](../../common/COMMON-CORE.md#core-control-plane-rest-apis) | Pagination, LRO polling, rate limiting |
73| Gotchas & Troubleshooting | [COMMON-CLI.md](../../common/COMMON-CLI.md#gotchas--troubleshooting-cli-specific) | `az rest` audience, shell escaping, token expiry |
74
75## Rules
76
77### MUST
78
79- Select exactly one mode from the table above before doing anything else.
80- 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.
81- 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.
82- Resolve workspace and item ids by listing and filtering, never by guessing a GUID.
83- Announce a mode switch explicitly when the request crosses a boundary.
84- 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.
85
86### PREFER
87
88- The narrowest mode that satisfies the request.
89- Reading exactly ONE mode reference. Load a second only when the request genuinely spans modes, and say so before you do.
90- Reporting the mode you chose in your first response so the user can correct you.
91
92### AVOID
93
94- Acting from this dispatcher alone -- it intentionally omits the operational detail.
95- Answering with a summary of the reference instead of executing it.
96- Re-reading or re-grepping a reference you already loaded; it costs turns and tokens.
97- Mutating anything while in a read-only mode.
98- Loading a different skill for work this family already owns (see CRITICAL NOTES 3).
99
100## Examples
101
102| User request | Mode | Reference to read |
103|---|---|---|
104| "How many events arrived per hour in the last day in the Telemetry eventhouse?" | `consumption` | [references/consumption.md](references/consumption.md) |
105| "Create a KQL table for the sensor feed and a 30-day retention policy." | `authoring` | [references/authoring.md](references/authoring.md) |
106| "Show me the tables in the KQL database and their row counts." | `consumption` | [references/consumption.md](references/consumption.md) |
Microsoft