I really like Microsoft Power Automate because it makes automating repetitive tasks simple and efficient. Its ease of use is great for beginners, and the templates make implementation quick. I use it frequently since it saves a lot of time, and it integrates seamlessly with Microsoft 365 apps and many third-party services. It’s also feature-rich, offering everything from simple workflows to advanced AI-powered automations. The customer support, through documentation and community forums, is helpful when I need guidance. Review collected by and hosted on G2.com.

On the downside, Power Automate can get complicated when building advanced flows, and troubleshooting errors can be frustrating since messages aren’t always clear. Some of the most useful features are only available in paid plans, which can limit what you can do on the free version. Multi-app integrations can be tricky to debug, and flows sometimes fail if there’s an internet disruption. Overall, while it’s powerful, there’s a noticeable learning curve and occasional limitations that can slow things down. Review collected by and hosted on G2.com.

I love using Microsoft Power Automate because it significantly enhances productivity and efficiency by automating complex tasks in a seamless way. The ability to create flows with a simple, no-code user interface is particularly beneficial, allowing for easy construction of automation processes without requiring technical expertise. I appreciate the vast variety of triggers and actions available, which cater to diverse automation needs and simplify multi-stage business processes. The new interface is fantastic for handling errors and exceptions easily, and it efficiently maintains parallel actions within a single trigger. The initial setup of Microsoft Power Automate was extremely easy, making the transition into using the tool smooth and stress-free. Review collected by and hosted on G2.com.

I find the formula language in Microsoft Power Automate quite complex, particularly when dealing with advanced expressions. It doesn't exactly follow the syntax of familiar languages like Python, Excel, DAX, or JavaScript, which adds a learning curve. Additionally, if a trigger fails, alerts are not immediately sent, which hampers timely resolution of issues. Furthermore, the Copilot integration could be improved for better functionality and user experience. Review collected by and hosted on G2.com.

I really like how it connects perfectly with Outlook and Excel. It saves me a lot of time because I can automate simple tasks, like saving email attachments to my OneDrive, without writing any code. Also, the best part is the ready-to-use templates. You don't need to be a programmer to start. You just pick a template, connect your accounts, and it works immediately. Review collected by and hosted on G2.com.

Sometimes the error messages are very hard to understand. When a flow fails, it is difficult to find exactly what went wrong if you are not an expert so i need to search expert solutions in Google. Moreover, i don't like the fact that numerous features require Premium subscription. Review collected by and hosted on G2.com.

I find Microsoft Power Automate very useful for automating tasks, helping me with data analysis projects, and connecting files seamlessly. It's very easy to use, with a straightforward interface that doesn't require coding skills to set up triggers or perform automations. I think the best thing about it is how it simplifies automation, allowing my colleagues with little to no coding knowledge to set it up easily. The initial setup is particularly easy, especially when specifying the apps you're using, which is great because it makes it accessible to everyone on my team. Review collected by and hosted on G2.com.

The last time, one of the issues I had was emails. Trying to incorporate it with my Power BI to work on a specific column and help triggers emails to that column. I actually had issues there because I have to start a course on that so I could do it. So I think it should be more pretty straightforward. Review collected by and hosted on G2.com.

I like Microsoft Power Automate because it's easy to automate tasks and has a wide range of apps for integration, especially with Microsoft tools. It offers many ready-made templates, making it possible to build workflows without much coding. The simple interface and low-code approach make it easy to create and modify workflows, even without deep technical knowledge. The wide app integration lets different tools work together smoothly. The initial setup was also very easy, with clear instructions that didn't take much time to follow. Review collected by and hosted on G2.com.

Some workflows can be hard to debug when something fails. Complex automation takes time to understand, and error messages are not always very clear. Clearer and more detailed execution logs would help, showing exactly where a flow fails to make troubleshooting easier. A better testing mode and suggestions to fix common errors would also improve handling complex automations. Review collected by and hosted on G2.com.

What I like most about Microsoft Power Automate is how effectively it simplifies automation across different applications without requiring deep programming knowledge. It provides a wide range of built-in connectors, so it’s easy to integrate services like Outlook, SharePoint, and Teams, as well as many third-party tools. Another major strength is the visual workflow builder, which allows users to design, monitor, and manage automated processes through a clear, well-structured interface. I also appreciate the ability to set up automated approval workflows and notifications, since this helps teams streamline routine processes and keep work moving without unnecessary delays. Overall, it cuts down on manual effort, boosts productivity, and helps ensure repetitive tasks are handled consistently and efficiently. Review collected by and hosted on G2.com.

One drawback of Microsoft Power Automate is that, as automation expands across multiple services and conditions, some workflows can become difficult to manage. For new users, it can take time to understand how triggers, actions, and connectors fit together, especially when you need to troubleshoot errors in more advanced flows. Another limitation is that certain premium connectors and advanced features require additional licensing, which can raise costs for organizations that depend heavily on automation. There may also be occasional delays in flow execution, depending on the trigger type or the specific service integration. Overall, the platform is powerful and flexible, but maintaining and optimizing larger workflows often requires careful planning and a bit of experience. Review collected by and hosted on G2.com.

I like Microsoft Power Automate because it offers reliable automation, which helps me eliminate a lot of repetitive manual work and saves time. The available templates are really useful, allowing me to get started quickly without having to build everything from scratch. The integration with other tools is great, and I find it very easy to use. The drag and drop feature, along with the clear step-by-step structure, makes creating automation simple and efficient. I also find the initial setup to be very easy, which keeps the process smooth. Review collected by and hosted on G2.com.

Debugging errors can be difficult at times and complex flows become harder to manage and also performance varies at time. Review collected by and hosted on G2.com.

I appreciate how Power Automate enables the automation of repetitive tasks without requiring any coding skills. The interface is very intuitive, and the extensive library of pre-built connectors makes it easy to integrate with M365 as well as various external services. This tool has helped our team cut down on manual work, standardize approval processes, and streamline workflows across different departments. Review collected by and hosted on G2.com.

As flows increase in complexity, especially when several people are working together on the same automation, they can become challenging to maintain. Debugging these flows often takes considerable time, since error messages are sometimes unclear and the logs may lack the detail needed to quickly pinpoint the underlying problem. Additionally, some connectors come with usage restrictions or can be unreliable at times, which may disrupt workflows if they are not closely monitored. Review collected by and hosted on G2.com.

This aid does not allow me, as an execution handler working with various channels, to be bombarded with manual entry of data. It is always working in the background; no leads are lost in favor of another task, which gives it some degree of operational consistency that is impossible to mimic by human effort. Typically, templates are junk, but in this case, they are encompassing a large percentage of typical marketing applications off the shelf. Social platform and email connection plug-ins are plug-and-play and that is why I was able to establish automation without the IT department assisting me. Review collected by and hosted on G2.com.

Connections to third-party social tools often die (after a few weeks), and thus manual authentication is required. Although this is not a dealbreaker, it is annoying to receive flow failed emails because of the lapse of time between tokens. Review collected by and hosted on G2.com.

Connectors for almost everything. HTTP, Azure, GitHub, Dataverse, Excel, Teams, ServiceNow, you name it. I can stitch infra checks, data setup, and notifications without reinventing wheels.

Fast incident workflows. A failed CI run posts to Teams -> one click opens a Power Automate “triage” flow that grabs logs, tags the right owners, and files a ticket with repro steps. It’s oddly satisfying.

Run history that’s actually useful. Each step’s inputs/outputs are viewable, so I can spot a bad payload or header mismatch in seconds instead of spelunking through app logs.

Human-in-the-loop made simple. Approvals and adaptive cards let QA/Product sign off on risky test data changes straight from Teams, no separate tooling.

Desktop flows for legacy UIs. When a vendor system has zero APIs, the desktop recorder (attended or unattended) gets us “good enough” RPA to unblock end-to-end tests. Review collected by and hosted on G2.com.

Complex logic gets messy. Big branching flows turn into spaghetti; the expression editor is powerful but unforgiving. Source control is awkward. Exporting/importing Solutions works, but it’s not as natural as a Git PR for reviewing logic changes. Fragile desktop automations. Minor UI tweaks can break selectors, so RPA steps demand babysitting. Review collected by and hosted on G2.com.