In this post, I will cover some basic concepts for creating high-quality runbooks in Azure Automation. The concepts covered in this post are: defining input parameters, defining output type, and how to call child runbooks from within a runbook.
Azure Automation allows you to automate the creation, deployment, monitoring, and maintenance of resources in your Azure environment using a highly scalable and reliable workflow execution engine.
My preferred method of deploying to an Azure Web Site is using git, partially because this is a feature I’ve been involved with from the beginning (it’s known as Kudu).
Introduction Azure Automation can be great for managing Azure resources and 3rd party systems, but what if you want to manage Azure Automation’s resources (runbooks, modules, assets, etc), themselves?
While Azure Automation runbooks can be intimidating at first, with a little training they can be easily mastered.
In this blog, I’ll show you how to leverage the Azure Automation service to accomplish a customer requested scenario of truncating tables when a particular database approaches its maximum size capacity.
Fundamentals for runbook management in Azure Automation. The steps to create an Automation account, create or import a runbook, test and publish , manage logging and setup a schedule for starting the runbook.
Running Azure Automation runbooks on a daily basis, you will want to know how your Automation jobs are functioning. If some unexpected issue arises you want to be able to quickly troubleshoot the issue and get your automation back online. This post shows you how.
