With Microsoft Azure you are finally able to utilise the Cloud to scale your infrastructure according to your needs. Virtual machines are popping in and out of existence at your whim. Today it’s collaborating with SharePoint, tomorrow you’re building databases in Oracle; a cornucopia of business applications await your every command. Furthermore, all this is accessed from any place, anytime, because the Cloud is wherever you need it to be, right?
Well, the Cloud is actually wherever you have a reliable Internet connection. And despite Azure’s graphical interface, you’d still better be well versed in PowerShell to get the most out of its automation capabilities.
So along comes the new Runbook Studio, a bridge between Azure Automation’s powerful processing portal and the versatile, integrated family of automation packs and modules that Kelverion is best known for developing.
Here are four big ways Runbook Studio makes Azure Automation even better:
1. Taking it offline
You need to author a Runbook, and it’s a tricky one. Of course, you can log on to Azure Automation and plunge in, but maybe you’re on the road, and while you can find a wifi connection here and there, you can’t rely on it long enough to shepherd your project from start to finish.
No worries. Runbook Studio allows you to build Runbooks offline to your heart’s delight. Only after you’ve dotted i’s, crossed t’s, and ironed out the wrinkly bits, do you tap into Azure Automation and upload your Runbooks with confidence.
2. One screen to rule them all
You’re likely managing test and production environments with multiple Azure Automation accounts and subscriptions. With Runbook Studio you can manage all your Assets from within a single workspace. Let’s take a look:
3. Not a PowerShell expert? Not a problem.
So maybe you mumble PowerShell commands in your sleep, but not every member of your team, now and in the future, can say the same. Wouldn’t it be nice if you could create Runbooks in a script-free, code-free, graphical authoring environment that is easy to maintain? You know how effortless System Center 2012 Orchestrator has made writing Runbooks, and it’s the same approach here: fast, simple and accessible.
Bonus: Once you complete your designs in Runbook Studio, your work is pretty much done, as the tool will automatically generate Azure Automation Runbooks for upload and execution.
4. Configuring Runbooks for any environment
One of the trickiest aspects of using PowerShell as an integration tool is the need to define what form, fields, data type or values you want when you come to call the commandlet.
Runbook Studio has your back with Kelverion’s library of integration modules for Azure Automation, which offers a discovery API that dynamically configures the commandlet inputs and outputs based on the target system. So just like that, you’re an expert in every third-party system you’ll be feeding.
Can it really be this simple?
Yes, it can. To put it all together, Runbook Studio allows you to plan and author your Runbooks offline, access an ultra-friendly user workspace where you can view your array of accounts and subscriptions, bypass a need for PowerShell expertise, and sit back while the tool uploads your Runbooks for both Azure Automation and all the third-party applications you’ll be integrating.
Great just got better.
For more information on this and our other posts on the Kelverion Runbook Studio visit