A utility script died on a fresh Windows 11 box. wmic bios get serialnumber, gone, and the DISM command that puts it back stops working this month. The one-liners map onto Get-CimInstance cleanly. The for /f blocks wrapped around them do not.
Pester 6.1 shipped, so I checked my Copilot standards against an install instead of the release notes. Four claims no longer held. Two aren’t in the announcement at all, and one example from the release notes doesn’t actually run.
A fresh Okta trial org is empty. The license caps you at ten active users, so I built a lab where 8 awkward users plus everything Okta doesn’t cap does the work. Seeds in 2 min, tears down safely.
Updated my PowerShell Copilot Standards repo and realized every other project was still on the old instruction copies. So I built a GitHub Actions workflow that mirrors them weekly and opens a PR when they drift.
One PowerShell module that talks to SecretStore, Azure Key Vault, AWS Secrets Manager, Bitwarden and CredMan through the same commands, so hybrid environments stop needing five different scripts.
My AD test environment module still had service account passwords sitting in plain text. This adds PowerShell SecretStore for setup, storage and retrieval, without making the lab harder to spin up.
A PowerShell module that fills a lab domain with a thousand-plus realistic users, groups and OUs in about a minute, and tears them back down cleanly when you are done.
A real path traversal validator, tested end to end with Pester. The test patterns, the edge cases that actually matter, and coverage that holds up once the function ships.
I went looking for a real use case for PowerShell classes and found one: blue/green patch deployment, with zero downtime and a rollback that takes effect immediately.
Copilot writes whatever PowerShell it feels like unless you tell it otherwise. Encoding your team’s standards as custom instructions so generated code matches your style, error handling and testing rules.