Custom Parameters

Custom Parameters let you define reusable task inputs once and link them to one or many automation tasks. This makes task execution flexible without changing step definitions every time.

Where to Manage Parameters

1. Open Operations > Automation.

2. Go to the Parameters tab.

3. Create, edit, and delete parameter definitions from the Custom Parameters table.

The Parameters tab is separate from the preview-gated Tasks tab, so parameter management is available even when task preview features are disabled.

Core Parameter Fields

Each parameter definition includes:

• Name - technical parameter name used for script/runbook matching.

• Display Title - friendly label shown to users at execution time.

• Description - helper guidance shown with input controls.

• Mandatory - whether users must provide a value.

• Display Position - base ordering metadata for the parameter definition.

• Parameter Type - controls the input model and available configuration.

Supported Parameter Types

Current parameter types available in create/edit dialogs:

• String - free text input with optional default value.

• Int - numeric input with optional default value.

• Bool - true/false switch with optional default.

• DateTime - date/time input value.

• Dropdown - user selects from configured value list.

• Graph Resources - dynamic dropdown populated by Azure Resource Graph query results.

• Known - mapped to built-in known parameter behavior.

Known Parameters

Known parameters provide standardized, built-in value sources (for example cloud resource selectors).

• SubscriptionId, SubscriptionName

• VirtualMachineId, VirtualMachineName

• ResourceGroupId, ResourceGroupName

• VirtualNetworkId, VirtualNetworkName

• AzureLocation, ComputeResourceSKU

• LoggedInUser

Use Known parameters when you want reliable, pre-defined value behavior without writing custom query logic.

Graph Resource Parameters

Graph Resource parameters are dynamic and query-driven.

• Enter a Resource Graph query and use Test Query.

• Review returned resources in test results.

• Set Value Property and Display Property mappings.

• Save the parameter and link it to tasks that need dynamic cloud resource selection.

Invalid queries show validation errors; always test query output before linking to production tasks.

Linking Parameters to Tasks

Parameters become active for task execution when linked in task configuration.

How Linking Works

• Open an automation task and go to linked parameter management.

• Use Link Parameter to select from unlinked custom parameters.

• Configure per-task overrides: display order, required override, and default value override.

• Save link order separately when reordering linked parameters.

Task-level overrides do not change the base parameter definition globally; they apply to that task link only.

Grouping and Discovery Modes

The parameter table supports three working modes:

• All Parameters - full inventory with type, mandatory status, linked tasks, and search.

• Group by Task - parameters organized per task, including shared-parameter visibility.

• Standalone Only - parameters not linked to any task.

Execution-Time Behavior

When a task is executed, linked parameters are prompted in the execution dialog.

• Parameter prompts follow the linked-parameter display order for that task.

• Required parameters are validated before execution is allowed.

• Provided values are passed to task execution by parameter name.

• Execution details show step output and errors for troubleshooting parameter-related failures.

Editing and Deletion Safety

• Editing a parameter updates that shared definition.

• Delete flow warns when a parameter is linked to one or more tasks.

• Removing a parameter can break task assumptions if steps/scripts still expect that input.

Recommendation: unlink and test tasks first before deleting parameters used in production workflows.

Best Practices

• Keep Name stable and script-aligned; use Title for user readability.

• Prefer Dropdown/Known/GraphResources when you want to reduce invalid free-text input.

• Use clear descriptions so operators understand expected format and impact.

• Review standalone parameters periodically and remove unused definitions.