WebJobs Options
Start course

This course will show practical applications of key Azure features to meet the programming and configuration challenges introduced by long-running tasks.

We'll start with Azure Batches and how you can use them to create large-scale, parallel, and high-performance apps in the Azure cloud. Then we'll go over Azure Queues and how they can add resiliency to your web applications. Next, you'll look at Webhooks and how they can address events in your cloud apps. Finally, we'll show you WebJobs and how they can deal with continuous processing tasks.

By the end of this course, you should be able to understand and apply these four Azure features to solve some of the challenges you face with long-running tasks, especially in high-performance computing applications.

Learning Objectives

  • Create large-scale, parallel, and high-performance apps by using Azure Batches
  • Build resilient apps by using Azure Queues
  • Implement code to address application events by using Azure Webhooks
  • Address continuous processing tasks by using Azure WebJobs

Intended Audience

  • People pursuing the Microsoft AZ-203 certification
  • IT professionals, web developers, DevOps administrators


  • Basic understanding of cloud concepts
  • Familiarity with web programming
  • Exposure to Azure configuration (Portal, CLI, or PowerShell)

We’d love to get your feedback on this course, so please give it a rating when you’re finished.


A few notes on the scale option. Generally, we want the WebJob to run alongside the web app. So as you scale out, you get one-to-one growth of your job instances. However, it is possible to limit the number of jobs as you scale. Also with the SDK, you can choose a batch size to load balance between job instances based on new messages from a queue and using a size of one. The default batch size is 16. 

One caveat, especially for long-running tasks, is a timeout after 20 minutes. Azure has its own internal techniques for optimizing the resources consumed by a web app within an app service. So you would need to use the Always On feature of Azure App Service as a countermeasure if needed. This is only available in some premium pricing tiers so be sure to check which features are supported especially if you're running a pilot project with a free trial or a demo subscription. Another limitation of the free or shared pricing tier is scaling. 

Azure Functions provide another way to run programs and scripts. You can look at the Azure documentation to choose between functions and WebJobs and also compare these Azure features to Flow and Logic Apps in the serverless comparison section of Azure Functions.

About the Author

Derrick is a content contributor and trainer for Microsoft cloud technologies like Azure, Office 365 and Dynamics 365. He works across North America and Europe to help companies and organizations with these technology shifts. Before that he has worn many hats but prefers to wear them one at a time.

When he is not night walking during his travels, you can find him on a bicycle path or performing guitar solos to an imaginary audience in his basement.