Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Cloud Infrastructure / Azure / KustoManagementClient
KustoManagementClient logo

Microsoft Azure KustoManagementClient

Browse all Azure APIs
43
AI ReadinessFoundational (D-)43/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticCloud InfrastructureComputeoauth234 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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.

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 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.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-kustomanagementclient" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-kustomanagementclient" | 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

Check name availability and list available SKUs before provisioning a Kusto cluster

Detach Event Hub consumer groups and stop or start clusters to control compute spend

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 your Jentic One instance.

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

GET

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

List available Kusto SKUs

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

K

KustoManagementClient

- Foundational (D-)
43/100
60
Foundational Compliance
61
Developer Experience & Jentic Compatibility
21
AI-Readiness & Agent Experience
94
Agent Usability
35
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
60

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B-Signals: 4
81%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

60%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

61

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

49%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

93%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

21

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
85%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

0%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

35

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
35%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Kusto (Azure Data Explorer) management API by hand means registering an Azure AD app, negotiating OAuth 2.0 tokens for management.azure.com, and threading subscription and resource-group scope through every cluster and database call. Through Jentic you install once, import KustoManagementClient from the API Directory, store the Azure AD credential once, and your agent calls it.

Permission scoping

This API puts the cluster in the URL path (/resourceGroups/{resourceGroupName}/providers/Microsoft.Kusto/clusters/{clusterName}), so a rule can pin your agent to one cluster: it can read the cluster, list SKUs, and check name availability. You choose the operations it may call, so creating, updating, or deleting a cluster is not included unless you add it.

Credential isolation

Your Azure AD credential for the Kusto control plane is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list Kusto clusters' or 'check a Kusto cluster name', and Jentic returns the matching Kusto operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

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 with Jentic One, the self-hosted execution layer.

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.).

Can I limit what my agent is allowed to do with the Microsoft Azure Kusto API?

Yes. Because you run Jentic One yourself, your own rules decide which Kusto operations and credentials the agent may use, and the cluster name sits in the request path, so you can pin the agent to a single cluster. You might allow it only to read a cluster, list available SKUs, and check name availability, while withholding the create, update, and delete operations so it cannot provision or tear down infrastructure unless you explicitly add those. The same control applies to database and data-connection operations, so the agent calls only the endpoints you have approved.

GET STARTED

Start building with KustoManagementClient API

Explore with Jentic One
View OpenAPI Document