By deploying infrastructure DevOps style, as code, for example, by using Desired State Configuration, you will increase the traceability of your deployments. This is very important in order to see what happened during a build, which components are deployed on a VM, and so on.

Usually, when we're talking about DevOps we need to talk about continuous integration and continuous delivery/deployment. In a CI/CD pipeline, the CI server or orchestrator usually just starts a build script. This is where PowerShell comes in handy. The build script controls the flow by running tests, creating build artifacts, and publishing those tests and artifacts to the CI system.

By using PowerShell, we can easily improve the traceability in the pipeline by using verbose, warning, and error channels, running great Pester tests, and leveraging the logging capabilities of (Windows) PowerShell 5+.