Offline creation and management of Microsoft Azure Automation Runbooks
The all new Kelverion Runbook Studio provides rich graphical authoring of Azure Automation Runbooks with a full offline authoring capability.
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. Ongoing 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 Orchestrator.
Once the Runbook design is complete the tool will automatically generate Azure Automation Graphical Runbooks for upload and execution from Azure Automation.
With the release 2.0 Runbook Studio now provides a full offline cache of your Azure Automation assets and Runbooks so you can continue to build and develop content whilst not connected to the internet, you can also build content offsite and then go onsite to upload content into the customers Azure Subscription over their secure VPN connection.
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 and Orchestrator SMA. These Kelverion Integration Modules offer a unique discovery API which allows the modules to interrogate the target third party system and dynamically discover its configuration and setup, in exactly the same way that Kelverion’s existing Orchestrator Integration Packs operate.
At Runbook design time the Runbook Studio hooks in to this discovery API and dynamically configures the commandlet inputs and outputs based on the data returned from the target system. For example when you want to create an Incident Ticket in ServiceNow the Integration Module will query ServiceNow for a list of available tables. Once you select an Incident Ticket table, the Integration Module queries the table and automatically configures each field in the Incident Table as an input parameter for use in the Runbook Studio.
As a designer you no longer need to be an expert in the target system to build Azure Automation Runbooks, significantly reducing build time and increasing supportability of your automation solutions.
You not limited to just using this smart discovery offered by the Runbook Studio with Azure Automation Runbooks, once you have configured your create Incident Ticket Activity in the studio you can right click on the activity and view the PowerShell Code of the activity commandlet. You can copy this code into any PowerShell script or SMA Runbook and proceed the code with an import module command to load the Kelverion Integration Module and you can then create the Incident Ticket from within a PowerShell script.
Come along to our stand 2067 at Microsoft Ignite 2017 and see the Runbook Studio for yourself or contact email@example.com for a demonstration.