I'm seeking alternatives for integrating GitHub with Azure Runbooks since the default source control integration Microsoft offers only works with PowerShell 5.1. We're currently using PowerShell 7.4 and Python in our Runbooks, and it seems we can't connect them. I'm interested in any experiences or workarounds that others have found effective, as it's challenging to track changes to our runbooks now. Previously, we managed our scripts through local AD with task scheduler for dynamic user assignments and custom connectors like Workday, but upon moving to Azure, we've lost that source control capability. Any help or tips would be greatly appreciated!
1 Answer
Have you considered flipping the model? Instead of having Azure Automation pull from source control, you could set up your Azure DevOps or GitHub Actions pipeline to push to Automation. This might streamline your workflow and keep track of changes more effectively.
That's an interesting approach! I'm not very experienced in this area though; do you have any documentation or references for a setup like that? Thanks!