Automation Tasks

Automation Tasks let you build reusable multi-step workflows for operations such as script execution, runbooks, service actions, certificate deployment, and DevOps pipeline triggers. This guide focuses on how tasks behave in the current product UI, what each configuration option means, and how to avoid common mistakes.

In the Operator Automation area, the Tasks tab is currently behind preview features. If you do not see it, your tenant likely has preview features disabled.

Where to Work with Tasks

1. Open Operations > Automation.

2. Use the Tasks tab (preview feature) to create and manage general tasks.

3. Select a task to open the task configuration page with Task, Steps, and History tabs.

The Tasks list in Automation shows General tasks. Certificate tasks are linked to certificate templates and managed from certificate workflows.

Task Properties

Every automation task has the following core properties:

Name:

A unique, descriptive name for the task. This name is used throughout the interface to identify the task.

Description:

Optional detailed description of the task's purpose and functionality. This helps other operators understand what the task does.

Type:

General for standalone workflows, or Certificate for tasks linked to certificate templates. Task type controls which step types are available.

Created On:

Timestamp when the task was first created.

Last Modified On:

Timestamp of the most recent modification to the task configuration.

Task Types

General Tasks

General tasks are created from the Automation Tasks list and are used for standard operator automation. They support all general-compatible step types.

General tasks are best for reusable operational workflows such as script orchestration, runbook-based automation, machine actions, and service/process maintenance.

Certificate Tasks

Certificate tasks are linked to certificate templates and designed for certificate deployment/renewal workflows. They can use certificate-specific system variables and certificate-specific step types.

Certificate tasks provide additional step options that are not available to general tasks:

• Certificate Install - Deploy the renewed certificate to target machines

• Azure Key Vault - Update certificates in Azure Key Vault

Supported Step Categories

The available step types are filtered by task type. In current behavior:

Available for General and Certificate Tasks

• Runbook

• Run Command

• PowerShell Script

• Windows Service Action

• Execute DevOps Pipeline

Certificate-Only Step Types

• Azure Application Gateway

• Certificate Install

• Azure Key Vault (certificate deployment)

If a step type is missing in the Add Step dialog, verify task type first. The UI only shows step types supported for that task.

Managing Task Steps

Steps are the building blocks of automation tasks. Each step performs a specific action, and steps execute in sequence according to their execution order.

Adding Steps

Click the "Add Step" button on the Steps tab to open the step creation dialog. Select a step type and configure its settings, then click "Add Step" to save it to your task.

Reordering Steps

Use the up and down arrow buttons on each step to change its position in the execution order. Reordering only updates in-memory state until you click Save Step Order.

Remember to save the step order after making changes. Unsaved order changes will be lost if you navigate away from the page.

Editing Steps

Expand any step to view and modify its configuration. Each step type has different configuration options. After making changes, click "Save Step" to persist them.

A "Unsaved changes" indicator appears next to steps that have been modified but not saved.

Enabling/Disabling Steps

You can temporarily disable a step without deleting it. Disabled steps are skipped during task execution. Click the "Disable" or "Enable" button on any step to toggle its state.

Removing Steps

Click the "Remove" button on any step to delete it from the task. This action cannot be undone. The execution order of remaining steps will automatically adjust.

A good workflow is: Add Step → Configure Step → Save Step for each step, then do ordering as a final pass and use Save Step Order.

Step Execution Settings

Each step has advanced execution settings that control how it behaves within the task workflow:

Execute in Parallel:

When enabled, this step starts without waiting for earlier steps to complete. Use this only for independent operations.

Parallel steps cannot access output from steps that may still be running. Use this carefully when steps depend on each other.

Stop on Failure:

Enabled by default. When enabled, a failure in this step stops the task. When disabled, later steps can continue.

Delay Before Next Step:

If configured for a step, this delays the next step by the configured number of minutes and is shown in step execution settings.

Parallel + Stop on Failure: A parallel step can still stop the task on failure, but other parallel work may already be in progress.

Task Configuration Tabs

The task configuration page has three main tabs:

Task (Info Tab):

Configure task metadata (name/description) and review task-level details. Type is informational here and controls behavior across task configuration.

Steps:

Add, configure, and manage the steps that make up your automation workflow. This is where you build the actual logic of your task.

History:

View execution history with run status and details. History refreshes as runs complete and is the first place to troubleshoot failed runs.

Parameter Validation Alerts

A validation alert is shown when enabled steps contain mandatory parameters that have no direct value/default and are not linked as task parameters.

An alert banner appears at the top of the configuration page showing:

• The number of affected steps with missing required links

• Missing parameter names per step

• A quick Create & Link action for each missing parameter

Linking parameters allows you to prompt users for input when executing the task, making it reusable across different scenarios. Learn more in the Custom Parameters documentation.

Execution and Troubleshooting

You can execute tasks from task actions and then review outcomes in the History tab.

• Use history to verify whether failure happened at task level or a specific step.

• Check step execution settings first when behavior differs from expectation (especially Stop on Failure and Parallel).

• If a step keeps failing after edits, confirm the step was saved (no unsaved changes indicator).

• If execution path seems wrong, re-check step order and make sure Save Step Order was applied.

Deleting Tasks

To delete an automation task, navigate to the Automation Tasks list, find the task you want to delete, and click the "Delete" button in the options column.

Warning: Deleting a task is permanent and cannot be undone. All steps, execution history, and parameter links will be deleted. If the task is published, users will immediately lose access to it.

Recommendation: Before deletion, export/review key step settings or keep a reference task so you can recreate the workflow quickly if needed.