Overall Satisfaction with Microsoft Power Automate (formerly Microsoft Flow)
We use Microsoft Flow to automate internal processes such as material purchase approval flow, document file upload, customer data collection, technical teams communication when new documents are published in the file repository, and recently the integration between our chatbot to support technical and commercial teams, implementing in the bot the sending of emails with attachments and password validation by 2FA. All these automation have been integrated with Office365 products: SharePoint, Microsoft Forms, Outlook 365, Office 365 Users, and Microsoft Teams. Activity flows utilize various integration components such as HTTP webhook, Egnyte, Office 365 user, and groups search. As a result, we reduced the time spent on internal processes, with email exchanges and billing between teams, improved the dissemination of important documents, and expanded the resources and services available to our internal users.
- Easy to configure and implement the flows.
- Large catalog of addons and integration components.
- Ease of working collaboratively.
- Allows creation of custom flow components.
- Easy to share and distribute the flows.
- Documentation about some components, functions, and usage syntax needs to be improved.
- A tool for creating custom connectors.
- Native integration with office365 services.
- Active Directory-integrated security and permissioning.
- Automation of communication tasks, treatment and dissemination of information.
- Real-time alerts when new documentation material becomes available.
- Tracking and visibility of steps in a purchasing process.
- Insufficient documentation for lay users or beginners regarding formulas and connector configuration.
- Has an engaged community with multiple forums covering all aspects and features of Flow.
The tools competing with Microsoft flow have interesting features, but they fail when you need to use resources located internally in the company, such as databases and network file repositories, in your flow, in addition, the security, permissions, and authentication part is not integrated to the Active Directory used for user authentication on the network, it is even possible to implement this authentication integration, but this requires a level of access to the server environment and network services that ordinary users will not have. If you only want to use cloud services in your flow, some free tools can be useful, including the free license of the Microsoft flow itself.
Do you think Microsoft Power Automate delivers good value for the price?
Are you happy with Microsoft Power Automate's feature set?
Did Microsoft Power Automate live up to sales and marketing promises?
Did implementation of Microsoft Power Automate go as expected?
I wasn't involved with the implementation phase
Would you buy Microsoft Power Automate again?
For those who use Microsoft and Office 365 products, it is a great orchestrator and Automator of routines, running autonomously to integrate SaaS products, databases, and collaborative tools such as Teams and Sharepoint. Depending on the need, a Premium subscription is necessary, as it enables a series of native or third-party connectors and integration services. Integrations with third-party systems and services require you to have a subscription or license to these services. Microsoft Flow will be much better used in situations involving several teams, or manual processes with many steps, standalone use can automate many routines that should be done using a workstation, even if server components, such as Sharepoint, are required. Possible to create a flow integrating the components of these two environments. However, the workstation flow editor is not for beginners, it is a more complex tool that requires prior knowledge of the functioning of corporate systems and infrastructure and programming logic.