Azure Automation: prove the published version before running a runbook
A production runbook for tying source commit, sync job, draft, published version, no-effect test and rollback together before allowing Azure Automation to act.
Read article
Tag
3 articles connected to this technical signal.
A production runbook for tying source commit, sync job, draft, published version, no-effect test and rollback together before allowing Azure Automation to act.
Read articleA production runbook for qualifying a new Azure Automation runtime environment across versions, packages, Hybrid Workers, no-effect tests, canary execution, validation and rollback.
Read articleA production runbook to identify the principal that actually executes an Azure Automation job, bound its permissions, validate with a canary and retain rollback.
Read article