Azure service that runs runbooks, scripts that carry out imperative steps such as scaling Azure Virtual Desktop host pools. It is not an infrastructure-as-code tool.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Azure Automation in context, with comparison tables and the common traps.
Terms in this definition
- Agents (classic) API
First-generation Foundry Agent Service API, based on threads, messages and runs. It is deprecated, replaced by conversations and responses, and retires on 31 March 2027.
- Imperative
An automation approach that spells out every step in order, like a run of CLI commands. Declarative templates are the opposite, stating only the desired end result.
- Azure Virtual Desktop
Azure-hosted Windows desktop and app service; to add or remove session hosts in a host pool you use either an Autoscale scaling plan or Automation runbooks.
- Chat message roles
Labels on chat messages: instructions go under system, the person's input under user, the model's previous answers under assistant, and results returned by a called tool under tool (or function).
Related terms
- Automation account
Container in Azure Automation that holds runbooks, configurations and assets.
- Azure Automation State Configuration
DSC service within Azure Automation, due to retire on 30 September 2027. It compiles configurations, assigns them to onboarded machines that are running, and reports back on compliance.
- Hybrid Runbook Worker
Runs Azure Automation runbooks on machines, in Azure or elsewhere, grouped as workers. The extension-based V2 type has taken over from V1, which used an agent and has been retired.
- Runbook
An Azure Automation job script, in PowerShell, Python or graphical form, executed in an Azure sandbox or on a Hybrid Runbook Worker; a typical example resizes a VM at scheduled times.