As an Azure Automation runbook author you want to create runbooks that execute reliably in the face of unexpected issues like errors, exceptions, network issues, and crashes. In this post, I will talk about why, when, and how you should use checkpointing in your Automation runbooks.
If you’re a user of Azure Automation, you already know how useful it can be for automating manual, long running, frequently repeated, and error prone tasks that keep your cloud services up and running. You may also be well aware that there are a number of steps required to get Azure Automation set up to talk to Azure using certificate-based authentication. Well we on the Azure Automation and Azure PowerShell team are happy to present you with an easier alternative..
While Azure Automation runbooks can be intimidating at first, with a little training they can be easily mastered. In this blog post, we’ll go into depth on some of the features Azure Automation provides to help you write and use runbooks more effectively, as well as some best practices and common gotchas to help you reach true runbook nirvana.
Running Azure Automation runbooks on a daily basis, you will want to know how your Automation jobs are functioning. If some unexpected issue arises you want to be able to quickly troubleshoot the issue and get your automation back online. This post shows you how.