Microsoft Azure HDInsightManagementClient
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth24 EndpointsREST
For Agents
Install, list, and remove HDInsight cluster applications — the optional add-on workloads installed on a running HDInsight cluster.
Use for: I need to install an HDInsight cluster application on 'analytics-prod', List all applications running on cluster 'analytics-prod', Retrieve the status of the 'jupyter-extension' application on a cluster, Remove an unused cluster application to free resources
Not supported: Does not provision HDInsight clusters, submit jobs, or manage Spark workloads — use for installing and removing cluster applications on existing HDInsight clusters only.
Jentic publishes the only available OpenAPI specification for HDInsightManagementClient, keeping it validated and agent-ready. The HDInsight Management API manages HDInsight cluster applications — the optional add-on workloads that can be installed onto a running HDInsight cluster, such as third-party tools or custom services. This 2018-06-01-preview surface is focused specifically on the application lifecycle: list, get, create, and delete. Authentication is Azure AD OAuth2 against management.azure.com, and the resource is scoped under Microsoft.HDInsight/clusters/{clusterName}/applications.
Install Jentic One Beta
Connect the HDInsightManagementClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the HDInsightManagementClient, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: 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 instanceJentic 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 HDInsightManagementClient API.
Install a new application onto an existing HDInsight cluster
List all applications attached to a specific HDInsight cluster
Retrieve the configuration and state of a single cluster application
Remove an application from a cluster when it is no longer needed
Verify that a cluster application has reached a terminal provisioning state
Use Cases
Patterns agents use HDInsightManagementClient API for, with concrete tasks.
★ Install a third-party application on a cluster
Use PUT on /subscriptions/.../clusters/{clusterName}/applications/{applicationName} to deploy an application onto an existing HDInsight cluster. The API accepts the application definition and returns 202 with an Azure-AsyncOperation header that callers poll until the application reaches Succeeded. Useful when standardising tooling installs across a fleet of HDInsight clusters.
PUT /subscriptions/{sub}/resourceGroups/{rg}/providers/Microsoft.HDInsight/clusters/analytics-prod/applications/jupyter-extension with the agreed application definition body and poll until provisioningState is Succeeded.
Inventory of installed applications
List all applications on a cluster via GET /subscriptions/.../clusters/{clusterName}/applications. The response gives application name, kind, and current state, suitable for a fleet inventory dashboard. Useful when verifying that all clusters share the same baseline tooling.
GET /subscriptions/{sub}/resourceGroups/{rg}/providers/Microsoft.HDInsight/clusters/analytics-prod/applications and return the names and provisioning states of all installed applications.
Remove an unused application
Delete a cluster application via DELETE /subscriptions/.../clusters/{clusterName}/applications/{applicationName}. The DELETE returns 202 and runs asynchronously while the application's resources are torn down. Useful at the end of a tooling deprecation cycle.
DELETE the 'old-jupyter' application from cluster 'analytics-prod' and poll the async operation until provisioning is removed.
AI agent cluster tooling management via Jentic
An infrastructure agent uses Jentic to standardise tooling on every HDInsight cluster — listing what is installed, installing missing applications, and removing deprecated ones. Jentic resolves natural-language intents to the right Applications operation and injects the bearer token at execution time.
Use Jentic to search for 'install an application on an hdinsight cluster', load Applications_Create, and execute it for 'jupyter-extension' on cluster 'analytics-prod'.
Key Endpoints
4 endpoints — jentic publishes the only available openapi specification for hdinsightmanagementclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HDInsight/clusters/{clusterName}/applications
List applications on a cluster
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HDInsight/clusters/{clusterName}/applications/{applicationName}
Get a specific cluster application
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HDInsight/clusters/{clusterName}/applications/{applicationName}
Install an application on a cluster
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HDInsight/clusters/{clusterName}/applications/{applicationName}
Delete an application from a cluster
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HDInsight/clusters/{clusterName}/applications
List applications on a cluster
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HDInsight/clusters/{clusterName}/applications/{applicationName}
Get a specific cluster application
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HDInsight/clusters/{clusterName}/applications/{applicationName}
Install an application on a cluster
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HDInsight/clusters/{clusterName}/applications/{applicationName}
Delete an application from a cluster
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure service principal credentials sit encrypted in the Jentic vault. Agents receive a scoped Azure AD bearer token at execution time and never see the raw client secret.
Intent-based discovery
Agents search Jentic for 'install an application on an hdinsight cluster' and Jentic returns the Applications_Create operation with its input schema.
Time to first call
Direct ARM integration: 1-2 days for AAD setup and async polling. Through Jentic: under 30 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using HDInsightManagementClient API through Jentic.
Why is there no official OpenAPI spec for HDInsightManagementClient?
Microsoft Azure does not publish a stand-alone OpenAPI specification for the 2018-06-01-preview HDInsight applications surface. Jentic generates and maintains this spec from the Microsoft.HDInsight ARM surface so that AI agents and developers can call HDInsightManagementClient 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 this API use?
It uses Azure AD OAuth2 against management.azure.com, declared as the azure_auth security scheme. Through Jentic, your service principal credentials sit in the encrypted vault and are exchanged for a scoped bearer token at execution time.
Does this API let me create a cluster?
No. This 2018-06-01-preview surface is scoped to cluster applications only — install, list, get, and delete add-on workloads on an existing cluster. To provision the cluster itself, use a more recent HDInsight Management API or ARM template that exposes the clusters resource.
What are the rate limits?
Standard ARM throttles apply at the subscription level — about 12,000 reads and 1,200 writes per hour per subscription. PUT and DELETE on applications are long-running, so callers should poll the Azure-AsyncOperation header rather than retry the original request.
How do I install a cluster application through Jentic?
Run jentic.search('install an application on an hdinsight cluster'), load the Applications_Create schema, and execute it with the subscription, resource group, cluster name, application name, and the application definition body. The PUT returns 202 and the async operation reports success once installation completes.
GET STARTED