KustoManagementClient

Name: KustoManagementClient API
Brand: KustoManagementClient
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth234 EndpointsREST

For Agents

Provision and manage Azure Data Explorer (Kusto) clusters, databases, and data connections through Azure Resource Manager. Use for cluster lifecycle and configuration, not for running KQL queries.

Connect the KustoManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the KustoManagementClient, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with KustoManagementClient API.

Create, scale, and delete Azure Data Explorer clusters across regions and SKUs

Provision and manage Kusto databases with retention and cache policies

Configure Event Hub, IoT Hub, and Event Grid data connections that stream into Kusto databases

Attach follower databases to share data between Kusto clusters via AttachedDatabaseConfigurations

GET STARTED

Start building with KustoManagementClient API

Explore with Jentic

View OpenAPI Document

Use for: I need to provision a new Azure Data Explorer cluster in West Europe, Scale up an existing Kusto cluster to a larger SKU, Create a database inside a Kusto cluster with a 90-day retention policy, Set up an Event Hub data connection that streams telemetry into a Kusto table

Not supported: Does not run KQL queries, ingest event data, or manage table schemas — use only for provisioning and configuring Kusto clusters, databases, and data connections through Azure Resource Manager.

Jentic publishes the only available OpenAPI document for KustoManagementClient, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for KustoManagementClient, keeping it validated and agent-ready. KustoManagementClient is the Azure Resource Manager control plane for Azure Data Explorer (ADX) — it provisions and manages Kusto clusters, the databases inside them, attached database configurations, and data ingestion connections (Event Hub, IoT Hub, Event Grid). It does not run KQL queries or ingest data; it shapes the infrastructure that the ADX query engine runs on.

Use Cases

Patterns agents use KustoManagementClient API for, with concrete tasks.

★ Provision Telemetry Analytics Infrastructure

Platform teams building observability or product analytics pipelines need to stand up Azure Data Explorer clusters that ingest high-volume telemetry from Event Hubs. KustoManagementClient handles the full cluster lifecycle (PUT on /clusters/{clusterName}), database creation, and Event Hub data-connection wiring in one Azure Resource Manager flow. Provisioning a Standard_D13_v2 cluster typically takes 10-15 minutes via the asynchronous PUT pattern.

Create a new Kusto cluster named 'telemetry-prod' in eastus with SKU Standard_D13_v2 and capacity 2, then create a database 'events' with 90-day soft-delete retention, then add an Event Hub data connection pointing at the 'raw-events' hub.

Cost Control Through Cluster Stop/Start

Engineering teams reduce Azure Data Explorer compute spend by stopping non-production clusters outside business hours and restarting them on demand. The Clusters_Stop and Clusters_Start endpoints suspend compute billing while preserving data and configuration. A scheduled agent or runbook can list clusters tagged with environment=dev and stop them at 18:00, then restart at 08:00.

List Kusto clusters in the subscription tagged environment=dev, then call Clusters_Stop on each cluster that is currently in the Running state.

Multi-Tenant Follower Database Sharing

SaaS platforms expose customer-facing analytics by attaching follower databases from a central leader cluster to per-tenant clusters. The AttachedDatabaseConfigurations resource lets you configure read-only follower attachments without copying data. This pattern keeps storage costs flat while letting tenant-side clusters scale independently for query concurrency.

Create an AttachedDatabaseConfiguration on the 'tenant-a' cluster that follows the 'shared-analytics' database from the leader cluster's resource ID, with default principal modifications kind 'None'.

AI Agent ADX Operations

AI agents handling DevOps or SRE workloads use Jentic to discover and execute Kusto management operations without hardcoding ARM URLs. The agent searches for an intent like 'create azure data explorer cluster', loads the Clusters_CreateOrUpdate schema from Jentic, and executes against management.azure.com using an OAuth 2.0 token retrieved from the Jentic vault.

Use Jentic to search 'provision azure data explorer cluster', load the Clusters_CreateOrUpdate operation schema, and execute a PUT to create the cluster in the requested resource group with the agent's scoped Azure credential.

Key Endpoints

34 endpoints — jentic publishes the only available openapi specification for kustomanagementclient, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Kusto/clusters/{clusterName}

Create or update a Kusto cluster

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Kusto/clusters

List all Kusto clusters in a subscription

POST

/subscriptions/{subscriptionId}/providers/Microsoft.Kusto/locations/{location}/checkNameAvailability

Check if a cluster name is available

PATCH

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Kusto/clusters/{clusterName}

Update an existing cluster

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Kusto/clusters/{clusterName}

Delete a Kusto cluster

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Kusto/skus

List available Kusto SKUs

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Kusto/clusters/{clusterName}

Create or update a Kusto cluster

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Kusto/clusters

List all Kusto clusters in a subscription

POST

/subscriptions/{subscriptionId}/providers/Microsoft.Kusto/locations/{location}/checkNameAvailability

Check if a cluster name is available

PATCH

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Kusto/clusters/{clusterName}

Update an existing cluster

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Kusto/clusters/{clusterName}

Delete a Kusto cluster

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AAD client credentials and refresh tokens are stored encrypted in the Jentic vault. Agents receive a short-lived bearer token scoped to https://management.azure.com/ at call time — the client secret is never exposed to the agent's prompt or logs.

Intent-based discovery

Agents search by intent (for example, 'provision azure data explorer cluster') and Jentic returns the matching Clusters_CreateOrUpdate operation with the full ARM input schema, so the agent can call the right endpoint without reading Microsoft Docs.

Time to first call

Direct ARM integration: 2-4 days for AAD app registration, token refresh handling, async poll loops, and 429 retry. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

LogicManagementClient

Build Azure Logic Apps that orchestrate data flow into Kusto.

Use when the agent needs to schedule or transform data being ingested into Azure Data Explorer rather than provision the cluster itself.

Alternative

HDInsightManagementClient

Provision Hadoop, Spark, and Kafka clusters as an alternative analytics platform.

Choose HDInsight when the workload needs Spark or Hadoop ecosystems; choose Kusto for log and time-series analytics with KQL.

Complementary

MonitorManagementClient

Configure Azure Monitor diagnostic settings that route platform logs into Kusto.

Use to wire Azure Monitor diagnostic exports into a Kusto database after the cluster is provisioned.

FAQs

Specific to using KustoManagementClient API through Jentic.

Why is there no official OpenAPI spec for KustoManagementClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call KustoManagementClient via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the KustoManagementClient use?

It uses Azure Active Directory OAuth 2.0 bearer tokens for the management.azure.com audience. Through Jentic, AAD client credentials live in the encrypted vault and a short-lived bearer token is injected into the Authorization header at call time — the client secret never enters the agent's context.

Can I run KQL queries with the KustoManagementClient?

No. This is the management plane. To execute KQL queries against a database, use the Azure Data Explorer query endpoint at https://{clusterName}.{region}.kusto.windows.net via the Kusto data-plane SDKs. KustoManagementClient only handles cluster, database, and connection lifecycle through Azure Resource Manager.

What are the rate limits for the KustoManagementClient?

Azure Resource Manager applies subscription-level throttling — typically 12,000 read and 1,200 write requests per hour per subscription per region, with 429 responses including a Retry-After header. Cluster create operations are long-running and return 202 Accepted with an Azure-AsyncOperation URL to poll.

How do I provision a Kusto cluster through Jentic?

Run pip install jentic, then search Jentic for 'provision azure data explorer cluster'. Jentic returns the Clusters_CreateOrUpdate schema (PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Kusto/clusters/{clusterName}). Load it, fill in SKU and location, then execute — Jentic handles AAD token injection.

Can I add an Event Hub data connection to a Kusto database?

Yes. Use the DataConnections sub-resource on a Kusto database to wire up Event Hub, IoT Hub, or Event Grid streaming ingestion. The connection definition includes the Event Hub resource ID, consumer group, target table, and data format (JSON, CSV, etc.).