canonical: https://jentic.com/apis/azure.com/azure-log-analytics-operations-management # Microsoft Azure Azure Log Analytics - Operations Management 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. ## For AI 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. ## Scope Does not query workspace data, manage clusters, or configure alerts - use for Operations Management Solution lifecycle and ARM associations only. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **Solutions** — Install, list, get, and delete Operations Management Solutions on a workspace - **ManagementAssociations** — Link solutions to parent ARM resources and list those links - **ManagementConfigurations** — Manage ARM template configurations bundled with a solution - **Operations** — Enumerate Microsoft.OperationsManagement Resource Provider operations ## Why Jentic - **Setup:** Wiring the Microsoft.OperationsManagement resource provider by hand means registering an Azure AD app, acquiring bearer tokens for management.azure.com, resolving OMS gallery plan publisher and product values, and polling the 202 Azure-AsyncOperation responses that solution installs return. Through Jentic you install once, import Azure Log Analytics - Operations Management 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 solution name in the URL path (/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationsManagement/solutions/{solutionName}), so a rule can pin your agent to solutions in one resource group. You choose the operations it may call, so ones like deleting a solution or creating a ManagementAssociation 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 'install an Operations Management solution on a Log Analytics workspace' or 'list management associations', and Jentic returns the matching Microsoft.OperationsManagement operation with its input schema so the agent calls the right endpoint without browsing the provider reference. ## Related APIs - **Azure Log Analytics** — Manages the dedicated Log Analytics clusters that host the workspaces solutions are installed onto. - **Azure Monitor Management Client** — Configure metric alerts, action groups, and diagnostic settings against the workspace once solutions are installed. - **Azure Log Analytics Query Packs** — Manage saved KQL queries that target the data each Operations Management Solution writes to a workspace. ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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. ### Can I limit what my agent is allowed to do with the Azure Log Analytics - Operations Management API? Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and this provider carries the subscription, resource group, and solution name in the URL path, so you can pin the agent to solutions in a single resource group. You also choose exactly which operations it may call, so destructive ones like deleting a solution or creating a ManagementAssociation are not available to the agent unless you add them. Read-only work such as listing installed solutions can be permitted while write and delete calls stay excluded.