Migrate runbook with assets to another Automation Account
It would be nice to have the option to migrate a runbook to another Automation Account. With a user action, on whether or not assets and stuff, associated to the runbook, should be moved too.
I see it useful in a Test / Prod environment. We want multiple users to be able to develop runbooks, but only in a controlled environment. And then move it to our production Automation Account when done.
Thanks for posting this suggestion. We do have integration with source control which would easily enable you to sync your runbooks from a dev to prod account easily. https://azure.microsoft.com/en-us/blog/azure-automation-source-control-13/
Are you asking to be able to pick a runbook and supporting assets and then move them to another account? Would being able to group them together and export them as an ARM template work as a potential solution or is your preference to have a tool in the UX to do this?
It would be useful to actually being able to copy/clone the whole automation account. The reason is that an automation account can also have some libraries that have been uploaded. For example, in one of my auto accounts I updates Powershell Azure RM to version 1.5. The updating process is very long and slow, and therefore repeating it on several accounts is very time-consuming.
Got it. Thanks for the details here Morten!
Morten Christiansen commented
The possibility of grouping and exporting as an ARM template would work. To be able to group multiple runbooks and assets would be ideal.
A runbook should also be able to be member of multiple groups if needed.
Powershell Cmdlets would be preferable - that way we can create an engine for approval of runbooks to production.