TIP: Keep your Azure Automation runbooks healthy across PowerShell module updates

Here’s a quick tip that may help you ensure you’re protect yourself from a problem that happens occasionally.

Problem: I had a runbook that was broken when the PowerShell modules in the store were updated.

Solution: What can you do to prevent this problem? One thing you can do to protect yourself against breaking changes in new versions of PowerShell moduels is to configure your runbook to run on a schedule. Once schedule is created, that runbook will always run with the modules that were in the store at the time of the schedule creation.

Get a deep dive on Azure Automation in our comprehensive book on the Microsoft Operations Management Suite (OMS), which is available free on the TechNet Gallery or if you prefer, for a small price in paperback and Kindle formats on Amazon.com.

Leave a Reply