Hey everyone! I'm facing a bit of a challenge with Azure Runbooks. The default source control integration from Microsoft only supports PowerShell 5.1, which isn't ideal since we're using PowerShell 7.4 and Python in our Runbooks. This lack of integration means that tracking changes to our runbooks has become difficult. I'm hoping to hear about any experiences or workarounds others might be using to get source control functionalities or something similar working. Previously, we ran our scripts on local Active Directory via task scheduler for dynamic user assignments and used custom connectors to systems like Workday. Since migrating to Azure, we've lost access to that source control feature, and it's proving to be a headache. Any tips or suggestions would be greatly appreciated!
3 Answers
Honestly, if you're looking to avoid the headaches, consider running your scripts directly from GitHub Actions instead of relying on Azure Runbooks. It could streamline your workflow significantly.
One alternative could be to reverse the workflow a bit. Instead of having Azure Automation pull from source control, consider setting up an Azure DevOps or GitHub Actions pipeline that pushes updates to your Automation instance. This way, you can manage your code in GitHub while automatically deploying the latest versions to Azure.
You might want to look into using Logic Apps or Function Apps. If you must stick with the Automation Account, think about using it as a trigger for those apps. They can offer more flexibility and integrate well with Azure DevOps processes.
I totally agree! Function apps are super flexible and work nicely with Azure DevOps.
That's an interesting approach! I don't have much experience with this setup—can you point me to any documentation that could help me configure it?