Part 2 : Focus on Deploying with DevOps Pipeline
In Part 1 Azure & Desired State Configuration Part 1/4 - Microsoft Tech Community we saw how we could deploy a web server on a new VM in using a Desired State Configuration file and the Azure Portal. Now we will take this a step further and set up the deployment in a Pipeline on Azure Devops. This will be most likely one the ways you could Automate deployments in your organization and increase collaboration. Completing the below requires knowledge on Azure DevOps in relation to Repo’s and Pipelines. If you are not yet familiar with these please have a look at our learning modules below. Respectfully the focus of this Article is to showcase DSC in DevOps not to explain the entire process.
What will I need?
- Azure Subscription (with Permissions to create resources)
- The Storage Account and DSC Script from Part 1 of this series
- Azure DevOps Organization Service Connection set up to communicate with Azure (Service connections in Azure Pipelines - Azure Pipelines | Microsoft Docs)
- If DevOps Organization has been running in Free Tier you need to request compute by filling in this form (https://aka.ms/azpipelines-parallelism-request more information at Change in Azure Pipelines Grant for Private Projects | Azure DevOps Blog (microsoft.com) )
- ARM template for deploying Virtual Machine (Can be found in Azure QuickStart templates on GitHub - azure-quickstart-templates/101-simple-windows-vm at master · github/azure-quickstart-templates)
In this article we saw how it is possible to create a pipeline in DevOps to deploy an Arm Template that contains a DSC Extension. This means not only can I deploy infrastructure but I can customize the roles and features they deploy with. Stay Tuned for Part 3 where we will be exploring our next step in Automation tooling, Azure Automation Account.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.