Introduction:

In this article, we will see how to migrate Azure WebJobs from Azure Scheduler to Azure Logic Apps. As we all know that Azure Scheduler will become obsolete on 31st December 2019, after which all Scheduler job collections and jobs will stop running and they will be deleted from the system. 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 which are as below:-

  1. 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.
  2. Manages each scheduled workload as a first-class Azure resource.
  3. Runs multiple one-time jobs using a single logic app.
  4. Sets schedules that automatically adjust to daylight saving time.
  5. For more details about its features and usage please refer to the below article.

 

Migrate Azure Scheduler jobs to Azure Logic Apps

Before going further, Let’s know something Azure WebJobs:

WebJobs is a feature of 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. For more detail please refer to the below article.

Run Background tasks with WebJobs in Azure App Service

Now, we will see step by step, how to schedule Azure WebJobs using Azure Logic Apps.

Step1:

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

CodeView

 

Step 2:

Create a blank Logic App.

 

CodeView

 

Step 3:

Edit the logic app and select a Recurrence type of Schedule trigger.

CodeView

Step 4:

Set the interval, as per your requirement. 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.

 

CodeView

Step 5:

After trigger configuration, now its time to set HTTP action with post method and basic authentication.

CodeView

"inputs": {
   "authentication": {
   	"password": "password",
       "type": "Basic",
       "username": "$username"
        },
    "method": "POST",
    "uri": https://appname-webjob.scm.azurewebsites.net/api/webjobtype/webjobname/run
  },

CodeView

 

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.

 

CodeView

 

CodeView

 

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 as per 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.

Summary:

In the above article, we have learned how to schedule the WebJobs using Azure Logic Apps. In the reference of 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, we need to shift Azure Scheduler jobs to Azure Logic Apps.