Is it possible to run a PS script module in a workflow but have it run as the user who started the workflow, not the AR service account?
In the "run-as" setting for the workflow, we have it set to run as the user, not the AR service account. Also in the script, we are using the -proxy parameter but when we look at logs, its still using the AR service account to modify the AD groups. We can see the workflow is indeed getting started by the user account, but the script still runs under the AR service account. We don't want this script to work unless the user running the workflow has rights to modify the groups.