Automation Tasks

Welcome to the Automation Tasks documentation for AZExecute. Automation Tasks enable you to orchestrate complex workflows across Azure and on-premises environments by combining multiple automation steps into reusable, executable tasks.

In the Operator experience, Automation is organized around Tasks, Parameters, Scripts, Accounts, and Machines. Build the workflow in Tasks, collect reusable input in Parameters, and use Scripts, Accounts, and Machines as the reusable building blocks.


What are Automation Tasks?

Automation Tasks are workflow orchestrations that combine multiple steps to automate complex operations. Each task can execute a sequence of actions including:

• Running Azure Automation runbooks

• Executing PowerShell or Bash scripts on AZExecute agents

• Running scripts on Azure VMs through Azure Run Command

• Creating or updating TOPdesk incidents

• Creating users, creating groups, and updating objects in Active Directory

• Managing Windows services and SCOM maintenance mode

• Triggering Azure DevOps pipelines

• Deploying certificates to machines, Key Vault, Application Gateway, Application Proxy, Citrix ADC, and Azure-native services


Automation Tasks Overview

Key Features

Multi-Step Workflows:

Chain multiple automation steps together to create complex workflows. Steps normally run in order, and output from earlier steps can be reused by later steps with variables.

Reusable Custom Parameters:

Define parameters once and reuse them across multiple automation tasks. Parameters can be mandatory or optional, with support for various types including text, dropdowns, and checkboxes.

Global Variables:

Share data between steps using variable references with the {{ VariableName }} syntax. Variables can come from user input, certificate task context, scripts, TOPdesk steps, Active Directory actions, and other step output.

Parallel Execution:

Organize steps into execution groups and decide whether a group should wait for the previous group or start in the same execution stage. Individual steps can still use step-level parallel execution when the work inside a group is independent.

Error Handling:

Use Stop on Failure to control whether task execution halts when a step fails or continues with remaining steps.

Publishing & Sharing:

Publish automation tasks to end users with role-based access control. Published tasks appear in a user-friendly interface for execution without requiring operator privileges.

Execution History:

Track all task executions with detailed history including status, duration, step-by-step results, and error details for troubleshooting.


Execution Groups

Automation task steps are displayed in groups. A group is a practical execution stage: keep dependent steps in the same ordered flow, and split unrelated work into separate groups when it can run independently.

• A group header shows the group name, step count, and whether the group runs with the previous group.

Run with previous group starts that group in the same execution stage as the group above it.

• Leave the setting off when the group depends on outputs, installed files, service state, or variables from the previous group.

• Use step-level parallel execution only inside groups where those individual steps do not depend on each other.

A real production pattern is to validate prerequisites in one group, deploy or update several independent targets in parallel groups, and finish with a final sequential verification group.


Task Types

AZExecute supports two types of automation tasks:

General Tasks:

Standalone automation workflows for any purpose. These tasks are created manually and can contain any combination of supported step types.

Certificate Tasks:

Specialized tasks linked to ACME certificate templates. These tasks are automatically associated with certificate renewal workflows and can automate certificate deployment after renewal.


Use Cases

Common scenarios where Automation Tasks provide value:

Certificate Deployment: Automatically deploy renewed certificates from Key Vault to application servers and restart services.

Application Deployment: Orchestrate complex deployment workflows involving Azure resources, on-premises systems, and DevOps pipelines.

Disaster Recovery: Create automated failover sequences that execute across multiple systems in the correct order.

Compliance Automation: Run scheduled compliance checks across your infrastructure with automated remediation steps.

Self-Service Operations: Publish pre-approved automation tasks to end users, enabling them to perform operations safely without operator access.


Getting Started

To begin using Automation Tasks, we recommend following this learning path:

1. Getting Started Guide - Create your first automation task

2. Automation Tasks - Learn about task configuration and management

3. Task Steps - Understand all available step types

4. Custom Parameters - Create reusable parameters

5. Global Variables - Share data between steps

6. Automation Accounts - Manage imported Automation Accounts and runbooks

7. Machines - Manage run-command targets and AZExecute Agent installation

8. Scripts - Build and manage reusable script content


If you encounter any issues or need further assistance, please contact us at

info@azexecute.com

. Our support team is here to help you.

An unhandled error has occurred. Reload 🗙
An unhandled error has occurred. Reload 🗙