Microsoft Azure AutomationManagementClient

Name: AutomationManagementClient API
Brand: AutomationManagementClient
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi Cdoauth26 EndpointsREST

For Agents

Create and manage webhooks that trigger Azure Automation runbooks from external systems, callable by an AI agent.

Install Jentic One Beta

Connect the AutomationManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AutomationManagementClient, 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 AutomationManagementClient API.

List all webhooks attached to a specific Automation account

Generate the unique webhook URI used to invoke a runbook

Create a webhook bound to a runbook with optional parameter defaults

GET STARTED

Start building with AutomationManagementClient API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use AutomationManagementClient API for, with concrete tasks.

★ Event-Driven Runbook Triggering

Operations teams want their monitoring tools, CI systems, or custom apps to trigger an Azure Automation runbook on specific events. Generating a webhook URI and creating the webhook resource produces a single-use HTTPS endpoint that, when POSTed to, starts the bound runbook. Webhook URIs are returned only at creation time and cannot be retrieved later, so they must be captured and stored securely.

POST /webhooks/generateUri to get a fresh URI, then PUT a webhook resource with that URI bound to the target runbook, and securely capture the URI in the response.

Webhook Lifecycle Hygiene

Security policies require webhooks to expire and be rotated periodically. Listing webhooks per account, filtering by expiryTime, and PATCHing the expiryTime forward (or deleting and recreating) keeps the webhook estate aligned with policy. Disabled webhooks reject incoming POSTs but preserve the resource for audit.

List webhooks, identify those expiring within 30 days, and either PATCH the expiryTime or DELETE and recreate based on the rotation policy.

Abuse Response

If a webhook URI is leaked, the fastest mitigation is to disable or delete the webhook. PATCHing isEnabled to false stops the runbook from being invoked while preserving the resource for incident review; DELETE removes it entirely. Both calls take effect immediately at the control plane.

PATCH the affected webhook with isEnabled=false to stop incoming invocations, then GET to confirm the disabled state, and decide whether to DELETE.

Agent-Driven Webhook Provisioning via Jentic

An AI agent setting up an event-driven workflow can use Jentic to create a runbook webhook on demand, capture the returned URI, and pass it to the upstream event source — all without holding the Automation account credentials in its context. Jentic returns the schemas for both the URI generation and webhook creation calls.

Search Jentic for 'create an Azure Automation runbook webhook', execute the generateUri POST followed by the webhook PUT, and return the URI for the agent to relay to the event source.

Key Endpoints

6 endpoints — automationmanagementclient is the azure resource manager api for managing webhooks attached to azure automation runbooks.

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/webhooks

List all webhooks on an Automation account

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/webhooks/generateUri

Generate a unique webhook URI

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/webhooks/{webhookName}

Create or update a webhook bound to a runbook

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/webhooks/{webhookName}

Retrieve a webhook resource

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/webhooks/{webhookName}

Delete a webhook

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/webhooks

List all webhooks on an Automation account

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/webhooks/generateUri

Generate a unique webhook URI

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/webhooks/{webhookName}

Create or update a webhook bound to a runbook

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/webhooks/{webhookName}

Retrieve a webhook resource

Why Jentic?

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

Credential isolation

AAD bearer tokens are vaulted in Jentic. Webhook URIs returned at PUT time are passed back to the agent in the response and not retained by Jentic, so the agent decides where to relay them.

Intent-based discovery

Agents search by intent ('create a runbook webhook') and Jentic returns the two-step schema (generateUri then PUT webhook) so the agent does not have to discover the order from the spec.

Time to first call

Direct integration: a few hours for AAD setup and the two-step URI dance. Through Jentic: under 30 minutes — search, load, execute.

FAQs

Specific to using AutomationManagementClient API through Jentic.

What authentication does the AutomationManagementClient use?

Azure Active Directory OAuth 2.0 bearer tokens scoped to https://management.azure.com/. Through Jentic the token is held in the encrypted vault and a scoped session is supplied at call time.

Can I create a webhook for a runbook with this API?

Yes. POST to /webhooks/generateUri first to receive a single-disclosure URI, then PUT /webhooks/{webhookName} with the URI, runbook reference, expiry time, and any default parameter values. The URI is only returned at this PUT and cannot be retrieved later, so capture and store it immediately.

What are the rate limits for the AutomationManagementClient?

Calls go through Azure Resource Manager and follow ARM throttling — typically 12,000 reads and 1,200 writes per hour per subscription. Webhook management is low-frequency in normal use; rate limits are unlikely to be a constraint.

How do I rotate a runbook webhook through Jentic?

Search Jentic for 'rotate Azure Automation webhook'. Jentic returns the schemas for the generateUri POST, the webhook PUT, and the DELETE. Execute generateUri, create a new webhook with the fresh URI, switch the upstream caller to the new URI, then DELETE the old webhook.

Is the AutomationManagementClient free?

Webhook management calls do not have a per-request charge. Runbook job execution triggered by the webhook is billed under the parent Automation account's SKU (Free monthly minutes plus per-minute Basic billing above the allowance).

What happens when a webhook expires?

Once expiryTime passes, POSTs to the webhook URI are rejected with HTTP 401, and the runbook does not start. The webhook resource itself remains visible via GET so you can audit when it expired; PATCHing expiryTime forward reactivates it without changing the URI.

Microsoft Azure AutomationManagementClient

Connect the AutomationManagementClient to your agent

Capabilities

Start building with AutomationManagementClient API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs