Microsoft has recently announced changes to its cloud workflow service, Flow, to enable teams to contribute and manage flows centrally. This new sharing capability is also available to SaaS and custom API Connectors. In addition to these collaboration features, Microsoft has also announced support for…
Microsoft has recently announced changes to its citizen workflow service, Flow, to enable teams to contribute and manage flows centrally. This new sharing capability, called Team flows, is currently in public preview and extends to sharing SaaS and custom API connections. In addition to these collaboration features, Microsoft has announced Flow support for Gmail and LUIS , a Microsoft Cognitive Service.
For some enterprises, there has been requests to provide greater control over who can create flows and what API connections can be used within a flow. For example, some organizations may not want end-users writing workflows that create data in certain applications. Having more granular security capabilities has been one of the top asks on Microsoft’s ideas forum. John Luangco, a technology blogger, feels this sort of control in the enterprise is needed as:
Employees leave organizations and the flow should be able to continue to work even after the original author of the flow has left the organization.
