The few of us that have started working with Azure Automation and/or SMA have probably noticed the lack of functionality that would equal a monitoring activity in Orchestrator.
I’ve seen some solutions which consist of a Runbook being set in an infinite loop with a sleep timer at the bottom.
In practice this method would replicated the desired functionality, that is, until the Runbook hits the maximum runtime value and kills the process. If you’re using Azure Automation this would also mean that you’ll be consuming Automation Minutes. 24/7.
What you’ll want to do with Azure Automation and SMA is to work with schedules to mimic a monitoring activity. And this can be a hassle to manage… Unless you’re using the right tools! 🙂
First we’ll want to create the required schedules. In 99% of the cases I work with hourly schedules at different minute intervals and I create them with the following script found at Technet Gallery.
If you use the “-Verbose” parameter you’ll get output on the schedule creation process.
And lastly we’ll want to assign Runbooks to the required schedules so the Runbook executes at the right time with the following script:
By piping to “Out-Gridview -Passthru” I can easily filter all the schedules and select the ones I want. Oh, and they script writes the intervals into the Description property of the schedules. This makes life a bit easier if you want the Runbook to execute, for example, every 5 minutes.
The result would look something like this in the Azure Management Portal:
I hope this helps you to manage your Automation Runbooks in a more efficient way and lower your Azure bill!
Again, the script can be found at: https://gallery.technet.microsoft.com/Generate-Azure-Automation-1dab9193