What is usually do is just, delete everything. Then you will need to select your repository and select “Starter pipeline”Īnd then you should be shown a yml file looking like this: In my case, I have my repository stored in Azure DevOps Then select which repository you want to use your pipeline with. To create a new pipeline in Azure DevOps you can go to “Pipelines” –> “New Pipeline” This file is the pipeline created in Azure DevOps. The last file in the repository is the azure-piipelines.yml file. This script is used by the pipeline, so this will handle the functionality of actually connecting to Azure and deploying the runbooks. Inside the scripts folder, I have created a single script called run.ps1.

The way I have created this pipeline the runbook folder and script must have the same name. This folder will contain a folder with the exact name of the runbook script, and inside this folder, I have the script. In my repository i have create a folder structure like so: Root I have created a repository in Azure DevOps, this could just as well be on Github, the procedure is more or less the same. In this blog post, I am going to demonstrate how you very easily can set up a pipeline on Azure DevOps, which uploads your Powershell scripts into Azure Automation whenever to push into the main branch. You could also just set up a pipeline which when you push into the main branch, automatically uploads the script into Azure. Here you could set up a pipeline that used PSScryptAnalyzer and Pester, for analyzing and testing your script before it gets uploaded to Azure. With the possibility to use Source Control you also get the possibility to set up a pipeline for automating the deployment of Runbooks to Azure. One of the best things about running the scripts in Azure Automations is that you have the possibility to upload your scripts to Azure through Source Control, such as Github or Azure DevOps. I find Azure automation to be a great solution for managing and running your automation, instead of having them run on a server with scheduled tasks. I use it for both my Azure environment but also my on-premises environment. I use Azure Automation for orchestrating alot of my Powershell automation.

Choosing to either synching the existing runbooks or deploying the new runbooks.

Finding the Automations Account name and already existing runbooks.

Creating the run.ps1 script to use with the pipeline.

Original ps1 controller