Azure DevOps

Post 19 built an automation practice around PowerShell , modules, DSC v3, CI/CD pipelines. For many organizations, that’s enough. PowerShell is native, it’s free, it covers 100% of Hyper-V functionality, and your Windows team already knows it.

But some organizations have standardized on Ansible for configuration management across Linux and Windows. Others use Terraform for all infrastructure provisioning. And some want both , Terraform for creating resources, Ansible for configuring them. The question isn’t “which tool is best” , it’s “which tool fits your team, your existing investments, and your Hyper-V use case.”

“PowerShell Returned to Its Throne” isn’t just a series tagline. It’s the architectural reality.

Every post in this series has used PowerShell for configuration, validation, and management. But there’s a difference between running scripts manually and building an automation practice. If you’re honest with yourself, most of us do the same thing: write a script, run it, tweak something, run it again, save it in a folder called “scripts-final-v3-FINAL,” and hope we remember the parameters next quarter.

So recently I have been dragged kicking and screaming into the security world. Well, not really dragged, if you know me I am a large guy and it would be more like fork lifting me kicking and screaming? Anyway, I actually love working with security products like Microsoft Sentinel, Defender for Cloud and the many other Defender for.. Products Microsoft offers, along with Identify solutions like Entra Permissions Management and more.