Azure Scheduler lets you run jobs on any schedule, such as calling HTTP/S endpoints or posting messages to Azure Storage queues. Integrate jobs into your applications that run immediately, on a recurring schedule, or anytime in the future—and call services both inside and outside of Azure.
Pricing Details
Free | Standard | P10 Premium | P20 Premium | |
---|---|---|---|---|
Price per Month 1 | Free | ¥96.81/unit | ¥938.15/unit | ¥10,300/unit |
Job executions 2 | 3,600 | Unlimited | Unlimited | Unlimited |
Maximum execution frequency | Every hour | Every minute | Every minute | Every minute |
Job collections | 1 | 10/unit | 10k/unit | 5k/unit |
Jobs per collection | 5 | 50 | 50 | 1,000 |
Scaling | N/A | Up to 10 units |
1 premium unit
Contact us for more |
1 premium unit
Contact us for more |
Outbound authentication | -- | √ | √ | √ |
1 Billing is prorated hourly. One standard unit is billed for every 10 job collections (or fraction) created, prorated hourly. Similarly, one premium unit is billed for every 10,000 job collections (or fraction) created, prorated hourly. Jobs are aggregated across geographies.
2 The execution times of jobs in the Free Scheduler services will be counted every 30 days. All service tiers will be restricted by the maximum execution frequency and the total number of executable jobs. Within the 30-day calculation period, the number of job executions will be actually limited as follows: 21.6 million executions for every standard unit and 21.6 billion executions for every advanced unit. The word “limitless” in the tables above means that the total number of executions for every unit is limitless within the maximum execution frequency.
FAQ
Expand all-
What is the billing for Scheduler?
In the case of one or multiple active job assemblages, Scheduler will prorate billing by the hour. A Standard unit will be charged in proportion to the number of hours for every 10 Standard job assemblages (or part of them) established. Similarly, an Advanced unit will be charged in proportion to the number of hours for every 10,000 Advanced job assemblages (or part of them) established.
-
Is the Scheduler quota applied at the subscription level?
The quota of Scheduler shall be applied at the subscription level. In addition, it is worth noting that all the jobs of a given job assemblage will be bound to the region of that job assemblage.
-
How long will be the job execution log be retained?
The execution log contains the history records of job executions from the previous 60 days.
-
Can I upgrade my Scheduler service from the Free version to the Standard version?
Yes, the existing job assemblage can be upgraded by updating the hierarchy features.
-
How is the high availability of Scheduler achieved?
Scheduler supports high availability by matching two regions across the same territory, such as pairing southern central America and northern central America, northern Europe and western Europe, eastern Asia-Pacific and southeastern Asia-Pacific. The jobs submitted to a given territory (see the following listed territory) can be executed in either of the paired regions.
-
Is Scheduler independent from the Scheduled Job feature in the Mobile Service?
Yes, they are independent from each other, although they can both offer scheduling features. The Scheduled Job feature in the Mobile Service is a feature of the same kind while Scheduler is an independent scheduling program with more extensive usage occasions.
Support & SLA
If you have any questions or need help, please visit Azure Support and select self-help service or any other method to contact us for support.
We guarantee in at least 99.9% of cases all schedule calling operations can be started within 30 minutes of the scheduled time. Availability is charged and settled per month. To learn more about the details of our Service Level Agreement, please visit the Service Level Agreements page.