Powershell steps are executed with the -noprofile powershell option.

This is not always desired. In our case we add setup and configuration tasks to the default profile. A workaround if to add ". $profile" at the beginning of each powershell step but this adds overhead to all steps and is a maintenance burden.

Additionally, the powershell plugin for jenkins doesn't use -noprofile, so it would be good to preserve that behaviour to make the switch to the jenkins pipeline seemless.

Suggestion:

Make the hardcoded command line to powershell configurable globally, so that  a "use default profile" global checkbox can drive this behaviour.