Task Steps

Task steps are the executable units inside an automation task. This page explains the currently available step types, what each step requires, and how to configure steps so executions are predictable in production.

Step availability depends on task type. General and Certificate tasks do not expose the exact same step set.

Step Availability by Task Type

Available for General and Certificate Tasks

• PowerShell Script

• Runbook

• Run Command

• Manage Windows Service

• Execute DevOps Pipeline

Certificate-Only Step Types

• Azure Application Gateway

• Azure Key Vault (certificate target)

• Certificate Install

1. PowerShell Script Step

Executes a stored script on a selected AZExecute client machine.

Required: Client Machine + Script

Optional: PowerShell version and script parameter values

• PowerShell version selector is shown when the selected machine reports PowerShell Core support.

• Parameters support static values and variable references from linked task parameters.

• Good fit for custom logic and legacy integration on managed machines.

2. Runbook Step

Executes a runbook from an Azure Automation Account.

Required: Automation Account + Runbook + Run On target

Optional: Runbook parameters

• Run On can be Azure (cloud) or a Hybrid Worker Group.

• Parameter inputs are generated from the selected runbook parameter definitions.

• Use for Azure-native operations or workflows already standardized in runbooks.

3. Run Command Step

Runs a stored script on an Azure VM through Azure Run Command.

Required: Subscription + Virtual Machine + Script

Optional: Script parameters

• VM list is loaded from the selected subscription.

• Includes script preview and parameter input when script parameters exist.

• Best for short/medium remote actions on Azure VMs without deploying AZExecute client agent there.

For complex long-running orchestration, prefer a Runbook or agent-based PowerShell step.

4. Azure Key Vault Step (Certificate Tasks)

Targets a Key Vault certificate entry for certificate deployment/update.

Required: Key Vault + Certificate Name

• Key Vault picker is grouped by tenant and supports cross-tenant visibility based on settings/access.

• You can select an existing certificate name or type a new one.

• Use this to keep certificate targets centralized for Azure workloads.

5. Certificate Install Step (Certificate Tasks)

Installs certificates on a selected AZExecute client machine.

Required: Client Machine

Optional: PFX export, cleanup, IIS binding update, binding entries

• Supports private key exportability and optional PFX export path/password.

• Supports cleanup of older certificates generated by AZExecute naming pattern.

• IIS binding updates can be configured with one or many binding entries.

6. Windows Service Action Step

Performs service operations on a selected AZExecute client machine.

Required: Target Machine + Service Name + Action

Optional: Startup Type + Startup Parameters (for Configure action)

• Service Name expects the internal service name, not display text.

• Actions include Start, Stop, Restart, and Configure.

• Common in post-deployment sequences (for example after cert or config updates).

7. Azure Application Gateway Step (Certificate Tasks)

Targets Azure Application Gateway certificate integration in certificate workflows.

Required: Application Gateway target details based on your environment configuration

This step type is available for Certificate tasks only and is intended for certificate-centric automation paths.

8. Execute DevOps Pipeline Step

Triggers Azure DevOps pipelines from within your task workflow.

Required: Organization + Project + Pipeline

Optional: Branch + pipeline parameters

• Organizations are listed by tenant and then projects/pipelines are loaded progressively.

• Branch suggestions are loaded from pipeline details.

• Pipeline parameters support task-level variable usage through linked custom parameters.

Common Step Behavior

• Execution Order: Change with arrow controls, then persist with Save Step Order.

• Execute in Parallel: Step starts without waiting for earlier steps.

• Stop on Failure: When enabled, failure in this step stops task progression.

• Unsaved Changes: Step edits are not active until saved with Save Step.

• Enabled/Disabled: Disabled steps are skipped without deleting configuration.

Always save each edited step before running, and save step order after reordering.