Microsoft Azure Azure Log Analytics - Operations Management
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilityoauth215 EndpointsREST
For Agents
Install, list, and remove Operations Management Solutions on Azure Log Analytics workspaces, and manage the ManagementAssociation and ManagementConfiguration records that link solutions to ARM resources.
Use for: I need to install the Updates solution on a Log Analytics workspace, List all Operations Management solutions in my subscription, Remove a solution from a Log Analytics workspace, Create a ManagementAssociation between a solution and a VM
Not supported: Does not query workspace data, manage clusters, or configure alerts — use for Operations Management Solution lifecycle and ARM associations only.
Jentic publishes the only available OpenAPI specification for Azure Log Analytics - Operations Management, keeping it validated and agent-ready. This API manages Operations Management Solutions and their associated configuration objects in the Microsoft.OperationsManagement namespace, letting operators install, list, update, and remove solutions like Updates, AzureActivity, or Security on a Log Analytics workspace. It also exposes ManagementAssociations and ManagementConfigurations for binding solutions to ARM resources. All requests authenticate with Azure AD OAuth 2.0 against Azure Resource Manager.
Install Jentic One Beta
Connect the Azure Log Analytics - Operations Management to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Azure Log Analytics - Operations Management, 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 Azure Log Analytics - Operations Management API.
Install an Operations Management Solution onto a Log Analytics workspace
List solutions installed across a subscription or scoped to a resource group
Delete a solution and clean up its associated resources
Create a ManagementAssociation that links a solution to a parent ARM resource
Manage ManagementConfiguration ARM templates that ship with a solution
Enumerate Microsoft.OperationsManagement Resource Provider operations for RBAC tooling
Use Cases
Patterns agents use Azure Log Analytics - Operations Management API for, with concrete tasks.
★ Bulk Solution Deployment Across Workspaces
Platform teams standardise telemetry collection by installing the same set of Operations Management Solutions on every Log Analytics workspace in an environment. The PUT call on solutions accepts a plan with the publisher, product, and workspace resource ID, and returns the solution record once Resource Manager finishes provisioning. Pair listing with idempotent PUT to bring drifted workspaces back into compliance.
Install the OMSGallery/Updates solution onto Log Analytics workspace 'la-prod-eu' in resource group 'rg-observability' and confirm provisioningState=Succeeded.
Solution Lifecycle Cleanup
When a workspace is decommissioned or a solution becomes redundant, the DELETE endpoint on a solution removes both the solution record and its ManagementAssociations. This is the supported clean removal path; deleting the workspace alone leaves orphaned ARM resources behind that the Resource Provider tracks.
Delete the 'AzureActivity(la-old)' solution from resource group 'rg-old' and verify no ManagementAssociations remain.
ManagementAssociation Auditing
ManagementAssociations link solutions to parent ARM resources such as virtual machines or Automation accounts, and they accumulate as solutions are installed and reinstalled. The GET on /providers/Microsoft.OperationsManagement/ManagementAssociations enumerates every association in a subscription, which lets a platform team detect dangling links to deleted parents and remove them.
List all ManagementAssociations in subscription '00000000-0000-0000-0000-000000000000' and report any whose parent resource ID returns 404.
Agent-Driven Compliance Enforcement
An AI agent through Jentic can enumerate Log Analytics workspaces, check whether a required baseline of Operations Management Solutions is installed, and PUT any missing solutions in one pass. Jentic returns the operation schema for each call so the agent never browses the OperationsManagement provider docs.
For each workspace in subscription '00000000-0000-0000-0000-000000000000', ensure the Updates and AzureActivity solutions are installed; install any that are missing.
Key Endpoints
15 endpoints — jentic publishes the only available openapi specification for azure log analytics - operations management, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
PUT
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationsManagement/solutions/{solutionName}
Install or update a solution on a workspace
GET
/subscriptions/{subscriptionId}/providers/Microsoft.OperationsManagement/solutions
List solutions in a subscription
DELETE
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationsManagement/solutions/{solutionName}
Delete a solution
PUT
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/{providerName}/{resourceType}/{resourceName}/providers/Microsoft.OperationsManagement/ManagementAssociations/{managementAssociationName}
Create a ManagementAssociation under a parent resource
PUT
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationsManagement/ManagementConfigurations/{managementConfigurationName}
Create or update a ManagementConfiguration
GET
/providers/Microsoft.OperationsManagement/operations
List Resource Provider operations
PUT
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationsManagement/solutions/{solutionName}
Install or update a solution on a workspace
GET
/subscriptions/{subscriptionId}/providers/Microsoft.OperationsManagement/solutions
List solutions in a subscription
DELETE
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationsManagement/solutions/{solutionName}
Delete a solution
PUT
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/{providerName}/{resourceType}/{resourceName}/providers/Microsoft.OperationsManagement/ManagementAssociations/{managementAssociationName}
Create a ManagementAssociation under a parent resource
PUT
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationsManagement/ManagementConfigurations/{managementConfigurationName}
Create or update a ManagementConfiguration
GET
/providers/Microsoft.OperationsManagement/operations
List Resource Provider operations
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD service principal credentials are stored encrypted in the Jentic vault. Agents receive short-lived Bearer tokens scoped to https://management.azure.com/ — client secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'install an Operations Management solution') and Jentic returns the matching Microsoft.OperationsManagement operation with its parameter schema.
Time to first call
Direct integration: 1-2 days for Azure AD app setup, async polling, and gallery plan resolution. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Azure Log Analytics - Operations Management API through Jentic.
Why is there no official OpenAPI spec for Azure Log Analytics - Operations Management?
Microsoft Azure does not publish a single consolidated OpenAPI specification for the Microsoft.OperationsManagement Resource Provider. Jentic generates and maintains this spec so that AI agents and developers can call Azure Log Analytics - Operations Management 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?
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.
Can I install any solution from the OMS Gallery with this API?
Yes — the PUT on /subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationsManagement/solutions/{solutionName} accepts a plan block whose publisher and product fields identify the gallery solution, e.g., publisher 'Microsoft' and product 'OMSGallery/Updates'. The Resource Provider validates the plan against available gallery entries.
How do I install a solution through Jentic?
Search Jentic for 'install an Operations Management solution', load the resulting PUT operation on the solutions resource, and execute it with the workspace resource ID and the gallery plan. Install with pip install jentic and run the async search-load-execute flow.
What is the difference between a solution and a ManagementAssociation?
A solution is the deployed package on a workspace (e.g., Updates, AzureActivity); a ManagementAssociation links that solution to a parent ARM resource such as a VM or Automation account. Solutions are managed under /providers/Microsoft.OperationsManagement/solutions, while associations are nested under the parent resource path.
What are the rate limits for this API?
Azure Resource Manager applies subscription-level throttling — typically 12,000 reads and 1,200 writes per hour per subscription. Solution PUTs are long-running and return 202 with an Azure-AsyncOperation header for polling.
GET STARTED