There are 4 options in tasks(preview) in azure vm. I want to shutdown, deallocate a vm in the evening and start in the morning. So I have created three tasks. It says chargeable in the creation menu. I'd like to know how much its charged. docs page also doesnt define clearly this.
Hi @Ashad-0363
Azure Automation Tasks use Azure Logic Apps as their service deployment and payment model. The Task creates a Logic App that you can review the tasks and operations under, the Logic App will be the name of the Task created from the resource. https://azure.microsoft.com/en-us/pricing/details/logic-apps/
Thank you very much for your answer. I'm not familiar with azure logic app and how it's charged. based on the link, you shared with me. Azure charges $0.000025 per action. since I have 3 tasks - shutdown, deallocate and start in a day. are these tasks considered 3 actions in logic apps ?
@Ashad-0363 Not quite. When Azure Automation creates the Logic App for one of those tasks, for example for Start Virtual Machine, the Logic App workflow will comprise of a recurrence trigger and multiple actions. You can determine or get an idea of how much it will cost by examining the Logic App workflow that Azure Automation created under the covers, and correlating the details to the LA pricing model. If you've already created a Task, you'll probably find the Logic Apps resource in the resource group.
As an example, below is the screenshot of a Logic Apps workflow that was created from the Start Virtual Machine task for a VM that runs a BizTalk server:
Sorry for the blurry screenshot in advance but you may see that it has (a) recurrence trigger, (b) Start VM action (c) Conditional action followed by (d) Outlook action that sends email notification on success or failure.
Because the Recurrence trigger is built-in, its runs are charged at Actions price which is $0.000025 as of this writing. Also, because the Start VM action is part of the Azure VM connector which is classified as a Standard-tier connector, its runs are charged at $0.000125 rate. Similarly, you may make the same determinations for the Conditional and Outlook actions and then get an idea of how much the total will be for each run of the overall workflow. I would also factor in and be mindful of unmetered runs and any retry policies that come into play in the pricing model as well.
13 people are following this question.
