Microsoft Azure WorkbookClient

Name: WorkbookClient API
Brand: WorkbookClient
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsBusiness Intelligenceoauth21 EndpointsREST

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.

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 | sh

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 instance

Jentic 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

GET STARTED

Start building with WorkbookClient API

Explore with Jentic

View OpenAPI Document

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.

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Azure AD OAuth tokens for `azure_auth` are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped, short-lived bearer tokens — refresh tokens and client secrets never enter the agent context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'list azure insights operations') and Jentic returns the matching Operations_List call with its full input schema, so the agent can fetch the catalogue without reading Microsoft docs.

Time to first call

Direct integration: under an hour given the single endpoint, but Azure AD auth still has to be wired up. Through Jentic: a few minutes — search, load schema, execute.

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.