Halo + PowerShell Integration
Halo's native PowerShell integration runs your scripts automatically — triggered by ticket actions, approval steps, or on a schedule. Pass live ticket data straight into your parameters. Included in every licence.
What it does
Every trigger, every action, every result — controlled entirely from within your Halo configuration.
Assign a PowerShell script to any Halo action. When that action is performed on a ticket, the Halo Integrator fires the script automatically — passing live ticket data in as parameters. Configured at Configuration > Tickets > Actions, with the system use set to "Queue PowerShell Script".
Link a PowerShell script to a specific step in a Halo approval process. The script fires when that approval step is approved — ideal for provisioning tasks that require sign-off before changes are made. Configured at Configuration > Tickets > Approval Processes.
Run PowerShell scripts as part of Halo's built-in scheduled tasks. Housekeeping routines, nightly sync jobs, and recurring compliance checks — all managed from within Halo without relying on external schedulers.
Map any Halo field — ticket ID, user details, custom fields — directly to your PowerShell script parameters. The values are passed automatically at execution time. You declare variables in your script; Halo populates them.
Halo evaluates each script's output against a configured result text. If matched, the ticket status is automatically updated to your defined success state. If the script fails, the failure message is added as a ticket action for visibility. There is no limit on the number of scripts you can configure.
Everything included
No add-ons. No tiers. Every PowerShell integration feature is available in every Halo licence from day one.
Getting started
The steps below walk through how Halo's PowerShell integration is configured. Allied ESM can scope and deliver this as part of your project — contact us to discuss what's involved.
Before you start
Halo Integrator
The Halo Integrator must be installed and running on a server in your environment. This is the component that executes PowerShell scripts — scripts run on this server, not on Halo's own infrastructure. The user account running the Integrator scheduled task must have permission to execute the scripts.
Scripts accessible on the Integrator server
Your PowerShell script files must be stored on the server where the Integrator runs and accessible via a local file path (e.g. C:\Scripts\mailbox-resize.ps1). Halo stores the path reference — not the script content itself.
Agree which manual task is the best first candidate — onboarding, mailbox changes, and AD account management are the most common starting points.
Write the PowerShell script and declare the variables it needs (e.g. $Username, $MailboxSize). These variable names are what you'll map to Halo fields in the next steps. Save the script to the Integrator server.
Go to Configuration > Integrations and enable the PowerShell module. Once enabled, click into it to begin configuration. Create a new script entry: give it a name, set the file path to the script on the Integrator server, and choose the type — Action or Approval.
Add field mappings in the script configuration — match each Halo field (ticket, customer, site, user, or custom field) to the corresponding script variable name. Halo passes the live values into the script at execution time.
For action-triggered scripts: go to Configuration > Tickets > Actions, set the system use to "Queue PowerShell Script", and choose your script. For approval-triggered scripts: go to Configuration > Tickets > Approval Processes, open the relevant process, and assign the script to the appropriate approval step.
Set the success result text that Halo should match against your script's output, and choose the ticket status to apply on success. Configure a failure status too — failed runs are logged as a ticket action with the full failure message. Run a test, confirm the outcome, and go live.
As a pure play Halo partner, Allied ESM can scope and configure PowerShell automation as part of your project — writing scripts, setting up the Integrator, building field mappings, and documenting every routine for your team. Contact us to discuss what's involved.
Real-world examples
These three workflows are the most common starting points for teams implementing the Halo PowerShell integration.
A service request is raised for a new employee. The manager approves it in Halo. PowerShell creates the AD account, assigns group memberships, provisions the mailbox, and sets the correct permissions — the new starter is ready before their first day without a single manual task.
A user raises a service request to increase their Exchange mailbox quota. IT approves it via Halo's approval workflow. The Integrator runs the PowerShell script with the user's email and new quota size passed as parameters. The mailbox is updated; if the result text matches, the ticket status is set to resolved automatically.
An HR leaver ticket is raised in Halo. On manager sign-off, PowerShell immediately disables the AD account, removes the user from all security groups, and revokes email access. If anything fails, the failure message is logged as a ticket action for the team to review.
Common questions
Allied ESM can scope and configure PowerShell automation for your Halo project. Tell us what you want to automate first.