Schedule Azure WebJobs Using Azure Logic Apps

Image title

Migrate your Azure WebJobs with Azure Logic Apps before it’s too late.

In this article, we will see how to migrate Azure WebJobs from Azure Scheduler to Azure Logic Apps. As we all know, Azure Scheduler will become obsolete on December 31, 2019, after which all Scheduler job collections and jobs will stop running and they will be deleted from the system.

You may also enjoy:  An Inside Look at Microsoft Azure WebJobs

In order to continue to use jobs, we must move Azure Schedulers to Azure Logic Apps as soon as possible. Azure Logic Apps have numerous features:

  • Uses a visual designer and connectors to integrate with more than 200 different services, including Azure Blob storage, Azure Service Bus, Microsoft Outlook, and SAP.

  • Manages each scheduled workload as a first-class Azure resource.

  • Runs multiple one-time jobs using a single logic app.

  • Sets schedules that automatically adjust to daylight saving time.

  • For more details about its features and usage please refer to this article.

WebJobs is a feature of the Azure App Service that enables you to run a program or script in the same context as a web app, API app, or mobile app. There is no additional cost to use WebJobs. 

Schedule Azure WebJobs Using Azure Logic Apps.

Step 1: Create and deploy an on-demand (triggered) job under Azure App Service. Click here to learn how to create and deploy a WebJob.

Create on-demand job

Step 2: Create a blank Logic App.

Blank Logic App

Step 3: Edit the Logic app and select a Recurrence type of Schedule trigger.

Recurrence type

Step 4: Set the intervals according to your requirements. Also, you can set other parameters like Time Zone and Start Time as shown in the below image. In my case, I am going to set 1 minute without any extra parameter.

Setting parameters

Step 5: After trigger configuration, now it’s time to set HTTP action with post method and basic authentication.

Set HTTP action

"inputs": { "authentication": { "password": "password", "type": "Basic", "username": "$username" }, "method": "POST", "uri": },


Note: we can get the basic authentication from publish profile of an application where we have deployed the WebJob.

Step 6: Run the Logic App and check the status under run history.

Status check

WebJob Details

Note: You can download the code, copy and paste it in code view. Change your credentials and URI according to your WebJob; your Recurrence type Logic App is ready.

Expected Results

The Logic App has configured correctly, and it is working as expected. It is running the Azure WebJob according to the set frequency. If there is an error in the WebJob, then your run will be failed, and you can see it under Runs History.


In this article, we have learned how to schedule the WebJobs using Azure Logic Apps. In reference to the article given above, we noticed that the Azure Scheduler is scheduled to retire fully on December 31, 2019, and All Scheduler job collections and jobs will stop running and they will be deleted from the system simultaneously. So, before that, shift Azure Scheduler jobs to Azure Logic Apps as soon as possible.

Further Reading

Azure Logic Apps Lifecycle – The Big Picture

Azure WebJobs vs. Azure Functions

Comment here

This site uses Akismet to reduce spam. Learn how your comment data is processed.