Part 1 : Focus on Desired State Configuration in PowerShell
I recently had a customer that requested some demo's on how they could use Azure Automation, Azure Devops and PowerShell Desired State Configuration to Automate their deployments and increase the quality of deployments. In this 4 Part Series I will be going through the different options you have for deploying Desired State Configuration and understanding that it is not some scary, vague concept that only developers can use. If you work in Operations(or any other area working with VMs and Operating Systems), this might be of great benefit ensuring consistent and repetitive deployments of what would have been admin intensive tasks previously.
What will I need?
- Visual Studio Code
- Azure Subscription (with Permissions to create resources)
We just explored how easy it is to deploy a Web Server using our own Desired State Configuration file and the functionality of the Azure portal. There are many more items that can be installed, configured, and even repaired/auto corrected using Desired State Configuration. Some examples can be found:
Official Documentation DSC Configurations - PowerShell | Microsoft Docs
PowerShell Gallery PowerShell Gallery | Packages:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.