Microsoft Power Automate Reviews

I have been using Microsoft Power Automate for about three years now, and it allows us to automate various processes. Our main use case is to automate repetitive business processes and integrate it with different systems, especially when we want to replace manual email and Excel-based workflows.

For example, we use Microsoft Power Automate to handle workflows when a user submits a request, and it automatically triggers approvals and sends notifications via Microsoft Teams or Outlook. I keep both options enabled so that the end customer or the approver has flexibility, and once the approval is done, we update the data in SharePoint or a database. We track the status in real time, and if approved, the approval is stored in real time.

Microsoft Power Automate works tightly with applications like Microsoft Power Apps. We also integrate it with Power Apps to trigger backend workflows, making it part of a complete end-to-end solution.

Microsoft Power Automate has many features, but what I feel is best is its huge connector ecosystem. It connects with Microsoft tools, databases, some APIs, and third-party applications, supporting hundreds of services. Another best feature is that Microsoft Power Automate is a low-code workflow automation platform because we have the option to drag and drop to build a flow, making it easy to create notifications, approvals, and data workflows.

The combined impact of using Microsoft Power Automate has helped me and my team with integration and efficiency. For instance, we connected tools like Microsoft Outlook, Microsoft SharePoint, and Microsoft Teams very seamlessly. We eliminated the need for custom integration code because it is directly connected, reducing dependency on other API development or databases. This had a great impact on faster implementation of workflows, and we now rely less on developers. Previously disconnected systems are now working smoothly. For example, an email automatically saves attachments, updates in SharePoint, and notifies us in Teams, all without coding but simply through drag and drop on Microsoft Power Automate.

For improvement, I think there should be version control like Git. While Microsoft Power Automate can improve in debugging and error visibility, it is quite good given the amount of its use and the complexity of the tasks we want it to handle. We utilize Microsoft Power Automate for small tasks, and it is ideal for handling collaborative efforts or tasks connected to Microsoft 365 products.

I chose that rating because it cannot handle a lot of complex tasks, which makes it difficult to manage larger tasks. It excels in small tasks, and I think Microsoft can develop this better. While it is already good for small tasks, there could be something offered like Microsoft Power Automate Plus.

I am a senior at Alstom and I have been working in development for five years now.

Microsoft Power Automate is quite stable in my experience.

I think Microsoft Power Automate fares really well in scalability. We can increase app functionality and design multiple workflows effectively.

Microsoft provides very good customer support and is always ready to assist whenever we reach out.

We did not use any other solution before Microsoft Power Automate. Although we had demos or free trials for UIPath, I found UIPath a little more complex, so we switched to Microsoft Power Automate.

Microsoft Power Automate is not very expensive and comes with many bundles. It is essentially plug and play, so setup is not an issue, although we may need to invest a little more for all features. However, licensing is managed when we consider the costing to buy.

In terms of ROI with Microsoft Power Automate, everyone has saved time, leading to a good return on investment regarding time saved.

Microsoft Power Automate is not very expensive and comes with many bundles. It is essentially plug and play, so setup is not an issue, although we may need to invest a little more for all features. However, licensing is managed when we consider the costing to buy.

We did not use any other solution before Microsoft Power Automate. Although we had demos or free trials for UIPath, I found UIPath a little more complex, so we switched to Microsoft Power Automate.

I advise others looking into using Microsoft Power Automate to use it for the best use case, explore all aspects, try all the integrations, and make use of Outlook and Teams capabilities, as it will be really helpful and convenient. My overall rating for this solution is 8 out of 10.

My main use case for Microsoft Power Automate is to automate equality assurance processes where my agents receive emails automatically after I complete assessments.

This automation has made the process a bit smoother for my agents rather than communicating their scores manually. Microsoft Power Automate has helped to disseminate their scores to them seamlessly.

It's also made work easier for my quality assurance team whereby they communicate feedback to the agents easily when needed.

The best features Microsoft Power Automate offers include the aspect of providing responses instantly to the agents. It's a great one for me, and I think that stands out.

Instant responses have helped in that the agents are able to get assessment in real-time, and we also developed a feedback mechanism whereby the agents can submit feedbacks if they want to query a particular result. We are able to automate all of these processes using Microsoft Power Automate, and it's a win-win case for the analysts as well as the agents.

Microsoft Power Automate has positively impacted my organization as it has saved a lot of time and effort. Before now, what we did was to collate the response results of the agents after assessments and had to provide it to the agents manually. But with Microsoft Power Automate, the agents get their scores in real-time and it saves time, effort, and a lot of stress for our team. It's a very good one for me.

Something frustrates me concerning Microsoft Power Automate, and that is about the integration with Microsoft Forms and Excel. The issue now is that I don't get my responses synchronized automatically, and that frustrates me a lot. If the team could take this as feedback, the synchronization of the feedback responses from the forms and the Excel sheets should be seamless.

This synchronization issue happens frequently, and it causes a lot of delays in the sense that the mails that ought to go out to the agents fail at some point. I have to reload these responses so that the agents can get their responses as when submitted. What I notice is that the responses don't go out without proper synchronization, so I reload the field responses, and this works afterwards.

I would say probably a seamless walkthrough process for new users would be beneficial. For those using it for the first time, a seamless walkthrough process would be fine.

I have been using Microsoft Power Automate for about a year now.

My experience with the configuration process has a bit of a challenge at some point. Moving from on-prem to cloud definitely could be a bit challenging, especially for my team transitioning from what we've been using before now to a new system.

I relied on customer support and online research, which were of great assistance to help overcome those challenges during the configuration.

So far, Microsoft Power Automate is stable, and I have not experienced any downtime or reliability issues.

I think that the scalability of Microsoft Power Automate might be a challenge regarding increased workloads.

Recently, the customer support for Microsoft Power Automate has not been quite responsive. I complained about the failed responses and real-time synchronization, but I haven't gotten responses since then.

The customer support of Microsoft Power Automate rates as four on a scale of one to ten.

Neutral

I haven't used a different solution since joining the organization; we just worked manually.

The initial setup with Microsoft Power Automate was really quite easy.

Deploying Microsoft Power Automate in my environment is quite easy. It is smooth.

Since using Microsoft Power Automate, I have seen a return on investment primarily in time saved for me. Time is very valuable to me, and it saves time a lot.

On a daily basis, it saves about two to three hours. Then cumulatively, from a weekly perspective, we've saved up to 10 to 12 hours.

My organization did evaluate other options before choosing Microsoft Power Automate.

When responses are submitted via the form and come through the Excel workbook, the mails fail at instances, and the agents don't receive these mails, which can be very frustrating.

I wasn't too much into the pricing for Microsoft Power Automate as my financial team handled that.

Power Automate is doing great. Keep it up and keep doing good.

I rate Microsoft Power Automate eight out of ten.

Microsoft Power Automate is used to integrate with other Microsoft products, though not to a great extent. UiPath was started first as an RPA tool, and one of its advantages is that it is not application-dependent, so it understands the screen to connect to any application. When we started going with Microsoft, we also began using Microsoft Power Automate, and many times, even the users can do it; a simple type of automation can be handled by the user also. This is a combination of Microsoft Power Automate as well as UiPath.

Microsoft Power Automate's no-code workflows help my team in daily operations to a great extent. Automating a particular activity may not be so useful, but when you connect the whole workflow, then it starts helping a lot. We have not started as of now, but we are planning to use Microsoft Copilot Studio also for developing AI agents so that everything starts falling into Microsoft, where we can use a combination of Microsoft Power Automate, AI agents, and other Microsoft platforms to make a seamless workflow that is fully automated to a great extent, not fully, but at least to a great extent automated.

Microsoft Power Automate's no-code workflows help my team in daily operations to a great extent. Automating a particular activity may not be so useful, but when you connect the whole workflow, then it starts helping a lot.

I cannot say much about the best features in Microsoft Power Automate because I have not used it personally, but first of all, it is very easy, it is a low-code platform, and Microsoft has a lot of integration with Microsoft technologies, making it very easy to connect with MS Teams and different Microsoft products, including MS Azure. From that point of view, it provides a lot of connectivity options. From a cost point of view, Mendix is much more costly compared to Microsoft Power Platform, allowing us to develop applications very quickly.

For future updates in Microsoft Power Automate, I think there are many features already provided that we are unable to use fully; we are just the users. One thing I might suggest is to look at connecting more diverse connectors, so users do not require much time to connect to different applications. It is very easy to connect MS Teams or SharePoint or even Azure cloud services, and I have not tried connecting with different applications or how it will work with legacy applications, but the more we try, the better it would be.

I work with Microsoft Power Automate and Power Platform for development, including Power Apps, for roughly about two years, mainly, but not for full automation because we also use UiPath as an RPA for automation. This is a combination of UiPath as well as Microsoft Power Automate.

I do not have much experience with Microsoft support, but while using the Microsoft platform for development, sometimes we look for specific functionalities available according to the documentation. However, when our team finds that it does not work, we try to find out who can support us. When we create a support ticket on the Microsoft platform, it takes a good amount of time in certain cases, especially when we get stuck, and at that time, Microsoft's response can be much slower.

I would rate the support from Microsoft around eight; I really appreciate it from that perspective, so I would not say it is a ten, but I think we can definitely go up to nine.

Positive

AI-driven automation helps with business processes mostly, as I think, by allowing us to create AI agents very quickly when we talk about large language models, and nowadays there are many platforms that allow you to do orchestration. We can do many things quickly, such as connecting different applications and performing web searches. There are tools available now, and the protocols are also there, which standardize the process when we discuss A2A protocol or MCP protocol, helping standardize things, which is beneficial to that extent. The only concern I have is that people still feel concerned about security, but if that is taken care of, it does not require many highly technical developers to create agents.

From my perspective regarding Microsoft Power Automate, there are no areas needing improvement or any downsides; this is based on a user perspective. For AI systems, there has to be a top-down approach; it is not just technical elements that can fit in. When we talk about responsible AI or ethical AI, security is also an area of concern. It requires a strategy, but focusing on AI agents, it is very easy and does not demand many complex programming skills to create the agents.

It may be difficult for me to specify how many external data sources we connect with Microsoft Power Automate because our data center is hosted in Germany and the whole architecture is not well-known to me. However, people are not using it for end-to-end automation as of now, but it can connect to different applications. Mostly, they are using it to connect to Microsoft Outlook mailing system or SharePoint or Share Drives or making some connection to send data from one platform to another for later use in Power Apps. I provided an overall rating of eight for this solution.

Microsoft Power Automate is primarily used for triggering emails based on activity in SharePoint lists or SharePoint objects, wherein a flow is created that will trigger something into action.

One scenario I recently worked on involved a list containing all employee birth date details. For every person whose birthday is today, an email is sent from the organization wishing them a happy birthday, with the employee, their colleagues, and their manager included in the CC line.

Microsoft Power Automate has multiple use cases such as approval workflows with business logic, where managers, senior managers, and other stakeholders are involved in monitoring and approving tasks. We also pull data from multiple sources such as Excel, SQL, and APIs for reporting purposes.

The best feature of Microsoft Power Automate is its extensive library of connectors, allowing integrations with Microsoft 365, SAP, Salesforce, SQL, ServiceNow, REST APIs, SharePoint, and Teams, along with being a low-code platform for creating workflows with minimal coding and supporting robotic process automation.

The most seamless connectors I rely on in Microsoft Power Automate are Outlook, SharePoint, and Teams, as they allow me to filter and automate actions such as saving email attachments to SharePoint or sending notifications in Teams easily.

Microsoft Power Automate has positively impacted our organization with significant time savings, achieving a 60 to 80% reduction in manual effort for tasks such as downloading attachments and sending emails, thereby saving hours of repetitive work per week per team. We saved two hours daily per team.

For improvement in Microsoft Power Automate, better debugging for errors is needed, as it is difficult to trace the root of issues. Handling complex logic could be cleaner with version control for better collaboration, and decision-making regarding premium connector pricing could be simplified.

AI features in Microsoft Power Automate could be made more developer-friendly, as they sometimes remain basic or generic and do not always provide helpful suggestions for complex enterprise use cases.

I have been working with this solution for more than five years.

Microsoft Power Automate is stable but can become very laggy at times.

Microsoft Power Automate is quite scalable.

Customer support for Microsoft Power Automate is pretty good.

Previously, we used only Excel to manually manage tasks, but now we utilize Microsoft Power Automate for better efficiency.

Before using Microsoft Power Automate, others should take a trial to understand their requirements and use cases, as trying the free trial can help them assess its suitability for their needs.

We have seen a return on investment with time saved, as previously we missed notifications and were late on scheduled flows, but now we receive reminders and notifications promptly.

My experience with pricing, setup costs, and licensing for Microsoft Power Automate indicates that the premium plan costs $20 per user per month while the enterprise pricing is $12 per user per month. There is a free developer plan for building and testing, though it has limited app capabilities.

Microsoft Power Automate runs on Azure, and its hosting and execution are dependent on that cloud infrastructure. I would rate Microsoft Power Automate an 8 out of 10. It scores an 8 out of 10 due to debugging not being very developer-friendly, performance issues, and throttling limits, making it an excellent automation tool but not a full development-grade platform.

My usual use cases for Microsoft Power Automate are for productivity and enhancement, so I create workflows to produce a particular output and reduce manual, mundane tasks by streamlining them into a process. I integrate Microsoft Power Automate into applications like Excel to perform a particular action, and it also integrates with Teams to follow up on different business units and their various use cases. I work on different business use cases, but mostly I focus on streamlining processes using Microsoft Power Automate.

The RPA feature in Microsoft Power Automate has significantly impacted my digital transformation efforts because it has improved my understanding and knowledge. It has made my processes better by reducing ad hoc coding. What I build now is easier to maintain and scale for more efficiency.

I usually do not connect with external data sources outside of Microsoft sources that we have, so it is limited to our own environment and the tools that we have, such as Excel and everything Microsoft. My team does not go outside of Microsoft to connect to any databases.

The features of Microsoft Power Automate that I have found the most valuable include the ability to get notifications for things I set up using Teams, which is a quick win for me. I can create calendar invites from emails to notifications in Teams and then back to my calendar and also the calendars of people I want to have as recipients for a particular process; this is one of my most used features.

The RPA feature in Microsoft Power Automate has significantly impacted my digital transformation efforts because it has improved my understanding and knowledge. It has made my processes better by reducing ad hoc coding. What I build now is easier to maintain and scale for more efficiency.

I would like to see the continuous improvement of Copilot because when I have really complex flows, Copilot just tells me it is not sure. I think it is still a limitation and a work in progress, so that is what we need to work on. Every other thing seems good; when you have an error, you know where to see the error, and you know how to decode it.

I have been working with Microsoft Power Automate for six months.

In the past six months, I would say Microsoft Power Automate has been very stable.

Having stability is absolutely important for me because I have a lot of workflows that need to be very stable, and I rely on that dependency. I would say that is a 10 out of 10 need.

I think Microsoft Power Automate is scalable; I have not come across any limitations for the number of things I do, from that angle, I would say it is.

I do not often communicate with the technical support of Microsoft Power Automate; I am quite reliant on the community. Most of my questions always go there, so I have not had to communicate with tech support.

Besides the community, I also use official documentation provided by Microsoft.

Before Microsoft Power Automate, I did not use a different solution for the same use cases.

Before choosing Microsoft Power Automate, I evaluated Excel and Microsoft Outlook itself, as there are functionalities in those that have been enhanced by Microsoft Power Automate. I rely on Microsoft Power Automate for functions that Microsoft Outlook cannot do.

Organization-wide, I am in the Microsoft Power Automate community at my work and see a lot of improvements people discuss about their teams and what they have used Microsoft Power Automate to accomplish. I would say it is a good reach and a high percentage for the team and different businesses to improve their processes.

I would say the quality of the documentation is good. I am sure there are ways it can be better, but for now, I think we have enough information; it can depend on the reader to take their time to search for what they need.

I have rated this review 7 out of 10.

The engineers on-site can generate an automated report that takes approximately 10 minutes, while before it took them two days. This is the type of solution we are implementing with Microsoft Power Automate and Power Apps.

This case was for an industrial company, and we use Microsoft Power Apps for this industrial sector, specifically for medium companies.

For example, when he had to use Java or other programming languages, he spent considerable time. With Microsoft Power Automate, he can complete complex development in 60 hours, so he can improve significantly because it's a really easy tool.

We connect with several external data sources using Microsoft Power Automate, and it has benefited our operations.

AI agents could be included in the next releases. Additionally, chatbots would be a great addition.

Positive

We have been using Microsoft Power Automate at Planview. Earlier, we would mostly have the Waterfall type of project approaches rather than Agile because of the nature of the projects. We were trying to adapt to Agile methods, which is where we were looking at both AgilePlace and ProjectPlace.

We are using it as a backend for some tools. The decision making focuses on formatting, and we have to filter out based on dates or based on the area where it stands in the process flow.

It has been good overall as we didn't have the process in place before. With these features in place, it has definitely improved the overall turnaround time by approximately 20% to 30% at least.

I have to explore more, but it is good. I need to review other options before I can have a fair idea as I have not fully gone into depth exploring it.

We haven't gone into depth to explore the integration with AI, so I am not really sure. Going into the future, I believe it would be important.

We have been using Microsoft Power Automate for less than a year.

We don't directly need to contact Microsoft most of the time because the IT department takes care of it.

Positive

We are currently using some in-built tools. We are not using any third-party tools for project management, mostly in-built in-house tools, involving Excel and Power BI.

There has been around 20% to 30% productivity improvement, which will definitely save money and costs, but we have not actually calculated anything on the cost saving. There is definite improvement in productivity.

If someone could elaborate on which features they are interested in, that would be helpful. I am not using it currently, though I used it in my previous experience.

I would rate Microsoft Power Automate a seven out of ten.

I think my current use cases with Microsoft Power Automate involve using the basic suite such as Word, Excel, PowerPoint, databases, and Outlook on a daily basis, and some things such as SharePoint, Teams, all the share stuff, and communications. I have worked with Microsoft Power Automate and the new features such as Viva, Insights, not much.

We use Microsoft Power Automate in several streams with Power Apps, where we have developed a custom-made quotation tool. It has an interface with some inputs from the sales users, and then we upload an Excel file with some other details and lines, and we connect all that with Power BI also, within the suite, to output quotations for our customers.

Our company has integrated AI-driven automation in Microsoft Power Automate. Our company has recently developed three AI agents: one for human resources to ask for leave time and vacations, called Sophia; another integrates with Copilot to help us address some issues for books related to our company culture, including Stephen Covey's Seven Habits of Highly Effective People; and there's also an agent for support cases that I haven't used yet, but we've done that with Copilot integrations and Teams integrations, allowing me to chat with it in Teams.

We just connect with one external data source using Microsoft Power Automate, which is our CRM; there's an API that we use to connect with the external CRM, Odoo.

The best features of Microsoft Power Automate are its ability to switch from one app to another without user interaction, so you can automate a task, take data from one source, process it, and then output it in another format or have it as an input for another app, and also to transform data and have that done with minimal human interaction.

Regarding integrations, we have integrated within the Microsoft suite for our workflows; I don't recall having to integrate from another source, as all the integrations we have done are within Microsoft products.

The Microsoft products integrations help our workflows because it's very easy; all products and APIs are in the same interface, and all the fields you need are easy to find and call, making it a seamless app for the end user.

At this point, I don't have any features for improvement in Microsoft Power Automate. I haven't used it with AI language models, and I think it may be restricted to work very friendly with Copilot, which could lead to further developments with other AI models or tools, thus suggesting some work is pending to do.

I have been using Microsoft 365 business since it was launched, and I have been using Microsoft since '95.

I don't remember having complex tasks for the initial setup of Microsoft Power Automate. It was very easy for us, especially since we're in the technology field, and it wasn't so complicated.

I rate their customer service or support for Microsoft Power Automate as great, but I haven't used it yet. I don't remember having a support case open, so we've relied on online documentation and videos, but I don't recall needing to address a support case or service.

Positive

I don't remember having complex tasks for the initial setup of Microsoft Power Automate. It was very easy for us, especially since we're in the technology field, and it wasn't so complicated.

Microsoft Power Automate is included in the licenses we bought initially, but I don't recall having to purchase anything else. Perhaps we had the correct tier or licensing from the beginning, as I don't remember paying anything excessively or overpriced.

I think Microsoft Power Automate is great; I haven't used any other tools, and it has been the one we have used since the beginning. I would rate it a nine out of ten.

We started with the E3 model alias called Enterprise, but it's not the last or top licensing product we have; it's one step before.

Our primary use case for Power Automate is mainly extracting data from regulators' and government websites. We have executed numerous projects, with a major one being the data extraction from these websites.

One of the most valuable features of Power Automate is its ability to extract text from a website. The capability to navigate different pages using click buttons is also crucial. 

We have saved thousands of hours by automating tasks that would have been labor-intensive and error-prone if done manually. This automation has significantly reduced human errors, allowing us to avoid such issues more effectively.

Power Automate could be improved by adding an internal fuzzy lookup or fuzzy match feature. This addition would enhance the tool's utility.

I have been working with Power Automate for the last three and a half years.

I usually reach out to the Microsoft Power Automate community for support. Sometimes it has worked, but other times it hasn't, as Power Automate is a relatively new tool. 

There needs to be more support documentation and videos that could be more helpful. However, having experience with coding is essential to fully utilize Power Automate.

Negative

We started off with UiPath, but Power Automate's desktop version is easier to use and more user-friendly. Additionally, since Power Automate is part of the Microsoft ecosystem, it integrates well with the other Microsoft tools we use.

Power Automate is cost-effective. It has helped us save time, and we've saved thousands of hours through automation.

I used UiPath previously.

The community around Power Automate is quite helpful, however, there's a need for more comprehensive support documentation and videos. However, in the end, having coding experience is crucial. 

I would rate Power Automate as six out of ten.

Positive