eventhouse-consumption-cli

Use az rest to POST to the cluster's /v1/rest/query endpoint with resource https://kusto.kusto.windows.net. Write the JSON body containing the database name and KQL query to a temp file and pass it with --body @file to avoid shell escaping issues with pipe characters.

Call the Fabric REST API to list kqlDatabases in your workspace with az rest, then read the queryServiceUri and databaseName from the item properties. Cluster URIs are per-item, so always resolve them dynamically rather than hardcoding.

KQL queries contain pipe characters that break inline shell escaping in both bash and PowerShell. Write the JSON request body to a temp file and reference it with --body @file instead of inlining the query string.

A 401 usually means the wrong token audience; use --resource https://kusto.kusto.windows.net for KQL queries and https://api.fabric.microsoft.com for control-plane calls. A 403 means you need the viewer role on the KQL Database.

No, this skill is strictly read-only and does not create, alter, or drop database objects. For authoring operations like table management, ingestion, and policies, use the eventhouse-authoring-cli skill instead.

Run the query with az rest and save output with --output-file results.json, then pipe it through jq to map column names and rows into CSV format using the @csv filter.