8 Ways to Screw Your Azure Automation
summary
Concrete takeaways: eight common failures and how to avoid them including secrets in code versus using Azure Key Vault and managed identities; limits like 10 automation accounts per region per subscription; the runbook name is the unique identifier so renames break syncs (runbook name is its unique ID); GitHub integration requires public-access Automation and is one-way (GitHub → Azure Automation); hybrid workers fetch jobs and cannot use user‑assigned managed identities so test modules and modules versions on workers; add alerting (Log Analytics/email) and source control.
AI-written summary · about
chapters (11)
- 0:00Azure Automation mistakes
- 2:59Insecure credential storage
- 9:04Single identity risks
- 14:03Runbook monitoring gaps
- 19:05No source control
- 25:50Hybrid worker challenges
- 31:53Hybrid worker limits
- 38:56Naming and limits issues
- 42:08Logging and efficiency
- 47:11Module and environment neglect
- 51:13Additional ways to break Azure Automation
related talks
20mThe 10 Most Common Azure Mistakes (And How To Fix Them)
47mBest practices for automating Azure with PowerShell...
47mA revival of Azure Automation
42mAzure DevOps security - Lessons learned
21mTop Ten Terraform Trip-Ups
25mSecuring Your DevOps Transformation
01h 01mKeep your nose out of it. Denying yourself access to production
47mAutomate Problem Solving with PowerShell, Azure Automation, and OMS