The other answers cover the template aspect of getting the job created in Azure, but there's still the question of getting the webjob executable uploaded.
Assuming this deploy is part of a larger Azure website deploy, you simply need to include your webjob executable in the distribution of your website.
Per the kudu documentation the convention for placing your EXE is as follows:
To deploy a triggered job copy your binaries to: app_data\jobs\triggered\{job name}
To deploy a continuous job copy your binaries to: app_data\jobs\continuous\{job name}
A template shared by David Ebbo shows how to deploy Webjobs using Arm Templates.
In this template, a triggered webjob is linked to a website deployed by the same template. A webjob is a part of a jobCollection. This jobCollection is linked to it's parent website using the "dependsOn" node.
Here's an Azure QuickStart Template that deploys an Azure Web App with a Schedule Job.
Additionally, have you looked at the Visual Studio 2015 Azure SDK support for the Azure Resource Manager project type? It contains UI for more easily authoring ARM Templates directly from within Visual Studio.
The other answers cover the template aspect of getting the job created in Azure, but there's still the question of getting the webjob executable uploaded.
Assuming this deploy is part of a larger Azure website deploy, you simply need to include your webjob executable in the distribution of your website.
Per the kudu documentation the convention for placing your EXE is as follows:
A template shared by David Ebbo shows how to deploy Webjobs using Arm Templates.
In this template, a triggered webjob is linked to a website deployed by the same template. A webjob is a part of a jobCollection. This jobCollection is linked to it's parent website using the "dependsOn" node.
Regards,