Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Developer Tools / Azure / AutomationManagementClient
AutomationManagementClient logo

Microsoft Azure AutomationManagementClient

Browse all Azure APIs
40
AI ReadinessNon-Ready (F)40/100
See full scorecard
Community OpenAPI document · agent-readyDeveloper ToolsCi Cdoauth26 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: I need to create a webhook that triggers my deployment runbook, Generate a fresh webhook URI for an Automation runbook, List all webhooks on my Automation account, Disable a webhook that is being abused

Not supported: Does not author runbooks, execute jobs, or manage Automation account billing - use for runbook webhook lifecycle management only.

AutomationManagementClient is the Azure Resource Manager API for managing webhooks attached to Azure Automation runbooks. It supports listing, creating, updating, and deleting webhooks, plus generating the unique webhook URI used to trigger a runbook from an external system. Use this client to wire runbooks into webhook-driven event sources such as monitoring tools, custom apps, or third-party CI systems.

Jentic One on GithubView OpenAPI Document

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.

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%2Fautomationmanagementclient" | sh
2

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%2Fautomationmanagementclient" | 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

Update a webhook's name, expiry, or enabled state

Delete a webhook to revoke external invocation access

Retrieve a single webhook's metadata for inspection

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

DELETE

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

Delete a webhook

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.

A

AutomationManagementClient

- Non-Ready (F)
40/100
73
Foundational Compliance
63
Developer Experience & Jentic Compatibility
18
AI-Readiness & Agent Experience
94
Agent Usability
35
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
73

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
91%

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.

18

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
71%

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.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring AutomationManagementClient by hand means registering an Azure AD app, exchanging OAuth 2.0 tokens for management.azure.com, and learning the two-step webhook dance where you generate a URI and then bind it before Azure Resource Manager throttling and retries get in the way. Through Jentic you install once, import AutomationManagementClient from the API Directory, store the Azure AD credential once, and your agent calls it.

Permission scoping

This client puts the subscription, resource group, automation account, and webhook name in the URL path (for example /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/webhooks/{webhookName}), so a rule can pin your agent to one account's webhooks. You choose the operations it may call, so ones like deleting a webhook or generating a fresh invocation URI are not included unless you add them.

Credential isolation

Your Azure AD credential 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 'create a runbook webhook' or 'rotate an Azure Automation webhook', and Jentic returns the ordered schema (generateUri then the webhook PUT) so the agent does not have to infer the two-step sequence from the spec.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Automation Management

→

Provision the parent Automation account that hosts these webhooks

Use Automation Management to create the account first; use this client to wire webhooks to its runbooks.

Complementary

Monitor Management Client

→

Configure Azure Monitor action groups that POST to runbook webhooks

Pair when the agent wants alerts to invoke a runbook via the webhook URI created here.

Complementary

Authorization Management Client

→

Grant RBAC roles on the Automation account that controls webhook management

Use Authorization Management to scope who can create or delete webhooks on the account.

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.

Can I limit what my agent is allowed to do with the Azure Automation Webhooks API?

Yes. Because you run Jentic One yourself, you write the rules that decide which operations and credentials the agent may use. Since this API carries the subscription, resource group, automation account, and webhook name in the URL path, you can pin the agent to a single Automation account's webhooks and grant only the calls you want, such as listing webhooks or retrieving one for inspection. Higher-impact operations like generating a fresh invocation URI, creating or updating a webhook, or deleting one stay out of the agent's reach until you explicitly add them.

GET STARTED

Start building with AutomationManagementClient API

Explore with Jentic One
View OpenAPI Document