Scheduling web jobs in Basic tier web apps

You have an application that is deployed to an Azure Web App running in Basic App Service hosting plan. You have a couple of web jobs there that are supposed to run on schedule and you chose to define the schedules with cron expressions. One day you noticed that these schedules never fired even though you remembered how you tested them on the Free plan and they seemed to work. You have Always On enabled as you want Kudu to always run to be able to trigger your scheduled jobs.

You check the state of your scheduled job with the following GET request:

GET https://{website}{jobname} HTTP/1.1
Authorization: Basic <your deployment credentials>

The response may look something like this:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8

     "latest_run": null,
     "history_url": "https://{website}{jobname}/history",
     "scheduler_logs_url": "https://{website}{jobname}/job_scheduler.log",
     "name": "TestJob",
     "run_command": "{jobexecutable}.exe",
     "url": "https://{website}{jobname}",
     "extra_info_url": "https://{website}{jobname}",
     "type": "triggered",
     "error": null,
     "using_sdk": true,
     "settings": {
          "schedule": "0 0 2 * * *"

If you triggered the task before, for instance manually, the 'latest_run' property will contain a state object of the last run attempt including a URL to the output log. You see that the schedule has been picked up and you expect the task to run at 2AM every day. Once you have checked out the scheduler logs:

GET https://{website}{jobname}/job_scheduler.log HTTP/1.1
Authorization: Basic <your deployment credentials>

HTTP/1.1 200 OK
Content-Type: application/octet-stream

[10/12/2015 06:18:27 > bfef75: SYS INFO] 'Basic' tier website doesn`t support scheduled WebJob.
[10/20/2015 05:10:10 > 2613fc: SYS INFO] 'Basic' tier website doesn`t support scheduled WebJob.
[10/20/2015 14:50:35 > 2613fc: SYS INFO] 'Basic' tier website doesn`t support scheduled WebJob.
[10/21/2015 02:32:37 > 882beb: SYS INFO] 'Basic' tier website doesn`t support scheduled WebJob.

I bet you’re ready to exclaim…


It has to be some marketing trick! Technically all you need is Always On which is supported on Basic and Standard tiers as you run a dedicated resource (read VM, well at least a separate application pool) and it's possible to configure the start mode of your application pool to AlwaysRunning.

Now why did it work on the Free tier? Perhaps they wanted to give you a taste of it or enable you to use the Free plan for development and testing activities and then you were supposed move to Standard for the show time. But why can't you use a perfectly valid Basic plan option when your application isn't that big and you can save a few bucks?

Using an external trigger

When you deploy from VS Microsoft.Web.WebJobs.Publish package sets up a free Azure Scheduler collection and adds scheduler jobs for your scheduled web jobs so they are triggered externally. In fact, you can trigger an On-Demand or a scheduled task with the following POST request (note that both On-Demand and scheduled jobs are referred to as triggered in terms of Kudu):

POST https://{website}{jobname}/run HTTP/1.1
Authorization: Basic <your deployment credentials>

HTTP/1.1 202 Accepted

You have to authenticate when making requests to Kudu. When you run them in the browser it will send your cookie but you can also use Basic authentication to run them from anywhere else. You need to use your deployment credentials which are associated with your live account. Now this is another twisted thing, please see this article for the explanation. The twisted part is that you define or reset your deployment credentials on one of your web app's settings blade but it's going to work with all apps as it's an account-wide setting.

Deployment credentials reset blade

Once you have your credentials all you need is to Base64 encode them:

var credentials ="username:password";
var bytes = Encoding.UTF8.GetBytes(credentials);
var value = Convert.ToBase64String(bytes);

You are now ready to set up an external trigger preferably with an automation option that is supported by your chosen scheduling system. You can use external solutions or you can choose Azure Scheduler.

One important thing to note about Azure Scheduler is that there can be only one free collection per Azure subscription that can contain up to 5 jobs. Pretty limiting but still can be used for your smaller applications. Another thing to note is that although Azure Scheduler supports a whole bunch of outbound authentication options for your jobs they are not supported on the Free tier.

But how does it work when deploying from VS?

Yes, it's another twist. If you try to set up a job on the portal input controls for Basic authentication credentials will be grayed out:

Grayed out input controls for Basic credentials

But you can still define the Authorization header directly:

Custom job HTTP headers

Is it a bug? Or a temporary workaround? Whatever it is you may also want to automate your schedule creation and you can do that with PowerShell:

New-AzureSchedulerJobCollection -JobCollectionName "TestCollection" -Location "West Europe" -Plan "Free"
$headers = @{"Authorization" = "Basic {your deployment credentials}"}
New-AzureSchedulerHttpJob -JobCollectionName "TestCollection" -JobName "TestJob" -Location "West Europe" -Method "POST" -URI https://{website}{jobname}/run -Headers $headers -Frequency "Day" -Interval 1

It's going to create a job in a free collection that will run once a day.