As an IT Process Automation specialist who has been using System Center 2012 R2 Orchestrator and Opalis since 2007, I was very excited by Microsoft’s announcement in 2014 of Azure Automation their new cloud based automation platform. I have been an avid user and follower of Azure Automation since its inception as a pure PowerShell interface, into its graphical authoring capability via the Azure Portal.
Azure Automation is an incredibly powerful tool but it does require a high degree of PowerShell knowledge and necessities a constant internet connection to be able to develop anything.
We realised at Kelverion that this need for PowerShell knowledge and the internet connection would be a stumbling block for Azure Automation adoption at most customers because not every IT engineer mumbles PowerShell in the sleep and certainly the 1st and 2nd line guys don’t speak PowerShell so who is going to support the automation on a day to day basis. So we decided to do something to help.
The all new Kelverion Runbook Studio provides rich graphical authoring of Azure Automation Runbooks without the need for a permanent internet connection. The Runbook Studio is aimed firmly at IT professionals who do not have much experience or knowledge of PowerShell but still want to leverage the power of Microsoft’s new cloud based tool Azure Automation. For experienced PowerShell users the Runbook Studio increases your productivity and makes your solution more supportable in the longer term. On-going maintenance and operation does not need detailed PowerShell knowledge.
The Runbook Studio enables users to create Runbooks using the same script free, code free, graphical authoring approach they have become used to with System Center 2012 Orchestrator. Once the Runbook design is complete the tool will automatically generate Azure Automation Graphical Runbooks for upload and execution from Azure Automation.
The Runbook Studio also provides a workspace to manage all of your Assets across multiple Automation Accounts and even multiple Azure Subscriptions from within one view. Within those Automation Accounts Create, Edit and Delete;
One of the biggest challenges with leveraging PowerShell as an integration mechanism is the need for you as the designer to define exactly what target form, fields, data type and values you want when you come to call the commandlet. This means you need to have a deep working knowledge of the configuration of the target system. The Runbook Studio also has full integration with Kelverion’s growing library of Integration Modules for Azure Automation, these offer the same target system discovery capability you have become used to with Kelverion’s Orchestrator Integration Packs.