canonical: https://jentic.com/apis/azure.com/schedulermanagementclient

# Microsoft Azure SchedulerManagementClient

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.

## For AI 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.

## Scope

Does not run multi-step workflows, host application code, or send notifications by itself - use for managing recurring HTTP, queue, service bus, and webhook job triggers only.

## Capabilities

- 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
- Inspect execution history including status, response codes, and retry attempts for a job
- List job collections at subscription or resource group scope to audit scheduled workloads

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

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

## Key resources

- **JobCollections** — Group of jobs sharing quota and pricing tier; supports create, update, delete, enable, disable
- **Jobs** — Individual scheduled actions with recurrence and retry policy; supports CRUD, run, and history

## Why Jentic

- **Setup:** Wiring SchedulerManagementClient by hand means registering an Azure AD app, running the OAuth2 azure_auth token exchange for the management.azure.com audience, and shaping a different request body for each action type (HTTP, storage queue, service bus, webhook). Through Jentic you install once, import SchedulerManagementClient from the API Directory, store the Azure service principal credential once, and your agent calls it.
- **Permission scoping:** SchedulerManagementClient puts the job collection and job name in the URL path (.../jobCollections/{jobCollectionName}/jobs/{jobName}/...), so a rule can pin your agent to one job collection. You choose the operations it may call, so destructive ones like disabling a collection or deleting a job are not included unless you add them.
- **Credential handling:** Your Azure service principal 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.
- **Discovery method:** Agents search Jentic by intent such as 'create a recurring HTTP job in Azure Scheduler' or 'trigger a scheduled job on demand', and Jentic returns the matching SchedulerManagementClient operation with its input schema covering job collection, job, action, and recurrence shape.

## Related APIs

- **Azure AutomationManagementClient** — Multi-step orchestrated runbooks rather than single-action recurring jobs
- **Azure LogicManagementClient** — Visual workflow with rich connectors triggered on a schedule
- **Azure ResourceManagementClient** — Provisions the resource group that holds Scheduler job collections

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

### 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.

### Can I limit what my agent is allowed to do with the Microsoft Azure Scheduler API?

Yes. Because you run Jentic One yourself, your own rules decide which SchedulerManagementClient operations and credentials the agent may use. The job collection and job name sit in the URL path, so a rule can pin the agent to a single job collection and only the operations you approve, such as creating a job, triggering an on-demand run, or reading execution history. Destructive calls like disabling a collection or deleting a job are excluded unless you add them.