Use GitHub Copilot plan mode for cloud operations tasks: Review

The `/plan` command is meant to turn a vague goal like 'set up a staging environment' into a sequence of shell commands. I hoped it could handle at least a basic level of ambiguity. Instead, the exercise here is to feed it a prompt that already spells out the answer. We're asked to generate a plan for 'creating a new Azure resource group named `my-rg` in the `eastus` location and then deploying a new storage account named `mystorage`.'

The plan Copilot spits out is just a bulleted list of the exact `az` commands to do that. It’s not reasoning; it's formatting. I could have written those two CLI commands faster myself. The sandbox gives you a terminal to run them, which works, but the whole thing feels like a demo where the magician shows you the card he's about to pick.

I tried to go off-script. I asked it to plan the migration of a containerized service from one Azure region to another, including networking and database replication steps. It choked. The plan was a generic, high-level checklist you could find in any blog post, with no specific commands or file edits. It completely missed the database part.

So, `/plan` mode seems useful only if you already know exactly what you want to do and just need a glorified to-do list. The module is a fine 90-minute tour of the feature's existence, but it won't give you the skills to apply it to a real, messy ops problem.