Skip to main content
  • EN

Are there any plans to introduce improvements to the current PowerShell App in FS Orchestration.  The current one uses an inordinate amount of system resources and is essentially useless for any non-local work.

My team has an established library of PowerShell-based automation scripts which simply cannot be used with the current app.  Why can’t we leverage these instead of needing to essentially recreate the workflows via your AD/Azure apps?  I see many have had to resort to using Azure Automation webhooks (which isn’t a bad idea) but wonder why this poor PowerShell implementation has received no attention despite the ravingly bad reviews (see Reddit).

Hello @anthony.martin I also have struggled in the past to get a solid implementation and workflow using the powershell orchestration application. It has, however, helped me solve some difficult onboarding processes, so it does have its benefits. One thing we have utilized is the ability to store the scripts on the server, and call the scripts using the execute command action of the orchestration application. Not sure if this would help your use case but just thought I would share that process. Our biggest pain point is passing credentials in a secure manner. Still trying to figure out an easier way to do so.

Anyway, hope that gives a little insight, and I will second your testament to the need to improve this application.

Take care!

Terms of Use