Automate recurring tasks on your Azure resources with scheduled actions.
Task Ember's scheduler lets you define recurring actions on your resources - start VMs at 9am, stop them at 6pm, or run PowerShell scripts on a schedule.
The most common use case. Schedule your Azure VMs to start in the morning and stop in the evening to save costs.
Example: Start at 08:00, Stop at 18:00, Monday-Friday, UK timezone.
Run PowerShell scripts on Azure VMs at scheduled times. Useful for maintenance tasks, health checks, or data collection.
Example: Run disk cleanup every Sunday at 02:00.
Scheduled chains run in Long Running mode, so every script parameter needs a manual value and the chain cannot contain decision branches.
Script chains let you run multiple PowerShell scripts in sequence on your VMs.
| Mode | Description |
|---|---|
| Sequential | Scripts run one after another. If a script fails, the chain stops |
| Fast | All scripts bundled into a single execution (no parameter passing between scripts) |
| Long Running | For scripts that take more than 5 minutes. Runs via Azure Custom Script Extension |
Add decision nodes between scripts to conditionally execute different paths based on the output of the previous script.
Scripts can accept parameters that are:
A VM schedule applies to the VMs in its component. A PowerShell schedule runs the chain on the target resources selected in the Remote PowerShell component, one or several in the same workspace.
View execution results in the Logs tab of the Remote PowerShell component. Each run shows:
Failed executions automatically create alerts in your Inbox.
ConvertTo-Json for structured table formatting and Excel export