Being able to use parameters in PowerShell packages

Also being able to use sensitive parameters in this context would be great. Bonuspoints for KeyVault integration.

please check this as well 

Hi
Parameters actually work behind the scenes but the UI is missing.
So if you have this in Global Parameters:
 

You can add it to the PowerShell script:
 

We can also use Dynamic Parameters which come either from the Schedule itself, or when a user runs it on the portal, they will be prompted for the input:

Here you can either run the Package with no input, and the package would write: nothing in input, 

or you can run it with --@inputparam "some input”

So for example you can in the Schedule add it as an Extra Parameter.

Note that if the Package is running in a Process, you can also pass the parameter to the process and it will be forwarded down.
 

Here is documentation for this feature: Create dynamic packages that accept parameters | Community

Sadly we don’t support KeyVault yet.

​@gunnarsteinn Having a the ability to run different PS script for each UAT would also be great to have.

Good point ​@Stefán Gunnar Jóhannsson. As a workaround you can create a Query Snippet with different UAT and embed that one.

​@gunnarsteinn  I always get an empty output from the parameter:

Global Parameters

Script:
 

Output: