If you’re familiar with Azure Automation, you’re probably aware that PowerShell is the fundamental technology that makes Azure Automation great. But PowerShell itself is great due to its extensibility through PowerShell modules.
Posts By: Joe Levy
Introducing the Azure Automation Script Converter – if you import a PowerShell script with no PowerShell Workflows in it, we’ll now attempt to convert the PowerShell script for you to PowerShell Workflow, so it will be able to run with little to no manual changes as an Azure Automation runbook.
If you’re a user of Azure Automation, you already know how useful it can be for automating manual, long running, frequently repeated, and error prone tasks that keep your cloud services up and running. You may also be well aware that there are a number of steps required to get Azure Automation set up to talk to Azure using certificate-based authentication. Well we on the Azure Automation and Azure PowerShell team are happy to present you with an easier alternative..
By now you’ve probably had a chance to experiment with all the great features of Azure Automation through the Azure Portal. Now what if I told you, you could do all these things and more easily and programmatically from the command line? Whether you want to use Azure Automation completely headless, or you’re just looking to script a few key actions like bulk runbook import, the Azure Automation cmdlets are for you.
While Azure Automation runbooks can be intimidating at first, with a little training they can be easily mastered. In this blog post, we’ll go into depth on some of the features Azure Automation provides to help you write and use runbooks more effectively, as well as some best practices and common gotchas to help you reach true runbook nirvana.
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.