Microsoft Azure WorkbookClient
Browse all Azure APIs45
AI ReadinessFoundational (D)45/100
Community OpenAPI document · agent-readyAnalyticsBusiness Intelligenceoauth21 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
List the available Microsoft.Insights operations to support tooling that wraps Azure Monitor Workbooks and Insights APIs.
Use for: List available Microsoft Insights operations, Discover what Azure Monitor Workbooks operations are available, Get the operations catalogue for Microsoft.Insights, Find which Insights operations are supported in this preview API
Not supported: Does not create, update, or render Azure Monitor Workbooks - use only for listing the available Microsoft.Insights REST operations.
The Azure WorkbookClient API exposes the operations metadata for Azure Monitor Workbooks under the Microsoft.Insights provider. This 2018-06-17 preview slice contains a single operation, Operations_List, that enumerates the available REST API operations for Insights. Use it to discover supported actions and as a discovery surface for tooling that wraps the broader Insights and Workbooks ecosystem.
Install Jentic One Beta
Connect the WorkbookClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the WorkbookClient, 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%2Fworkbookclient" | 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%2Fworkbookclient" | 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 WorkbookClient API.
Enumerate available Microsoft.Insights REST operations to power discovery surfaces
Surface Insights operation metadata to tooling that builds dynamic UIs
Verify which Workbooks-related operations are exposed in the 2018-06-17 preview surface
Feed operation metadata into agent tool registries that wrap Azure Monitor
Use Cases
Patterns agents use WorkbookClient API for, with concrete tasks.
★ Discovery for tooling that wraps Azure Monitor
Build tooling that needs to render the full list of available Microsoft.Insights operations - for example a dynamic command palette or a tool registry. The Operations_List endpoint returns the catalogue so the tool surface stays in sync with what Azure exposes, instead of hard-coding operation names.
Call GET /providers/Microsoft.Insights/operations and emit the returned operation names as a JSON list.
Validate Workbook tooling against the preview API
When integrating against the 2018-06-17 preview Workbook surface, list operations to confirm what is actually exposed before relying on specific calls in production code. This makes it possible to fail fast in CI when an expected operation is missing from the spec.
List Microsoft.Insights operations and assert that the response contains an operation matching 'workbook' before continuing the deployment.
Agent-driven operation discovery
Let an AI agent ask 'which Azure Monitor operations are available?' and receive a structured answer pulled live from the Insights provider. Jentic exposes this single operation as an agent tool so discovery becomes a one-call workflow rather than reading documentation.
Search Jentic for 'list azure insights operations', load the schema, execute it, and summarise the operation names back to the user.
Key Endpoints
1 endpoints — the azure workbookclient api exposes the operations metadata for azure monitor workbooks under the microsoft.
METHOD
PATH
DESCRIPTION
GET
/providers/Microsoft.Insights/operations
Lists all available Microsoft.Insights REST operations
GET
/providers/Microsoft.Insights/operations
Lists all available Microsoft.Insights REST operations
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.
W
WorkbookClient
- Foundational (D)45/100
100
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
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
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
Listing Microsoft.Insights operations by hand means acquiring Azure Active Directory OAuth 2.0 tokens, targeting the management.azure.com ARM control plane, and constructing the provider operations request yourself. Through Jentic you install once, import Workbook Client from the API Directory, store the Azure AD credential once, and your agent calls it.
Permission scoping
This API exposes a single read operation, a GET on /providers/Microsoft.Insights/operations, so the agent can only list the available Microsoft.Insights REST operations and cannot create, update, or delete anything. Limit the agent to that operation, which is the only one on the surface.
Credential isolation
Your Azure AD token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list available Azure Insights operations', and Jentic returns the Operations_List call with its input schema so the agent fetches the operation list without reading Microsoft docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using WorkbookClient API through Jentic.
What authentication does the WorkbookClient API use?
The API uses Azure Active Directory OAuth 2.0 via the implicit flow scheme `azure_auth`, scoped to user_impersonation against https://management.azure.com. Through Jentic the OAuth token stays in the vault and only short-lived scoped bearer tokens are exposed to the agent.
What operations does this API actually expose?
Just one: GET /providers/Microsoft.Insights/operations (Operations_List). It returns the catalogue of available Microsoft.Insights REST operations. Workbook CRUD itself is not part of this 2018-06-17 preview slice.
What are the rate limits for this API?
The spec does not declare explicit rate limits. Calls go through Azure Resource Manager, which applies standard ARM throttling per subscription. Inspect the x-ms-ratelimit-remaining-subscription-reads response header to see remaining quota.
How do I list Insights operations through Jentic?
Search Jentic for 'list azure insights operations', load the schema for GET /providers/Microsoft.Insights/operations, and execute it. Install with `pip install jentic` and use the async search/load/execute pattern.
Can I create or update a workbook with this API?
No. This 2018-06-17 preview surface only lists operations. To create, update, or share Azure Monitor Workbooks you need a different API surface - typically a newer applicationinsightsmanagementclient or monitormanagementclient version.
Is this API stable for production use?
It is a 2018-06-17 preview release. Treat it as a discovery aid for tooling rather than a production dependency, and prefer GA-stable Azure Monitor or Application Insights APIs when building runtime workflows.
Can I limit what my agent is allowed to do with the Microsoft Azure Workbook API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent can use, and this API surfaces only a single read call: GET /providers/Microsoft.Insights/operations, which lists the available Microsoft.Insights REST operations. You can scope the agent to just that Operations_List call, so it can enumerate the operations catalogue but cannot create, update, or delete anything. Your Azure AD credential stays with your Jentic One instance and is injected only when that permitted operation runs.
GET STARTED