At this year’s PSConfEU, Jeffrey Snover — the creator of PowerShell — gave a session called Navigating the AI Revolution. One idea stuck with me: engineering is how we take something that isn’t perfect yet and make it useful anyway. With AI specifically, the answer isn’t to trust it blindly — it’s to build verification layers around it. Validate the output. Trust, but verify.

That hit a nerve, because if I’m honest I’m a bit of a perfectionist and a bit of a control-freak. AI velocity is real and I want it — but handing work to something that’s confidently wrong sometimes goes against every instinct I have. So I’ve been trying to let the reins go a little, and the thing that makes that bearable is the same thing that’s always made me comfortable shipping code: tests. This post is about one testing layer in particular — Playwright MCP — and how it lets me let go without flying blind.

Microsoft Desired State Configuration v3.2 was released at the end of April, and unlike the usual point release, this one brings substantial changes. First-class Windows resources without the PSDSC adapter dance, an experimental Bicep ↔ DSC bridge, and a properly grown-up expression language.

If you haven’t caught up on DSC v3 yet, start with my DSC v3 primer — this post assumes you know what dsc.exe is and how a v3 configuration document is structured. For everything else that happened in PowerShell-land over the same window, see the April roundup.

Microsoft DSC v3.2 was released at the end of April and is genuinely the most interesting thing to happen in DSC-land in a long time. Before going into what’s new in v3.2 though, it’s worth a primer — DSC v3 has been around for a bit, but if you tried it in v1.1, bounced off it in v2, or just never made the time for it, the landscape now is meaningfully different. Here’s the quick catch-up.

For everything else that’s happened in PowerShell-land recently, see the April roundup.

PowerShell 7.6 GA in March was the headline of the spring, and the new DSC v3.2 release (covered separately, with a DSC v3 primer alongside it) is the most substantial follow-up since. A few other things shipped in PowerShell-land in between that are worth a quick sweep — a candid release postmortem, the first 7.7 preview, an MSI deprecation announcement, the LTS patch wave, and a couple of community notes.

Microsoft just announced the public preview of the Azure Resource Manager MCP Server — a remote, hosted MCP server that lets AI agents talk to Azure infrastructure through ARM. At this year’s MVP Summit I got proper hands-on time with this: a lab session walking through it, followed by preview access on my own tenant so I could poke at it with real resources for a while. Now everyone else gets to do the same.

Bit of a departure from the usual PowerShell and Azure content — Anthropic just released Claude Opus 4.7, and while this isn’t directly PowerShell-related, AI is changing how a lot of us work. It’s something I plan to dive into more on this blog going forward.