What is Azure Scheduler?
Azure Scheduler helps you create jobs that run in the cloud by declaratively describing actions. The service then automatically schedules and runs those actions. For example, you can call services inside and outside Azure, such as calling HTTP or HTTPS endpoints, and also post messages to Azure Storage queues and Azure Service Bus queues or topics. You can run jobs immediately or at a later time. Scheduler easily supports complex schedules and advanced recurrence. Scheduler specifies when to run jobs, keeps a history of job results that you can review, and then predictably and reliably schedules workloads to run.
Although you can use Scheduler to create, maintain, and run scheduled workloads, Scheduler doesn't host the workloads or run code. The service only invokes the services or code hosted elsewhere, for example, in Azure, on-premises, or with another provider. Scheduler can invoke through HTTP, HTTPS, a Storage queue, a Service Bus queue, or a Service Bus topic. To create, manage, and schedule jobs, you can use the Azure portal, code, Scheduler REST API, or Azure Scheduler PowerShell cmdlets reference. For example, you can programmatically create, view, update, manage, or delete jobs and job collections by using scripts and in the Azure portal.
Other Azure scheduling capabilities also use Scheduler in the background, for example, Azure WebJobs, which is a Web Apps feature in Azure App Service. You can manage communication for these actions by using the Scheduler REST API. helps manage the communication for these actions.
Here are some scenarios where Scheduler can help you:
Run recurring app actions: For example, periodically collect data from Twitter into a feed.
Perform daily maintenance: Such as pruning logs daily, performing backups, and other maintenance tasks.
For example, as an administrator, you might want to back up your database at 1:00 AM every day for the next nine months.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.