New white paper – “Transforming business process with Microsoft 365”

Chris McNulty Again, I raise the same concern with Flow. Do we really think it's a good idea to tie business process automation to the credentials of an individual user rather than to the site or list? Yes, we can share a Flow, but even a shared Flow is still tied to the credentials of a SINGLE user.  Life happens. People change jobs, go on maternity leave, or get sick or even die suddenly. The potential for interruption to the business is massive, especially when we're talking about onboarding or travel approval. 

You market Flow towards end users but it creates a massive risk for interruption to the business. When you add in the fact that many departments run everything through their local power user, we've magnified that risk exponentially. Now it's not just one or two Flows that will go down, it's the entire department.

What are the plans/recommendations from Microsoft to address this risk? This is the one thing that is keeping us tied to SharePoint Designer workflows. They won't die if the user does.