SchedulerManagementClient

Name: SchedulerManagementClient API
Brand: SchedulerManagementClient
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityTask Managementoauth215 EndpointsREST

For Agents

Manage Azure Scheduler job collections and the recurring jobs that fire HTTP, queue, service bus, and webhook actions, with on-demand run and execution history.

Connect the SchedulerManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SchedulerManagementClient, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

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

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 SchedulerManagementClient API.

Create or update a job collection that groups recurring jobs and sets quota tier

Define a job with an HTTP, queue, service bus, or webhook action and a recurrence rule

Trigger a one-off run of an existing job without waiting for its next schedule

Enable or disable an entire job collection in a single call

GET STARTED

Start building with SchedulerManagementClient API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for SchedulerManagementClient, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for SchedulerManagementClient, keeping it validated and agent-ready. The Azure Scheduler API manages job collections and the recurring jobs they contain, letting agents define HTTP, storage queue, service bus, or webhook actions to fire on a cron-like schedule. Job collections gate quota and pricing tier, while individual jobs hold the action, recurrence, and retry policy. Agents can enable, disable, run on-demand, and inspect history for any job in the collection.

Use Cases

Patterns agents use SchedulerManagementClient API for, with concrete tasks.

★ Recurring HTTP Webhook Triggering

Teams replacing custom cron servers use Azure Scheduler to fire HTTP requests against internal services on a recurrence. The job action holds the request URL, method, headers, and body, and the recurrence rule supports minute, hour, day, week, and month intervals. The PUT job endpoint creates or updates the job in-place and the run endpoint allows on-demand testing without waiting for the next tick.

PUT a job named nightly-report under jobCollection ops with action.request.uri set to https://internal/api/report and recurrence set to {frequency: Day, interval: 1}

Queue and Service Bus Fan-Out

Workflow engineers use Scheduler jobs to push messages onto Azure Storage queues or Service Bus topics on a regular cadence, kicking off downstream pipelines. The job action type covers both transports, and the recurrence rule supports complex schedules including time zones. Execution history records whether the message was successfully delivered.

PUT a job that pushes a message onto a Storage Queue every 15 minutes and inspect the history endpoint to confirm three successful deliveries

Maintenance Window Job Suspension

During an upgrade, operators disable an entire job collection so no scheduled runs fire while a downstream system is unavailable. The disable POST suspends every job in the collection at once, and a matching enable resumes them without recreating any jobs. This is faster and safer than deleting jobs and re-importing them after the maintenance window.

POST disable on jobCollections/payments-jobs and after maintenance POST enable on the same collection to resume all jobs

Agent-Driven Scheduled Workflow Setup via Jentic

Through Jentic, an automation agent can search for create scheduled job, load the PUT job schema for the matching action type, populate it from a natural language request, and execute the call with a managed Azure OAuth token. The same flow lets the agent inspect history or fire a one-off run when a user wants to verify the job works end-to-end.

Search Jentic for create scheduled http job, load the job PUT schema, execute it with a request body that posts to a Slack webhook every weekday at 09:00, and confirm via GET history after the first scheduled fire

Key Endpoints

15 endpoints — jentic publishes the only available openapi specification for schedulermanagementclient, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Scheduler/jobCollections/{jobCollectionName}

Create or update a job collection

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Scheduler/jobCollections/{jobCollectionName}/jobs/{jobName}

Create or update a job

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Scheduler/jobCollections/{jobCollectionName}/jobs/{jobName}/run

Run a job on demand

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Scheduler/jobCollections/{jobCollectionName}/jobs/{jobName}/history

Get job execution history

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Scheduler/jobCollections/{jobCollectionName}/disable

Disable a job collection

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Scheduler/jobCollections/{jobCollectionName}/enable

Enable a job collection

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Scheduler/jobCollections/{jobCollectionName}

Create or update a job collection

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Scheduler/jobCollections/{jobCollectionName}/jobs/{jobName}

Create or update a job

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Scheduler/jobCollections/{jobCollectionName}/jobs/{jobName}/run

Run a job on demand

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Scheduler/jobCollections/{jobCollectionName}/jobs/{jobName}/history

Get job execution history

POST

Why though Jentic?

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

Credential isolation

Azure service principal credentials are stored encrypted in the Jentic vault. Agents receive scoped OAuth tokens for the management.azure.com audience only — the underlying client secret never enters the agent context.

Intent-based discovery

Agents search by intent such as create scheduled job or trigger recurring webhook, and Jentic returns the matching SchedulerManagementClient operation with its full input schema covering job collection, job, action, and recurrence shape.

Time to first call

Direct integration: 1-2 days to wire MSAL and the action-type-specific request shapes. Through Jentic: under an hour to search, load, and execute a job creation.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Azure AutomationManagementClient

Multi-step orchestrated runbooks rather than single-action recurring jobs

Choose when scheduled work needs branching, variables, or multiple connected steps

Alternative

Azure LogicManagementClient

Visual workflow with rich connectors triggered on a schedule

Choose when a schedule triggers a multi-connector workflow rather than a single HTTP or queue action

Complementary

Azure ResourceManagementClient

Provisions the resource group that holds Scheduler job collections

Use first to create or select the resource group where the job collection will live

FAQs

Specific to using SchedulerManagementClient API through Jentic.

Why is there no official OpenAPI spec for SchedulerManagementClient?

Microsoft Azure does not publish a unified OpenAPI specification for the Scheduler control plane. Jentic generates and maintains this spec so that AI agents and developers can call SchedulerManagementClient via structured tooling. It is validated against the live Azure Resource Manager API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does SchedulerManagementClient use?

Like all Azure Resource Manager APIs, it requires Azure Active Directory OAuth 2.0. Acquire a bearer token for https://management.azure.com/.default and pass it as Authorization: Bearer. Jentic stores the underlying service principal in its vault so the agent only sees a scoped token.

Can I trigger a scheduled job on demand without waiting for the recurrence?

Yes. POST to .../jobCollections/{jobCollectionName}/jobs/{jobName}/run. The service executes the job's configured action immediately and records the result in execution history alongside the regular scheduled runs.

What action types does an Azure Scheduler job support?

The job action object supports HTTP and HTTPS requests, Azure Storage queue messages, and Azure Service Bus queue and topic messages. Each action type has its own request body shape — HTTP carries method, headers, body, and authentication; queue actions carry the message payload.

What are the rate limits for the Azure Scheduler API?

Calls count against Azure Resource Manager subscription throttling, roughly 12,000 reads and 1,200 writes per hour per subscription. Job execution itself is governed by the job collection's pricing tier, which caps the number of jobs and their minimum recurrence interval.

How do I create a scheduled job through Jentic?

Search Jentic for create scheduled http job, call client.load on the job PUT operation to receive its input schema, then call client.execute with subscriptionId, resourceGroupName, jobCollectionName, jobName, and the action plus recurrence. Jentic injects the OAuth token and returns the created job.