Microsoft Azure Azure Log Analytics
Browse all Azure APIs42
AI ReadinessFoundational (D-)42/100
Agent-ready OpenAPI document · curated by JenticAnalyticsBusiness Intelligenceoauth26 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Provision and manage dedicated Azure Log Analytics Clusters, including capacity sizing, customer-managed key attachment, and cluster-level operations across resource groups and subscriptions.
Use for: I need to provision a dedicated Log Analytics cluster, List all Log Analytics clusters in my subscription, Attach a customer-managed key to a Log Analytics cluster, Resize the capacity reservation on a Log Analytics cluster
Not supported: Does not run KQL queries, manage workspaces, or ingest logs - use for Log Analytics cluster provisioning, sizing, and CMK configuration only.
Jentic publishes the only available OpenAPI specification for Azure Log Analytics, keeping it validated and agent-ready. The Azure Log Analytics API in this version manages dedicated Log Analytics Clusters within the Microsoft.OperationalInsights namespace. It lets operators provision a cluster, scale capacity reservations, attach customer-managed keys for encryption, and link workspaces into the cluster for cross-workspace querying. All requests go through Azure Resource Manager and authenticate with Azure AD OAuth 2.0.
Install Jentic One Beta
Connect the Azure Log Analytics to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Azure Log Analytics, 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-log-analytics" | sh2
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-log-analytics" | 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 Azure Log Analytics API.
Provision a Microsoft.OperationalInsights cluster with a specified capacity reservation SKU
List Log Analytics clusters scoped to a subscription or resource group
Update a cluster to attach a customer-managed key from Azure Key Vault
Resize a cluster's capacity reservation in 1,000 GB-per-day units
Delete a Log Analytics cluster and its associated capacity commitment
Retrieve a single cluster's properties including provisioning state and identity
Use Cases
Patterns agents use Azure Log Analytics API for, with concrete tasks.
★ Dedicated Cluster Provisioning for High-Volume Logging
Customers ingesting more than 1 TB of telemetry per day move from per-workspace pricing to a dedicated Log Analytics cluster for cost predictability and customer-managed encryption. The PUT call on the clusters resource accepts a capacity reservation SKU expressed in GB-per-day commitments and returns the cluster record with provisioning state. A single cluster can later host multiple linked workspaces.
Create a Log Analytics cluster named 'la-cluster-prod' in resource group 'rg-observability' in East US with capacity reservation SKU 'CapacityReservation' at 1000 GB/day.
Customer-Managed Key Attachment
Compliance teams require log data to be encrypted with a key under their control. The PATCH endpoint on a cluster updates the keyVaultProperties to point at a Key Vault key URI; once Azure validates that the cluster's managed identity has wrap and unwrap permissions, the cluster re-encrypts data with the new key. This satisfies BYOK requirements without redeploying workspaces.
Patch cluster 'la-cluster-prod' in 'rg-observability' to set keyVaultProperties.keyVaultUri to 'https://kv-logs.vault.azure.net' and keyName to 'la-cmk' at version '7d1b'.
Cluster Capacity Right-Sizing
Ingestion volumes drift over time, so platform teams periodically resize Log Analytics clusters up or down. The cluster PATCH operation updates the SKU capacity in 1,000 GB-per-day increments, and the change takes effect against future ingestion without disrupting linked workspaces. Lower commitments must satisfy the minimum 31-day reservation window.
Update the SKU capacity on cluster 'la-cluster-prod' from 1000 to 2000 GB/day and confirm the new provisioning state.
Agent-Driven Cluster Inventory
An AI agent through Jentic can enumerate Log Analytics clusters across subscriptions, identify clusters using platform-managed keys instead of customer-managed keys, and queue PATCH calls to bring them into compliance. Jentic returns the operation schema for each step, so the agent does not need to interpret the OperationalInsights provider docs.
List clusters in subscription '00000000-0000-0000-0000-000000000000', report any with no keyVaultProperties set, and patch each to attach the customer-managed key at 'https://kv-logs.vault.azure.net/keys/la-cmk'.
Key Endpoints
6 endpoints — jentic publishes the only available openapi specification for azure log analytics, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
PUT
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/clusters/{clusterName}
Create or update a Log Analytics cluster
PATCH
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/clusters/{clusterName}
Update SKU or key vault properties
GET
/subscriptions/{subscriptionId}/providers/Microsoft.OperationalInsights/clusters
List clusters across a subscription
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/clusters
List clusters in a resource group
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/clusters/{clusterName}
Get a specific cluster
DELETE
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/clusters/{clusterName}
Delete a cluster
PUT
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/clusters/{clusterName}
Create or update a Log Analytics cluster
PATCH
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/clusters/{clusterName}
Update SKU or key vault properties
GET
/subscriptions/{subscriptionId}/providers/Microsoft.OperationalInsights/clusters
List clusters across a subscription
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/clusters
List clusters in a resource group
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/clusters/{clusterName}
Get a specific cluster
DELETE
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/clusters/{clusterName}
Delete a cluster
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.
A
Azure Log Analytics
- Foundational (D-)42/100
73
Foundational Compliance63
Developer Experience & Jentic Compatibility20
AI-Readiness & Agent Experience94
Agent Usability35
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
73
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
92%
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).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
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.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
20
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
79%
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.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Microsoft.OperationalInsights cluster control plane by hand means registering an Azure AD app, acquiring bearer tokens for management.azure.com, and polling the 202 Azure-AsyncOperation responses that cluster provisioning and CMK attachment return. Through Jentic you install once, import Azure Log Analytics from the API Directory, store the Azure AD service principal credentials once, and your agent calls it.
Permission scoping
This provider puts the subscription, resource group, and cluster name in the URL path (/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/clusters/{clusterName}), so a rule can pin your agent to clusters in one resource group. You choose the operations it may call, so ones like deleting a cluster or patching its capacity SKU are not included unless you add them.
Credential isolation
Your Azure AD service principal credentials are stored once, encrypted, by your own Jentic One instance and injected as a bearer token scoped to management.azure.com at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create an Azure Log Analytics cluster' or 'attach a customer-managed key to a cluster', and Jentic returns the matching Microsoft.OperationalInsights operation with its input schema so the agent calls the right endpoint without interpreting the provider docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Azure Log Analytics API through Jentic.
Why is there no official OpenAPI spec for Azure Log Analytics?
Microsoft Azure does not publish a single consolidated OpenAPI specification for the OperationalInsights cluster control plane. Jentic generates and maintains this spec so that AI agents and developers can call Azure Log Analytics 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 Azure Log Analytics API use?
The API uses Azure Active Directory OAuth 2.0; agents acquire a token for the https://management.azure.com/ resource and pass it as a Bearer token. Jentic stores the service principal credentials in its vault and injects scoped tokens at call time, so client secrets never enter the agent context.
Can I run KQL queries against a workspace through this API?
No. This spec is the OperationalInsights cluster control plane - it provisions and manages dedicated clusters and their SKUs. To execute KQL queries you call the Log Analytics Query API at api.loganalytics.io/v1/workspaces/{workspaceId}/query, which is a separate data-plane endpoint.
How do I provision a Log Analytics cluster through Jentic?
Search Jentic for 'create a Log Analytics cluster', load the resulting PUT operation on /subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/clusters/{clusterName}, then execute it with the cluster name, location, and SKU capacity. Install with pip install jentic and run the async search-load-execute flow.
What is the minimum capacity reservation for a Log Analytics cluster?
Dedicated clusters require a minimum commitment tier of 1,000 GB per day, set via sku.capacity in the PUT or PATCH body. Capacity must be increased in 1,000 GB-per-day increments and is subject to a 31-day minimum reservation period.
What are the rate limits for this API?
Azure Resource Manager applies subscription-level throttling rather than per-endpoint limits - typically 12,000 reads and 1,200 writes per hour per subscription. Cluster operations are long-running and return 202 Accepted with an Azure-AsyncOperation header to poll.
Can I limit what my agent is allowed to do with the Azure Log Analytics API?
Yes. Because you run Jentic One yourself, your own rules decide which of the six cluster operations the agent may call, so read operations like listing or getting a cluster can be allowed while destructive ones such as deleting a cluster or patching its capacity SKU stay out unless you add them. Since this provider carries the subscription, resource group, and cluster name in the URL path, you can pin the agent to clusters in a single resource group. Credentials for your Azure AD service principal are held by your own instance and injected at call time, so the agent never sees them.
GET STARTED