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
azure-automation
8 articles connected to this technical signal.
Azure Automation: rotate a webhook before the production trigger expires
A production runbook for inventorying Azure Automation webhook consumers, introducing a second endpoint, proving one execution per event, cutting over and revoking the old URL with a tested rollback.
Read articleAzure Automation: validate a runtime migration before cutting production runbooks over
A production runbook for qualifying a new Azure Automation runtime environment across versions, packages, Hybrid Workers, no-effect tests, canary execution, validation and rollback.
Read articleAzure Automation: prove the runbook identity before broadening RBAC
A production runbook to identify the principal that actually executes an Azure Automation job, bound its permissions, validate with a canary and retain rollback.
Read articleAzure Automation: diagnose a Hybrid Runbook Worker that stops picking up jobs
A production runbook for separating queueing, heartbeat, extension, network, capacity, identity and runtime failures before retrying a Hybrid Worker job.
Read articleAgentOps: validate the Foundry automation handoff before a production action
A production runbook for qualifying the handoff from a Microsoft Foundry agent to Azure Automation, AWX, Azure DevOps or an MCP tool with contract, identity, traces, dry run, human validation and rollback.
Read articleAzure Automation: diagnose a runbook before rerunning the job
A production runbook for qualifying an Azure Automation failure with managed identity, parameters, modules, Hybrid Worker, webhooks, logs, validation and rollback before rerun.
Read articleAzure Automation: validate a scheduled runbook before it changes production
A production runbook for qualifying a scheduled Azure Automation job with trigger, managed identity, parameters, dry-run, logs, validation and rollback before allowing real action.
Read article