Azure Webjobs is a way to invoke scripts or applications under your Azure App Service Context. Which means you don’t need to provision a VM or other services. One example is the image resize for the images that are uploaded via your website. You can have an image resize utility running under the same Azure App Service where your website is running (or different) and that utility can resize the images as soon as they are uploaded.
There are two primary types of Webjobs – Triggered and Continuous.
Azure provides an SDK for web jobs which makes its super easy to integrate with Azure services like EventGrid, Event hub, Send Grid, Azure Blobs, Azure Queues, Cosmos Db etc.
Azure web jobs SDK has two main concepts to achieve integration with other services – Triggers and Bindings.
Triggers: As the name suggests you can start the execution of your job based on these triggers. For example if you want to run your job as soon as an image gets placed onto a particular blob.
Bindings: It provides you the capability to integrate with other services primarily categorizing into Input Bindings and Output Bindings.
Lets have a deep dive and hands on about writing Web jobs using Triggers and Bindings.
Article Board 
1 Comment