The Azure VM Cmdlet You’ve Been Ignoring: Effective Post-Deployment Scripting

Gijs Reijn
7 min readMar 9, 2024
Freepik

Probably the first one that popped into your mind was the Invoke-AzVMRunCommand

… but no, that’s not the cmdlet I’m talking about, as there are already plenty of articles out there that use this cmdlet.

Actually, that’s also how I first stumbled on that cmdlet, when reading the article from Thomas Maurer where he was running multiple scripts against multiple Azure Virtual Machines (VMs).

Although he describes the ability to run the command simultaneously on several Azure VMs, the cmdlet itself doesn’t support executing multiple scripts at once.

If you try to do so, you’ll be presented with a lovely message.

Figure 1 — Running Invoke-AzVmRunCommand multiple times

Yeah, patience is a virtue of course, but when you’re dealing with serious heavy-lifting tasks and need to run multiple scripts at the same time, it could be a real career-saver. I know, it might sound a bit overdramatic, but you see the point I’m making.

So, can give us the cmdlet already? It’s actually in the same module, and you only have to switch the word Invoke to Set.

--

--

Gijs Reijn
Gijs Reijn

Written by Gijs Reijn

Sharing my experience through the IT world. Tutorials, guides, and opinions. Follow my newsletter at: http://eepurl.com/i1hSUw

No responses yet