Please consider adding deployment type of 'Powershell Script' for application deployments.

SCCM has the ability to adjust the Powershell Execution Policy for it's scripts only. This allows powershell to be used for things like detection methods.

However, if you want to actually install something using powershell there is no mechanism to allow this to happen. The only type of installation that you can used to run powershell is 'Script'. Since this isn't known to SCCm as powershell, it does not obey the client configured Execution Policy.

This causes problem when attempting to deploy applications like the new Edge based on Chromium using the inbox sccm deployment method. In order to make this work, the client execution policy must be adjusted, which an SCCM admin may not have the ability (or permissions to do).

If SCCM knew that we were running a powershell script instead of "generic script", it could execute the powershell script using the SCCM policies instead of those defined on the workstation.