Can we use GitHub Actions for Azure Automation CI/CD?

Question

Using Azure Automation, we want to build automated solution for examples below,

1. making M365 group
2. making SharePoint sites and relevant settings

I'm new to Azure and GitHub, so Id like to know if we can use GitHub Actions for these automated flows, and also if GitHub Actions covers version management and the previous version can be released?

Answer 1

Hi,

The question is a little bit unclear and very general. Azure Automation and GitHub Actions are two different services which overall serve two different purposes. GitHub Actions is for CI/CD where Azure Automation serves more like automation operational tasks. The way you can use GitHub Actions for Azure Automation is for example deploying the resources for Azure Automation using tools like Bicep, Terraform, Az PowerShell, az CLI, etc. Of course you can also use GitHub Actions to start Azure Automation runbook as well but I am not sure what is the valid scenario for that as you can easily do the same tasks within GitHub actions and not use Azure Automation runbooks at all. All the automation will happen inside the GitHub Actions. GitHub Actions is CI/CD so it does not do version management. The repository part (git) of GitHub can do version management. Version management in Git (GitHub) is not out of box experience but more of how your code is structured and what kind of Git tagging and branching strategy you have. So with GitHub you can create strategy of how you manage versions of your runbooks or resources for example and with GitHub Actions you can automate the deployment of those versions in way where it is possible to revert previous version. All this is custom and requires knowledge in Git, CI/CD and the deployment tools you will use (Bicep, Terraform, Az CLI, Az PowerShell or something else).

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.