Machines

The Machines tab in Operations > Automation is where you manage execution targets for run commands and AZExecute Agent operations. It includes Azure virtual machines and Arc-enabled machines discovered through your tenant access.

What You Can Do

• Search and filter managed machines by name or resource group.

• Install or re-install AZExecute Agent on supported Windows machines.

• Add run commands per machine.

• Expand each machine to inspect command execution state and details.

• Bulk-install the agent for selected machines.

• Use agents and agent groups as sync targets for managed PowerShell modules.

Agent Installation

The machine grid exposes Install Agent / Re-Install actions and a multi-select bulk install button. The installer flow uses a confirmation dialog and then triggers installation operations through Azure/Arc command execution.

Agent install actions are intended for Windows machines. Linux machines remain available for run-command scenarios according to platform capabilities.

Direct download used in the UI: AZExecute-latest.msi

Expanded Machine View

When you expand a machine, the UI can show two execution surfaces:

• AZ Client tab (shown when the AZExecute Agent is present): machine inventory and agent-side task details.

• Arc/Azure Run Command tab: command history with state, timing, and command actions.

Run command details support:

• Re-run existing command definitions.

• Delete command definitions.

• Auto-refresh command status in-place while monitoring activity.

PowerShell Module Sync Targets

Agents are the machines that receive managed PowerShell modules. When a module is assigned to an agent or an agent group, each matching agent downloads and installs the assigned module version into the AZExecute-managed module location.

• Assign modules directly to one machine for testing, exceptions, or specialist workloads.

• Assign modules to agent groups when the same dependency must be available on many machines.

• Review module sync status and logs from the Modules page when a script cannot import a dependency.

Use PowerShell Modules to manage module versions, assignments, and sync health.

Operational Notes

• Missing machine records usually indicate access scope, discovery, or connectivity constraints.

• Newly installed agents may take a short time before version/check-in details are visible.