I've contracted in places where cmd is blocked, but Powershell is not. The mind boggles.
(For those cursed to work in Windows enterprise land, most of what is being talked about here is that Powershell is essentially .Net, e.g. '$DateTime = New-Object System.DateTime -ArgumentList 2015, 10, 10')
I have the experience of having worked in UNIX shops where $HOME was mounted noexec, everyone got development rights over access groups and we only got to use official IT tools.
Many are spoiled by having their own devenv nowadays.
Ironically cloud computing is going back to those days, where the cloud IDE and shell only allows for IT validated tools.
I get that most of us live in a land of "Of course I have an IDE and compilers / REPL" at work.
You know what IDE and compiler IT can't take away? And the last option that's always available at any company?
Excel.