Modern business process is essential for transforming organizational productivity in Microsoft 365. Since the release of SharePoint workflows, Microsoft has evolved workflow orchestration to not only...
Published Jul 06, 2020
Version 1.0
Blog Post
This is an astonishingly myopic and damaging change, and with little to no notice, and a slap in the face to the dozens of client's we've convinced to migrate off on-premises into the Microsoft Cloud.
I have 50-100 clients with between dozens and hundreds of critical workflows each using the 2010 Foundation.
It's still far and away the easiest, quickest method of setting an object's permissions programmatically based on metadata.
Quite aside from my team's current project load, we now have 115 days to re-engineer thousands of workflows in PowerAutomate or Logic Apps?
Simply not viable, we'd need closer to 2 years to gear up for this, even with additional hiring.
Consider this real, edge-case scenerio; we've recently deployed a little over 7,000 lists from a template for a big client, recently migrated to SPO. Each with a 2010 metadata tagging workflow.
Recreating this in LogicApps will require 10 connections and 10 actions, for an instance run cost of €0.00128, which seems reasonable.
However, as we can no longer trust that 2013 workflow won't be disabled with 3 months' notice, we can't have a 2013 WF HTTP request a LogicApp and because LogicApps/PowerAutomate do not have true Triggers or fire on Event Receivers, checking those lists every 2 minutes for changes would require 1.8 billion annual runs.
In a worst case scenario he annual Opex cost of thus one workflow solution would go from €0 to €2.3 million overnight!
That would be if I had time to do the remediation, which I don't, so they'll just fail.
Thanks a million guys.