As an IT business analyst, have you ever been involved in the creation of a runbook?

As an IT Business Analyst, I have worked on Runbook.

In a computer system or network, a runbook is a compilation of routine procedures and operations that the operator carries out. System administrators in IT departments use runbooks as a reference. Runbooks can be electronic or in physical book form.  Typically, a runbook includes procedures to begin, stop, supervise, and debug the system. It may also describe procedures for handling special requests. An effective runbook allows other operators, with predetermine expertise.

Depending on their functions, runbooks can also be General runbooks. For routine IT department activities, such as reviewing audit logs, performing daily backups or monitoring system . Specialized runbooks. For more complex operations processes, like disaster recovery , network outages, DevOps, etc

The runbook should take the best possible solution  for the operator. Once we determined the procedure to be documented for your runbook, you can begin writing it in detail. There are a few things to remember when creating your new runbook: It should be flexible and adaptable to changes in our systems and applications

An Automation Account can have a runbook with multiple schedules set up at different times with different parameters. These schedules are then used to drive the execution of with the specified configuration.

I need to unlink/relink the schedule. As soon as I do that, the schedule will reset all the existing parameters I had. That means I need to edit all the parameters again. With that said, I’m sure I know the pain of resetting those parameters each time, especially if I am debugging a new runbook with many parameters. This post will show you how I used a PowerShell script to update my schedule parameters without dropping them.

There are three types of runbooks:

1. The Manual runbook containing step-by-step instructions to be followed by an operator.
2. The Semiautomatic composed of a combination of manual and automated steps.
3. The Automatic requiring no manual intervention.

Updating Existing Schedule Parameters

Until Microsoft simplifies the process of updating existing schedules, I can make use of a PowerShell script to update the schedule. To run the PowerShell script in this post,

I need to have the Microsoft Azure PowerShell module installed.

The PowerShell script takes several functions.

• Subscription – is the subscription GUID of the subscription which containing the runbook schedule.
• AutomationAccountName – It will display name of the automation account;
• Resource Group – It will display name of the resource group with the runbook schedule;
• Runbook Name – Runbook is the name of the runbook holding the schedule;
• Schedule Name – Schedule Name is the name of the schedule you want to edit;
• Search Parameter –Search Parameter is the name of the parameter you want to modify;
• NewParameterValue – New Parameter is the property or new parameter you want to use for the Search Parameter.

• Resource Group – Resource Group is the display name of the resource group with the runbook schedule;
• Runbook Name – Runbook Name is the name of the runbook holding the schedule;
• Search Parameter – Search Parameter is the name of the parameter you want to modify