Provide guidance on which direction SMA & Orchestrator are going
Enterprise solutions are looking for a 'Complete Package' and we are not being given proper guidance on the future of Workflow Automation within Microsoft. SMA with Workflows is literally, not figuratively, 10x slower than PowerShell executed with a C# engine. For a real life example, review the Accenture/Avanade implementation of their workflow engine. Orchestrator provides the GUI interface that allows for ease of management. PowerShell Workflow does not allow enough flexibility for Master Variable sets when working with multiple client or domains and SMA has scalability issues. So what should we be using to ensure our customers will have dependable, sustainable, solutions that Microsoft will continue to support for the next 2 years? 5 years? 10 years? Companies ask these questions, and we continue to NOT get a solid answer.
I want to make sure that I’m answering all of your questions here so let me know if I’ve missed anything. It sounds like your customers are having performance issues and miss the GUI offered by SCO. It also sounds like you are looking for guidance on where you should tell customers to look for the future. Any other questions?SMA just released PowerShell script support in TP5: https://blogs.technet.microsoft.com/orchestrator/2016/04/28/powershell-script-runbook-support-in-system-center-service-management-automation-2016-sma-part-1/. Since scripts are not compiled like workflows, the perf issues that you were seeing will go away if you convert your workflows to scripts. This also reduces the learning curve since PowerShell scripts are more well-known than Workflow.
Automation’s new features will show up first in Azure Automation and then we bring functionality to SMA. This means that if customers want the most up to date capabilities or want to see their feedback more rapidly integrated to the product, you should encourage them to look at Azure Automation. If customers cannot use hybrid for their on prem workflow, then we would encourage them to use SMA. If customers want to use a graphical representation of their scripts, then you should direct them to Azure Automation. If there are specific features that you feel need to be brought to SMA, please let us know.