For this recipe, you will need an existing public application that executes some business logic which does not require any dynamic input. We will leverage the Azure-hosted MVC application created in the previous recipe.
From an Azure perspective, you will require a valid Azure subscription to create a Scheduler.
The basic job collection is free of charge (limited to a minimum of hourly intervals between executions).
You will also need a preexisting job collection to use in your Scheduler; alternatively, you can create one when creating your first Scheduler.