<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Automation on The Provision Notes</title><link>https://provisionlogs.dev/tags/automation/</link><description>Recent content in Automation on The Provision Notes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 15 Sep 2026 10:00:00 +0700</lastBuildDate><atom:link href="https://provisionlogs.dev/tags/automation/index.xml" rel="self" type="application/rss+xml"/><item><title>Automating VM/AKS/PostgreSQL/SQL MI Start-Stop Schedules with Terraform + Azure Automation</title><link>https://provisionlogs.dev/posts/azure-automation-account-autostartstop-terraform/</link><pubDate>Tue, 15 Sep 2026 10:00:00 +0700</pubDate><guid>https://provisionlogs.dev/posts/azure-automation-account-autostartstop-terraform/</guid><description>Turning a manual Azure Automation Account setup — 8 PowerShell runbooks, tag-driven start/stop logic across VMs, AKS, PostgreSQL, and SQL MI — into Terraform, including the two provider quirks that don&amp;rsquo;t show up until you actually try to automate it.</description></item></channel></rss>