Manage Azure resources and monitor costs by creating automation tasks (preview)


This capability is in public preview, is provided without a service level agreement, and is not recommended for production workloads. Certain features might not be supported or might have constrained capabilities. For more information, see Supplemental Terms of Use for Microsoft Azure Previews.

To help you manage Azure resources more easily, you can create automated management tasks for a specific resource or resource group by using automation task templates, which vary in availability based on the resource type. For example, for an Azure storage account, you can set up an automation task that sends you the monthly cost for that storage account. For an Azure virtual machine, you can create an automation task that turns on or turns off that virtual machine on a predefined schedule.

Behind the scenes, an automation task is actually a workflow that runs on the Azure Logic Apps service and is billed using the same pricing rates and pricing model. After you create the task, you can view and edit the underlying workflow by opening the task in the Logic App Designer. After a task finishes at least one run, you can review the status, history, inputs, and outputs for each run.

Here are the currently available task templates in this preview:

Resource type Automation task templates
Azure resource groups When resource is deleted
All Azure resources Send monthly cost for resource
Azure virtual machines Additionally:

- Power off Virtual Machine
- Start Virtual Machine

Azure Storage accounts Additionally:

- Delete old blobs

Azure Cosmos DB Additionally,

- Send query result via email

This article shows you how to complete the following tasks:

How do automation tasks differ from Azure Automation?

Currently, you can create an automation task only at the resource level, view the task's runs history, and edit the task's underlying logic app workflow, which is powered by the Azure Logic Apps service. Automation tasks are more basic and lightweight than Azure Automation.

By comparison, Azure Automation is a cloud-based automation and configuration service that supports consistent management across your Azure and non-Azure environments. The service comprises process automation for orchestrating processes by using runbooks, configuration management with change tracking and inventory, update management, shared capabilities, and heterogeneous features. Automation gives you complete control during deployment, operations, and decommissioning of workloads and resources.


  • An Azure account and subscription. If you don't have a subscription, sign up for a free Azure account.

  • The Azure resource that you want to manage. This article uses an Azure storage account as the example.

  • An Office 365 account if you want to follow along with the example, which sends you email by using Office 365 Outlook.

Create an automation task

  1. In the Azure portal, find the resource that you want to manage.

  2. On the resource menu, scroll to the Automation section, and select Tasks

    Screenshot that shows the Azure portal and a storage account resource menu where the "Automation" section has the "Tasks" menu item selected.

  3. On the Tasks pane, select Add so that you can select a task template.

    Screenshot that shows the storage account "Tasks" pane where the toolbar has "Add" selected

  4. On the Add a Task pane, under Select a template, select the template for the task that you want to create. If the next page doesn't appear, select Next: Authentication.

    This example continues by selecting the Send monthly cost for resource task template.

    Screenshot that shows the selections, "Send monthly cost for resource" and "Next: Authentication"

  5. Under Authentication, in the Connections section, select Create for every connection that appears in the task so that you can provide authentication credentials for all the connections. The types of connections in each task vary based on the task.

    This example shows only one of the connections that's required by this task.

    Screenshot that shows the selected "Create" option for the Azure Resource Manager connection

  6. When you're prompted, sign in with your Azure account credentials.

    Screenshot that shows the selection, "Sign in"

    Each successfully authenticated connection looks similar to this example:

    Screenshot that shows successfully created connection

  7. After you authenticate all the connections, select Next: Configuration if the next page doesn't appear.

  8. Under Configuration, provide a name for the task and any other information required for the task. When you're done, select Create.


    You can't change the task name after creation, so consider a name that still applies if you edit the underlying workflow. Changes that you make to the underlying workflow apply only to the task that you created, not the task template.

    For example, if you name your task Send monthly cost, but you later edit the underlying workflow to run weekly, you can't change your task's name to Send weekly cost.

    Tasks that send email notifications require an email address.

    Screenshot that shows the required information for the selected task

    The task that you created, which is automatically live and running, now appears on the Automation tasks list.

    Screenshot that shows the automation tasks list


    If the task doesn't appear immediately, try refreshing the tasks list or wait a little before you refresh. On the toolbar, select Refresh.

    After the selected task runs, you get an email that looks like this example:

    Screenshot that shows email notification sent by task

Review task history

To view a task's history of runs along with their statuses, inputs, outputs, and other information, follow these steps:

  1. In the Azure portal, find the resource that has the task history that you want to review.

  2. On the resource's menu, under Settings, select Automation tasks.

  3. In the tasks list, find the task that you want to review. In that task's Runs column, select View.

    Screenshot that shows a task and the selected "View" option

    The Runs history pane shows all the runs for the task along with their statuses, start times, identifiers, and run durations.

    Screenshot that shows a task's runs, their statuses, and other information

    Here the possible statuses for a run:

    Status Description
    Cancelled The task was cancelled while running.
    Failed The task has at least one failed action, but no subsequent actions existed to handle the failure.
    Running The task is currently running.
    Succeeded All actions succeeded. A task can still finish successfully if an action failed, but a subsequent action existed to handle the failure.
    Waiting The run hasn't started yet and is paused because an earlier instance of the task is still running.

    For more information, see Review runs history

  4. To view the statuses and other information for each step in a run, select that run.

    The Logic app run pane opens and shows the underlying workflow that ran.

    • A workflow always starts with a trigger. For this task, the workflow starts with the Recurrence trigger.

    • Each step shows its status and run duration. Steps that have 0-second durations took less than 1 second to run.

    Screenshot that shows each step in the run, status, and run duration

  5. To review the inputs and outputs for each step, select the step, which expands.

    This example shows the inputs for the Recurrence trigger, which has no outputs because the trigger only specifies when the workflow runs and provides no outputs for the subsequent actions to process.

    Screenshot that shows the expanded trigger and inputs

    In contrast, the Send an email action has inputs from earlier actions in the workflow and outputs.

    Screenshot that shows an expanded action, inputs, and outputs

To learn how you can build your own automated workflows so that you can integrate apps, data, services, and systems apart from the context of automation tasks for Azure resources, see Quickstart: Create your first integration workflow by using Azure Logic Apps - Azure portal.

Edit the task

To change a task, you have these options:

Edit the task inline

  1. In the Azure portal, find the resource that has the task that you want to update.

  2. On the resource's menu, under Automation, select Tasks.

  3. In the tasks list, find the task that you want to update. Open the task's ellipses (...) menu, and select Edit in-line.

    Screenshot that shows the opened ellipses menu and the selected option, "Edit in-line"

    By default, the Authentication tab appears and shows the existing connections.

  4. To add new authentication credentials or select different existing authentication credentials for a connection, open the connection's ellipses (...) menu, and select either Add new connection or if available, different authentication credentials.

    Screenshot that shows the Authentication tab, existing connections, and the selected ellipses menu

  5. To update other task properties, select Next: Configuration.

    For the task in this example, the only property available for edit is the email address.

    Screenshot that shows the Configuration tab

  6. When you're done, select Save.

Edit the task's underlying workflow

When you change the underlying workflow for an automation task, your changes affect only the task instance that you created, and not the template that creates the task. After you make and save your changes, the name that you provided for your original task might not accurately describe the task anymore, so you might have to recreate the task with a different name.


As a best practice, clone the underlying workflow so that you can edit the copied version instead. That way, you can make and test your changes on the copy while the original automation task continues to work and run without risking disruption or breaking existing functionality. After you finish your changes and are satisfied that the new version runs successfully, you can disable or delete the original automation task and use the cloned version for your automation task. The following steps include information about how to clone your workflow.

  1. In the Azure portal, find the resource that has the task that you want to update.

  2. On the resource's menu, under Automation, select Tasks.

  3. In the tasks list, find the task that you want to update. Open the task's ellipses (...) menu, and select Open in Logic Apps.

    Screenshot that shows the opened ellipses menu and the selected option, "Open in Logic Apps"

    The task's underlying workflow opens in the Azure Logic Apps service and shows the Overview pane where you can view the same runs history that's available for the task.

    Screenshot that shows the task in Azure Logic Apps view with Overview pane selected

  4. To open the underlying workflow in the Logic App Designer, on the logic app's menu, select Logic app designer.

    Screenshot that shows the "Logic app designer" menu option selected and designer surface with the underlying workflow

    You can now edit the properties for the workflow's trigger and actions as well as edit the trigger and actions that define the workflow itself. However, as best practice, follow the steps to clone your workflow so that you can make your changes on a copy while the original workflow continues to work and run.

  5. To clone your workflow and edit the copied version instead, follow these steps:

    1. On the logic app workflow menu, select Overview.

    2. On the overview pane's toolbar, select Clone.

    3. On the logic app creation pane, under Name, enter a new name for your copied logic app workflow.

      Except for Logic App Status, the other properties aren't available for editing.

    4. Under Logic App Status, select Disabled so that the cloned workflow doesn't run while you make your changes. You can enable the workflow when you're ready to test your changes.

    5. After Azure finishes provisioning your cloned workflow, find and open that workflow in the Logic App Designer.

  6. To view the properties for the trigger or an action, expand that trigger or action.

    For example, you can change the Recurrence trigger to run weekly, rather than monthly.

    Screenshot that shows the expanded Recurrence trigger with the Frequency list open to show available frequency options

    For more information about the Recurrence trigger, see Create, schedule, and run recurring tasks and workflows with the Recurrence trigger. For more information about other triggers and actions that you can use, see Connectors for Azure Logic Apps.

  7. To save your changes, on the designer toolbar, select Save.

    Screenshot that shows the designer toolbar and the selected "Save" command

  8. To test and run the updated workflow, on the designer toolbar, select Run.

    After the run finishes, the designer shows the workflow's run details.

    Screenshot that shows the workflow's run details on the designer

  9. To disable the workflow so that the task doesn't continue running, see Manage logic apps in the Azure portal.

Provide feedback

We'd like to hear from you! To report bugs, provide feedback, or ask questions about this preview capability, contact the Azure Logic Apps team.

Next steps