Continuing the topic of automation, PowerShell, and Azure DevOps, in this blog post, I would like to share some ideas on implementing continuous deployment for Azure Automation accounts.
In my last post, I showed you how to use Azure Artifacts to host your PowerShell repository and publish your custom PowerShell modules to it. Here I would like to talk about accessing and using those modules by other Azure Pipelines.
Following my post on embracing DevOps practices in PowerShell automation, I decided to share a sample PowerShell module project with CI/CD pipeline that would put theory in practice.
I already wrote a pretty informative article about using PowerShell DSC for configuring Azure DevOps build servers, and here I would like to share a solution for a more common task – onboarding your servers for monitoring with Azure Monitor.
Despite the wide usage of PowerShell by DevOps practitioners, most automation solutions I come across in organizations are implemented in a quick & dirty way. It is a paradox that automation with PowerShell is often itself completely ignores the practices DevOps encourages to use.