Is there a use case for Azure Automation Runbooks?

  • I recently started a project where I needed to develop serverles automation for Azure VMs that have no inbound access.

    I started with Azure Automation, but I switched over to Azure DevOps when there were version controlled artifacts I needed to use and it didn't seems like there was a sensible way to deal with that.

    So far, everything I had been doing in Azure Automation Runbooks has been doable or even easier and more logically designed in Azure DevOps. So that got me thinking, is there even a use case for Automation Runbooks?

    As a side note, Azure DevOps is the only MS product I don't hate at the moment.

  • There is overlap between them both, MS knows this and it's on purpose. MS is full steam ahead on developing Azure Automation, for example with DSC, as well as full steam ahead with others.

    I use Runbooks for simply scheduling scripts that need to run. It's excellent for that. These types of things don't require the responsiveness that Function Apps provide, and costs less.

    I use Function Apps for more complex tasks and those that require webhooks or other triggers such as gates from Azure DevOps.

  • This might help too, even though it may be a bit dated:


  • Yeah, I guess I could see if for scheduling less critical stuff. It does seem like their plan is to flesh out Automation with more polished tools, but Runbooks seems pretty lacking in features.

    I did look I to Automation DSC, but I kind of doubt that's ever going to be a good idea for Linux. Ubuntu 16.04 is supported but not 18.04. And it sounded like on Linux, you can't have the Azure Monitor agent and the PS DSC agent installed on the same system.

Log in to reply