Back to catalog / Integrations
Azure Kusto: discover cluster/database before bounded KQL
Locate data before using time filters, aggregation, joins, or schema discovery.
Skills
List candidate clusters/databases/workspaces in the subscription. When the table location is unknown, check all candidates rather than treating the first empty result as not found. Use schema-aware KQL with bounded time ranges, explicit projected columns, aggregation, and necessary joins. Report source cluster/database, period, sample/count, and field meaning while minimizing unrelated data. Base conclusions on query results and do not write or expand to another tenant without authorization.
Permissions
Prerequisites
- Discover Azure Data Explorer or Log Analytics tables and analyze them with KQL.
Permissions
- Queries telemetry/business data; bound time windows, projected columns, and result size.
Limitations
Prefer read-only; search all candidate sources before reporting not found.
Pinned upstream source
- Repository
- microsoft/skills
- File path
- .github/plugins/azure-skills/skills/azure-kusto/SKILL.md
- Pinned commit
fc164ba1d7a0c10377dbcc1c9ac07253b9329fdb- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: MIT
Compatible tools
Azure MCP Kusto/query tools · KQL · resource discovery
Main topic
Take a coding Agent change from context to verification