Microsoft Azure Microsoft Insights
Browse all Azure APIs44
AI ReadinessFoundational (D)44/100
Agent-ready OpenAPI document · curated by JenticDeveloper ToolsMonitoring Observabilityoauth26 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage Azure Monitor scheduled query rules: create log-based alerts that run KQL queries on a cadence, list existing rules, and update or delete them. Useful for log-driven alerting automation.
Use for: I need to create a log-based alert on failed sign-ins, List all scheduled query rules in this subscription, Update the threshold on an existing log alert, Delete a noisy scheduled query rule
Not supported: Does not run KQL queries directly, manage action groups, or evaluate metric alerts - use for managing scheduled query rule definitions only.
Jentic publishes the only available OpenAPI specification for Microsoft Insights, keeping it validated and agent-ready. This Azure Monitor surface manages Scheduled Query Rules, the alert rules that run a Kusto query on a Log Analytics workspace at a defined cadence and trigger actions when a threshold is met. Use it to create, list, retrieve, update, and delete scheduled query rules across a subscription or a single resource group. Authentication is via Azure Active Directory OAuth 2.0 on Azure Resource Manager.
Install Jentic One Beta
Connect the Microsoft Insights to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Microsoft Insights, 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-microsoft-insights" | 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-microsoft-insights" | 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 Microsoft Insights API.
Create or update a scheduled query rule that runs a KQL query against Log Analytics on a defined cadence
List every scheduled query rule in a subscription to inventory log-based alerts
List scheduled query rules within a single resource group for environment-level reviews
Retrieve a single scheduled query rule by name to inspect its query, schedule, and action group
Update an existing scheduled query rule to change its query, severity, or action group
Delete a scheduled query rule that is no longer needed
Use Cases
Patterns agents use Microsoft Insights API for, with concrete tasks.
★ Codify log-based alerts as scheduled query rules
Operations teams use the API to define log-based alerts in version control and apply them through CI rather than clicking through the Azure portal. Each rule pairs a KQL query with a schedule, severity, threshold, and action group, and a single PUT call applies or updates the rule. The same definition can be reused across environments by templating the workspace ID and action group ID.
PUT /subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/microsoft.insights/scheduledQueryRules/{ruleName} with the KQL query, schedule, action, and severity in the body.
Audit log alert coverage
Reliability teams query the subscription-scoped list endpoint to inventory every scheduled query rule and confirm critical workloads have alerts in place. The output drives gap analysis: a workload missing alerts on its core failure metrics gets new rules, while duplicated or noisy rules are flagged for cleanup or merging.
GET /subscriptions/{subscriptionId}/providers/microsoft.insights/scheduledQueryRules and emit a report grouping rules by source resource and severity.
Tune alert thresholds in response to noise
When a scheduled query rule fires too often, the team adjusts the threshold or query window without recreating the rule. PATCH on the rule path updates the body in place, preserving the rule ID and history. Combine with the GET endpoint to read the current threshold before computing the new value.
GET the rule, compute a new threshold based on the past week's evaluation history, then PATCH /subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/microsoft.insights/scheduledQueryRules/{ruleName} with the updated trigger condition.
Agent-driven alert deployment
Through Jentic, an AI agent can read an SLO definition, infer the right KQL query and threshold, and create the corresponding scheduled query rule automatically. The agent searches Jentic for 'create azure log alert', loads the input schema, and executes with the workspace ID and action group ID. Jentic injects the Azure AD bearer token at execution time so the agent never sees raw secrets.
Use Jentic search 'create azure scheduled query rule', load ScheduledQueryRules_CreateOrUpdate, supply the source workspace, KQL query, and action group, and execute.
Key Endpoints
6 endpoints — jentic publishes the only available openapi specification for microsoft insights, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
PUT
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/microsoft.insights/scheduledQueryRules/{ruleName}
Create or update a scheduled query rule
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/microsoft.insights/scheduledQueryRules/{ruleName}
Get a scheduled query rule
PATCH
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/microsoft.insights/scheduledQueryRules/{ruleName}
Update a scheduled query rule
DELETE
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/microsoft.insights/scheduledQueryRules/{ruleName}
Delete a scheduled query rule
GET
/subscriptions/{subscriptionId}/providers/microsoft.insights/scheduledQueryRules
List rules in a subscription
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/microsoft.insights/scheduledQueryRules
List rules in a resource group
PUT
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/microsoft.insights/scheduledQueryRules/{ruleName}
Create or update a scheduled query rule
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/microsoft.insights/scheduledQueryRules/{ruleName}
Get a scheduled query rule
PATCH
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/microsoft.insights/scheduledQueryRules/{ruleName}
Update a scheduled query rule
DELETE
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/microsoft.insights/scheduledQueryRules/{ruleName}
Delete a scheduled query rule
GET
/subscriptions/{subscriptionId}/providers/microsoft.insights/scheduledQueryRules
List rules in a subscription
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/microsoft.insights/scheduledQueryRules
List rules in a resource group
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.
M
Microsoft Insights
- Foundational (D)44/100
72
Foundational Compliance63
Developer Experience & Jentic Compatibility21
AI-Readiness & Agent Experience94
Agent Usability35
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
72
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
88%
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.
21
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
86%
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 Microsoft Insights scheduled query rules by hand means implementing Azure AD OAuth 2.0, minting an ARM-scoped bearer token for management.azure.com, modelling the rule body with its KQL query and trigger condition, and handling PATCH semantics and ARM throttling yourself. Through Jentic you install once, import Microsoft Insights from the API Directory, store the Azure AD credential once, and your agent calls it.
Permission scoping
The API puts the subscription, resource group, and rule name in the URL path, so a rule can pin your agent to reading and updating scheduled query rules in one resource group and nothing else. You choose the operations it may call, so destructive ones like deleting a scheduled query rule are not included unless you add them.
Credential isolation
Your Azure AD credential is stored once, encrypted, by your own Jentic One instance and exchanged for a short-lived ARM-scoped bearer token at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create an Azure log analytics scheduled query rule' or 'update an Azure log alert threshold', and Jentic returns the matching ScheduledQueryRules operation with its input schema, including trigger conditions and action groups, so the agent executes the right call.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Microsoft Insights API through Jentic.
Why is there no official OpenAPI spec for Microsoft Insights scheduled query rules?
Microsoft Azure does not publish a standalone OpenAPI specification for the scheduled query rules surface of Azure Monitor. Jentic generates and maintains this spec so that AI agents and developers can call Microsoft Insights 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 Microsoft Insights API use?
The API uses Azure Active Directory OAuth 2.0 via the azure_auth scheme on https://management.azure.com/. Through Jentic, your Azure AD application credentials are stored encrypted in your Jentic One instance and exchanged for a short-lived bearer token at execution time.
Can I create a log-based alert with this API?
Yes. Call PUT /subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/microsoft.insights/scheduledQueryRules/{ruleName} with the source workspace, KQL query, schedule, action group, and trigger condition in the body. The rule begins evaluating on the configured cadence as soon as it is created.
What are the rate limits for the scheduled query rules API?
The endpoints inherit standard Azure Resource Manager throttle quotas, surfaced through x-ms-ratelimit-remaining-* response headers. Bulk creation should respect those headers and back off when remaining quota approaches zero.
How do I update an existing rule through Jentic?
Search Jentic for 'update azure scheduled query rule', load ScheduledQueryRules_Update, supply the rule name and the changed properties (such as a new threshold or query) in the body, and execute. PATCH semantics mean unspecified properties remain untouched.
Can the same rule run against multiple workspaces?
No. Each scheduled query rule references a single source resource ID, typically a Log Analytics workspace or an Application Insights resource. To alert across multiple workspaces, create one rule per workspace or use a cross-workspace KQL query against a single workspace that has read access to the others.
Does deleting a rule remove past alert history?
DELETE on a rule removes the rule definition and stops future evaluations. Historic alert instances and their state remain in Azure Monitor's alerts subsystem for the configured retention period and can still be queried through the alerts management API.
Can I limit what my agent is allowed to do with the Microsoft Insights API?
Yes. Jentic One is self-hosted, so your own rules decide which scheduled query rule operations the agent may call and which Azure AD credential it uses. Because the subscription, resource group, and rule name live in the request path, you can pin the agent to listing, reading, and updating scheduled query rules in a single resource group and nothing else. Destructive operations, such as deleting a scheduled query rule, are only available to the agent if you explicitly include them.
GET STARTED