canonical: https://jentic.com/apis/azure.com/azure-log-analytics # Microsoft Azure Azure Log Analytics 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. ## For AI 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. ## Scope Does not run KQL queries, manage workspaces, or ingest logs - use for Log Analytics cluster provisioning, sizing, and CMK configuration only. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **Clusters** — Create, read, update, delete, and list dedicated Log Analytics clusters - **SKU and capacity** — Manage capacity reservation tiers attached to a cluster - **Key vault properties** — Configure customer-managed keys for cluster-level encryption ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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 - **Azure Log Analytics Query Packs** — Manage saved KQL queries inside Query Packs that target workspaces hosted on this cluster. - **Azure Log Analytics - Operations Management** — Install Operations Management solutions on Log Analytics workspaces backed by this cluster. - **Azure Monitor Management Client** — Manages metrics, alerts, and diagnostic settings - a wider Monitor surface than just OperationalInsights clusters. ## FAQ ### 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.