azurerm_automation_account cost estimation

An azurerm_automation_account runs PowerShell/Python runbooks for process automation — VM start/stop schedules, configuration tasks, orchestration. Cost is per job-run minute: the first 500 minutes each month are free, then ~$0.002/minute. There's also a charge for watcher hours (continuously-running monitors) and optional features like Change Tracking and Update Management (which bill via Log Analytics). 10,500 job-minutes (10,000 billable) is ~$20/month.

It's an inexpensive service, and for many teams the free 500 minutes covers light automation entirely. Cost grows with how much runbook execution time you consume — long-running runbooks, frequent schedules, and watchers are the drivers. A common ironic case: an automation account used to *save* money (auto-stopping dev VMs off-hours) costs a few dollars in job minutes while saving far more in VM compute.

The levers: keep runbooks efficient (shorter runs = fewer billed minutes), avoid unnecessary watchers (they bill continuously), and lean on the free 500-minute grant for light automation. Update Management and Change Tracking ingest into Log Analytics, so factor that ingestion cost separately.

c3x prices the account from monthly job-run minutes as usage, so projected cost can be modelled.

Terraform example

A minimal but realistic configuration that C3X can estimate.

resource "azurerm_automation_account" "main" {
  name                = "ops-automation"
  resource_group_name = azurerm_resource_group.main.name
  location            = azurerm_resource_group.main.location
  sku_name            = "Basic"
}

Pricing dimensions

What you actually pay for when you provision azurerm_automation_account.

Dimension	Unit	What's being charged
Job run minutes	per minute	Runbook execution time. First 500 minutes/month free, then ~$0.002/minute. $0.002/minute (after 500 free) → 10,000 billable min = $20/month
Watcher hours	per hour	Continuously-running watcher monitors bill per hour. Usage-based.

Sample C3X output

10,500 job-run minutes in a month (10,000 billable after the free 500):

azurerm_automation_account.main
└─ Job run minutes   10,000 min   $20.00
                     Monthly      $20.00

Optimization tips

Common ways to reduce azurerm_automation_account cost without changing the workload.

Lean on the free 500 minutes

Up to 500 minutes/month free

The first 500 job-run minutes each month are free — enough for light automation (daily VM start/stop schedules, small config tasks). Many automation accounts stay free.

Keep runbooks efficient

Proportional to runtime reduced

Cost is per job-run minute. Optimize runbooks to finish faster (avoid sleeps/polling loops, parallelize where safe) so each run bills fewer minutes.

Avoid unnecessary watchers

Per watcher hour avoided

Watcher tasks run continuously and bill per hour. Use schedules or event triggers instead of always-on watchers where the use case allows.

Remember the automation usually saves more than it costs

Net positive vs the compute it manages

An automation account that auto-stops dev VMs off-hours costs a few dollars in job minutes while saving far more in VM compute — the net is strongly positive. Don't under-automate to save the trivial Automation cost.

FAQ

How is an Azure Automation Account billed?

Per job-run minute — first 500 minutes/month free, then ~$0.002/minute — plus watcher hours for continuous monitors. Update Management and Change Tracking ingest into Log Analytics (billed there). 10,500 job-minutes is ~$20/month.

Is Azure Automation expensive?

No — it's inexpensive, and the free 500 minutes/month covers light automation. Cost grows with runbook execution time and watchers. Notably, automation that stops idle VMs saves far more than the job-minute cost.

How does c3x estimate the cost?

It's usage-driven, so c3x models it from monthly job-run minutes in c3x-usage.yml (above the free 500). Watcher hours and Log Analytics ingestion for Update/Change Tracking are separate.

Related resources

Azure

azurerm_linux_virtual_machine

A common automation target — e.g. scheduled start/stop to cut VM cost

`azurerm_automation_account` cost estimation