In the previous recipe, we created an Azure-hosted web application that was accessible publicly. The façade encapsulated some Dynamics 365 business logic to create a timestamped account with a specific name format. In this recipe, we will leverage this application to create an Azure Scheduler task that will send an HTTP request on an interval to execute the code behind our MVC application.
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.
Note
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.
