11 Sample Runbooks to Help You Build Your Own

2 weeks ago, I posted an article regarding Automating Azure with runbooks. I got some really good feedback and some good questions I decided to address. But first, as usual, if you have not had any exposure to Azure. I recommend the following MVA modules as primer.

Q: “Why not use PowerShell and DSC extension?”

A: In order to provide high availability of workflow execution, Azure Automaton executes PowerShell code in different PowerShell sessions, in different processes, and even on different machines. In this context, replacing Automation Assets with regular mechanisms available in pure PowerShell workflow is very challenging.

Basically, you get the same benefits as straight PowerShell with added benefits that the usage of assets gives:

Centralized management of constant values

Sharing of assets (Variables, Connections, and Credentials) between jobs. In PowerShell you can do this but have to invent your own mechanism.

Secured management of credentials and connections

Out of box scheduling capability

Q: How do I create a new runbook?

A: Whatever tool you use to write your scripts is fine to create runbooks. you can use the Integrated Scripting Environment.