Updated: January 13, 2015
Azure Scheduler allows you to declaratively describe actions to run in the cloud, and then schedules and runs those actions automatically. Azure Scheduler can do this using either the Azure portal or through code.
Azure Scheduler maintains, manages, schedules, and invokes scheduled work. Azure Scheduler does not host any workloads or run any cod. It only invokes code hosted elsewhere; this code may be hosted in Azure, on-premise, or with another provider, and may be invoked via HTTP, HTTPS, or a storage queue. Azure Scheduler schedules jobs, keeps a history of job execution results that one can interrogate, and deterministically and reliability schedules workloads to be run. Azure Mobile Services Scheduled Scripts, Azure Web Sites WebJobs, and other Azure scheduling capabilities use Azure Scheduler behind the scenes.
Azure Scheduler is a multi-tenant application service for scheduling reliable actions on a recurrent or calendar aware-basis, executed reliably even in the face of network, machine, and data center failures. The Scheduler REST API helps manage the communication for these actions.
There are several scenarios that lend themselves to the usage of Azure Scheduler. For example:
Recurring application actions: As an example, a service may periodically get data from twitter and gather the data into a regular feed.
Daily maintenance: Web applications have needs such as daily pruning of logs, performing backups, and other maintenance tasks. An administrator may choose to backup her database at 1AM every day for the next 9 months, for example.
The Scheduler API allows you to create, update, delete, view, and manage “job collections” and scheduled “jobs” programmatically.