We use the solution for integrating Microsoft Team and SharePoint. Also, we use it to manage document libraries and automation processes.
Process Automation Engineer at a tech services company with 11-50 employees
Easy to set up, but its AI features for data and process mining need improvement
Pros and Cons
- "It works best to build cloud flows."
- "It is challenging to scale the solution across multiple branches."
What is our primary use case?
What is most valuable?
The solution's most valuable feature is cloud flows.
What needs improvement?
They should improve the solution's features for data and process mining. It is easy to run small automated tasks but difficult to build large complex flows. Also, it is challenging to scale it horizontally across multiple branches.
For how long have I used the solution?
We have been using the solution for a year.
Buyer's Guide
Microsoft Power Automate
January 2026
Learn what your peers think about Microsoft Power Automate. Get advice and tips from experienced pros sharing their opinions. Updated: January 2026.
881,757 professionals have used our research since 2012.
What do I think about the stability of the solution?
I rate the solution's stability as a seven. Its error-handling feature needs improvement.
What do I think about the scalability of the solution?
We have three developers and ten end users of the solution. It is a scalable solution, and I rate its scalability as a six. But it could be better for large and complex cloud flows.
How are customer service and support?
We often take help from online forums to fix errors instead of the solution's support documents.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
We use our in-house software as well.
How was the initial setup?
The solution's initial setup process is straightforward and takes a day to complete. I rate the process as a nine.
Which other solutions did I evaluate?
We evaluated UiPath. It has better functionality and scalability. But, Power Automate is more accessible as our systems are integrated with Microsoft ecosystem.
What other advice do I have?
I advise others to take some YouTube courses on how to build solutions for desktop and cloud flows.
I rate Microsoft Power Automate seven out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Process Specialist - Operational Excellence at a government with 51-200 employees
User friendly, low coding functionality, and responsive support
Pros and Cons
- "The most valuable features of Microsoft Power Automate are user-friendliness and low coding functionality."
- "When you try to create a flow or work on the flow in Microsoft Power Automate you cannot undo changes. There are no options to edit or, undo an action. This feature would be useful. The editing option within the flow can be enhanced."
What is our primary use case?
We are using Microsoft Power Automate for automating approval.
What is most valuable?
The most valuable features of Microsoft Power Automate are user-friendliness and low coding functionality.
What needs improvement?
When you try to create a flow or work on the flow in Microsoft Power Automate you cannot undo changes. There are no options to edit or, undo an action. This feature would be useful. The editing option within the flow can be enhanced.
In a future release, they could extend the flow run limits. When the flow is running it will be terminated.
For how long have I used the solution?
I have been using Microsoft Power Automate for approximately three years.
What do I think about the stability of the solution?
Microsoft Power Automate is reliable.
I rate the stability of Microsoft Power Automate a nine out of ten.
What do I think about the scalability of the solution?
We have five developers and IT managers that are using the solution.
The solution is scalable.
I rate the scalability of Microsoft Power Automate a nine out of ten.
How are customer service and support?
We opened a few tickets with support from Microsoft Power Automate. The support is responsive.
Which solution did I use previously and why did I switch?
I have not used a solution similar to Microsoft Power Automate.
What about the implementation team?
We did the implementation of the solution in-house.
What other advice do I have?
The solution is managed by the global tenant. We have three people who manage it.
I would recommend this solution to others.
I rate Microsoft Power Automate a nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
Microsoft Power Automate
January 2026
Learn what your peers think about Microsoft Power Automate. Get advice and tips from experienced pros sharing their opinions. Updated: January 2026.
881,757 professionals have used our research since 2012.
RPA/IA Solution Architect at a tech services company with 1,001-5,000 employees
Fast and easy to use, but if it had queue support and it was capable of doing more complex automation, it would be a much better tool
Pros and Cons
- "It is quick, so I'm quite happy with it. It is also easy to use."
- "It lacks a lot of functionality that other tools have. There should be queue management, and there should also be the capability to deal with a little bit more complex automation. If it had queue support and if it was capable of doing more complex automation, it would be a much better tool."
What is our primary use case?
We use it for office automation.
What is most valuable?
It is quick, so I'm quite happy with it. It is also easy to use.
What needs improvement?
It lacks a lot of functionality that other tools have. There should be queue management, and there should also be the capability to deal with a little bit more complex automation. If it had queue support and if it was capable of doing more complex automation, it would be a much better tool.
In terms of performance, it is a little bit slower with calculations than a typical Excel Macro, for example.
For how long have I used the solution?
I have been using this solution for about six months.
What do I think about the stability of the solution?
It is a very stable product.
What do I think about the scalability of the solution?
It is already implemented company-wide, so we don't have to scale it too much. It already has lots of functionality built-in.
How are customer service and support?
I haven't used their support.
Which solution did I use previously and why did I switch?
I also work with UiPath, Blue Prism, and Automation Anywhere. Functionality-wise, Blue Prism and Power Automate are two completely different tools, but they share the common RPA target.
How was the initial setup?
It was easy. It was already in the company when I joined.
What's my experience with pricing, setup cost, and licensing?
We are using the free version of Power Automate.
What other advice do I have?
I would rate it a six out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Project Manager at a consultancy with 1-10 employees
Useful web scraping, beneficial no-code environment, and simple deployment
Pros and Cons
- "The most valuable feature of Microsoft Power Automate in the desktop version is web scraping because you can do a lot with it. I work in retail and you can study prices changes, which can give you a lot of information. The solution is no code which is a large advantage."
- "I think the language Microsoft Power Automate uses when you do expressions could be better. What they use is not a popular programming language. It would be better for Microsoft to find a more popular programming language, such as Python. It would take away the whole no-code aspect of the solution but you don't need to write that many lines of code to improve something in a process. Instead of no-code, they could be a low-code environment."
What is our primary use case?
I use both the on-premise version and web versions because they both have different tools. I use them both for different use cases and different scenarios.
I use Microsoft Power Automate to make reports and web scraping. I automate the reports with the desktop version because it works well. I use Microsoft Windows, to do some commands in the CMD, also known as the line assistant. When it comes to the web version, I mostly do reminders, scraping, extracting data from emails, and creating ticket systems. I take that data and put it in a list or create a table in Excel to extract information and automate that part.
How has it helped my organization?
Microsoft Power Automate has helped our organization by making processes faster. I do some consulting on the side about Microsoft Power Automate. We realize we don't need as many people to work on something because you can automate it or at least semi-automate the tasks.
What is most valuable?
The most valuable feature of Microsoft Power Automate in the desktop version is web scraping because you can do a lot with it. I work in retail and you can study prices changes, which can give you a lot of information. The solution is no code which is a large advantage.
In the web version, the most valuable features are creating tickets, taking email information, and creating a ticket with it, similar to an IT ticket.
Microsoft Power Automate is a tool that is easy to learn. There is some basic logic that you will have to understand but overall it is not complicated.
What needs improvement?
I think the language Microsoft Power Automate uses when you do expressions could be better. What they use is not a popular programming language. It would be better for Microsoft to find a more popular programming language, such as Python. It would take away the whole no-code aspect of the solution but you don't need to write that many lines of code to improve something in a process. Instead of no-code, they could be a low-code environment.
For how long have I used the solution?
I have been using Microsoft Power Automate for approximately seven months.
What do I think about the stability of the solution?
The stability of Microsoft Power Automate is good, I have not had a problem with the performance.
What do I think about the scalability of the solution?
Microsoft Power Automate is scalable.
We have approximately 10 people using this solution in my organization. The solution is moderately being used. The more you use it, the more ideas come to you of what you can automate or what can you create. In the future, it's going to be used more.
How are customer service and support?
I have not contacted the support from Microsoft.
How was the initial setup?
The implementation of Microsoft Power Automate was straightforward. It took only hours to do the full implementation.
What about the implementation team?
I did the implementation of Microsoft Power Automate in my company. Additionally, I do the maintenance and patching of the solution when needed.
What's my experience with pricing, setup cost, and licensing?
The cost to use Microsoft Power Automate is approximately $15 per user per month, for the basic plan. However, the solution comes free with the Microsoft 365 Suite.
You have to pay extra for the scheduling of the automation tasks.
Which other solutions did I evaluate?
Microsoft Power Automate is a newer solution to the market. UiPath is a lot more popular and has more features than Microsoft Power Automate. There's a lot of potential in that Microsoft Power Automate because it connects well with other Microsoft programs inside the Suite which makes it even more powerful. UiPath connects with other applications, but the fact that if you use Microsoft in your organization, it's more seamless. It works better.
What other advice do I have?
I learned Microsoft Power Automate faster because I know how to use Microsoft Excel, and that teaches you how to think more logically when it comes to computers. If you have an Excel or programming background, it's going to be easier because the logic creates the flows. If you won't want your learning curve to be that steep, I would recommend learning Microsoft Excel and then going Microsoft Power Automate. You will have more ideas of what you can do with the tool.
I rate Microsoft Power Automate a nine out of ten because you have to pay to receive the schedule functionality of the automation, which is important.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Software Assets Manager at a financial services firm with 5,001-10,000 employees
Its ease of use and integration with some of the existing products are valuable, but it needs more development to be an enterprise product
Pros and Cons
- "The ease of use and the integration with some of the existing products that we have would be its main takeouts."
- "From an improvement perspective, Microsoft just needs to make sure that they have a real enterprise RPA tool. PowerApps and Power Automate are still not at the level of UiPath and Automation Anywhere. It could be because Automation Anywhere and UiPath have been in the market for quite some time. It's just about Microsoft increasing their focus in terms of product reviews and development and making them competitive products that one can consider at an enterprise level. Right now, their use cases are limited as compared to what one would consider doing with UiPath and Automation Anywhere."
What is our primary use case?
It is currently being used by our customer service department. They're using it for tracking overtime, and they're also using it for reporting and automating their various service quality reports. So, automation of service quality reports and overtime management are basically two major use cases.
What is most valuable?
The ease of use and the integration with some of the existing products that we have would be its main takeouts.
What needs improvement?
From an improvement perspective, Microsoft just needs to make sure that they have a real enterprise RPA tool. PowerApps and Power Automate are still not at the level of UiPath and Automation Anywhere. It could be because Automation Anywhere and UiPath have been in the market for quite some time. It's just about Microsoft increasing their focus in terms of product reviews and development and making them competitive products that one can consider at an enterprise level. Right now, their use cases are limited as compared to what one would consider doing with UiPath and Automation Anywhere.
What do I think about the stability of the solution?
It is a stable solution.
What do I think about the scalability of the solution?
It is scalable, but it is limited in terms of the processes that you can automate. If you have complex processes that you want to automate, it doesn't have that capability yet. So, it is scalable but to a certain extent.
Our organization is working with it actively. Its number of users could be between 100 and 200.
How are customer service and support?
Technical support is given by Microsoft through the support model that they offer for customers. If you have an issue, you can log the issue in with Microsoft, and they would always attend to it. I would rate them a three out of five.
How was the initial setup?
It was straightforward. There was nothing complex.
You don't need much staff for deployment and maintenance of it. You need a very limited number of people.
What about the implementation team?
We used a partner.
What's my experience with pricing, setup cost, and licensing?
Its license is a part of our enterprise agreement. It is a three-year contract, but we pay yearly. So, it is a yearly license. There are no additional costs.
What other advice do I have?
I would rate it a six out of 10.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Co-Founder at a tech services company with 1-10 employees
Integrates well with Microsoft products, includes pre-build templates that are easy to use, and the support is good
Pros and Cons
- "The most valuable feature is that it easily integrates with other Microsoft products, so it has multiple connectors. You can create solutions that connect to Teams, Outlook, SharePoint, and OneDrive."
- "There are some bugs or intermittent behavior in the Excel activities that require using workarounds."
What is our primary use case?
I am a solution provider and I implement RPA products and automate processes for my clients.
With this product, you create your workflows on the cloud. We've used this product for integrating with Microsoft solutions. For example, one of them is a document approval solution, where documents are sent to SharePoint and then pushed to different users within Active Directory for approval. This is done according to rules set by the client.
There is also a COVID application that was built around Power Automate and the Power Platform, where users within the organization can raise a request for a test and this would be pushed to managers for approval.
We are also looking at financial processes around bank reconciliations and interbank transfers.
What is most valuable?
The most valuable feature is that it easily integrates with other Microsoft products, so it has multiple connectors. You can create solutions that connect to Teams, Outlook, SharePoint, and OneDrive.
There are templates available for you to create your own flow, and it is easy to start creating a flow and automating a solution.
What needs improvement?
There are some bugs or intermittent behavior in the Excel activities that require using workarounds. For example, there is an Excel activity called Collect that fails once in a while. When you want to choose or select a particular cell, once in a while, it fails to do so. It doesn't happen all of the time and I don't know if it's a bug, but it's something that they can look into.
For how long have I used the solution?
I have been working with Microsoft Power Automate for approximately one year.
What do I think about the stability of the solution?
This is a very stable product.
What do I think about the scalability of the solution?
The scalability is amazing. This is a cloud-based resource, and there is no limitation in terms of scale or size. You can easily increase the scope of processes being handled.
The COVID use case is available for all of the employees, which is approximately 2,500. The documentation approval use case is used by managers and people making requests, which is approximately 2,000 people. The use case involving financial reconciliation is only for a small team that consists of about five people.
How are customer service and support?
The technical support is good. They are available and you can just call them. We have Microsoft Office online support, as well. This means that you can call them, or instead go to the forum and search for activities and resources. They have a lot of resources available online.
There are good tooltips available within the product itself. You can look at something and the tooltip will explain how it works and what you should do.
Overall, the support resources are good and I would rate the technical support a nine out of ten.
Which solution did I use previously and why did I switch?
I also work with UiPath and WorkFusion.
How was the initial setup?
The initial setup is straightforward. Power Automate is a cloud-based tool, although I downloaded the Studio to my local machine.
The deployment takes one day. You just switch environments from UAT to production. You can easily export your solution and import it into the production environment.
What about the implementation team?
We were working with another company to implement the solution but we completed the implementation and deployment ourselves.
What's my experience with pricing, setup cost, and licensing?
The licensing model is flexible in that you can pay per automation or per user. My client receives a discount because of the large number of users and pays approximately $15 for each one.
There are no costs in addition to the standard licensing fees unless other resources are being used. For example, Office resources are available on Azure, but that is a different product. It is related to Azure, rather than Power Automate.
Which other solutions did I evaluate?
Our client chose this solution. They already had Microsoft enterprise licenses, and they felt it was better to use a Microsoft product for their automation solution.
What other advice do I have?
Overall, this is a good solution and I like it. It's very scalable and easy to do so. Also, there are many connectors and they are quite useful. This is a product that I recommend.
My advice for anybody who is implementing Power Automate is to be cautious about how they distribute their flows, just to manage the licensing cost. Because it is cloud-based, it is an easy-to-use tool for both small and enterprise-wide solutions. There are no complications when integrating with Active Directory or the cloud platform, and this is good, in particular, because everybody is moving to the cloud. This product makes it easy to integrate things that people are already working with, such as Teams and Outlook.
I would rate this solution a nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Senior Product Manager Data Science at a government with 1,001-5,000 employees
Comes with many capabilities and phenomenal support, and allows us to trigger a workflow at a certain time or when an event happens
Pros and Cons
- "Different trigger events were most valuable. You could schedule a process on a recurring basis, at a certain time of day or week, or when something happens, which is huge."
- "Their connector to Oracle or premium data sets that aren't Microsoft would often fail for me. The information given back about why it failed wasn't always robust to understand how to fix it and why it happened."
What is our primary use case?
We held a hiring event specifically for veterans. All the people who were registering were external to our organization, so we had them fill out a Microsoft form, which then triggered an email, took all their information, and stored it into a SharePoint list. This list fed a Power App, and we were able to:
- Check members in whenever they arrived.
- Capture extra details about them.
- Pass the information onto hiring managers whenever a hiring manager was interested in an individual applicant or somebody who showed up.
In another use case, we used it to track the vaccination status of all employees. There were about 90,000 employees. If they scheduled it, it would trigger reminders whenever an employee's vaccination was coming up.
How has it helped my organization?
We set up a process to monitor Twitter so that whenever specific hashtags that we cared about were used, the whole record of what was tweeted out was captured and stored into a SharePoint list because it was free and easy to analyze as well. That has helped. Event triggers, several different connections, and what you can do with the information once you have it have been very helpful.
We also used it as a one-time solution in a scenario where records were captured in a Power App, and oftentimes, those records, which were almost like medical records, would need to go to another team one at a time. We used Power Automate to capture all the information that was stored in Oracle. From the record, it would put the information into a Word document, convert the Word document to a PDF, and then email the PDF off to the team. All that was done behind the scenes with the user clicking one button. It was great.
What is most valuable?
Different trigger events were most valuable. You could schedule a process on a recurring basis, at a certain time of day or week, or when something happens, which is huge.
What needs improvement?
Their connector to Oracle or premium data sets that aren't Microsoft would often fail for me. The information given back about why it failed wasn't always robust to understand how to fix it and why it happened.
Sometimes, Power Automate's flow would turn off when it got fired incorrectly or misfired, but we didn't always get a notification of when it was turned off, and that was a problem.
For how long have I used the solution?
I have been working with this solution since October of 2019.
What do I think about the scalability of the solution?
It can scale. We used it to track vaccinations for 90,000 employees.
How are customer service and support?
I did deal with their tech support, and they were phenomenal. Their support person taught us the whole process of how to take a record, put it into a Word document template that you can customize, turn it into a PDF, and then send that email off. He was phenomenal.
How was the initial setup?
It was straightforward for the most part. Once you do it a couple of times, it becomes more intuitive. There are so many different YouTube videos or resources on Google to be able to figure out how to do something, what are you doing wrong, or how you can work around an issue.
In terms of maintenance, everything that I did was more of a one-off solution. It was me and one other person who would maintain an individual Power Automate statement.
What other advice do I have?
There are so many different capabilities with it. I would advise mapping out your capability, usage, or whatever it is that you want it to do. After that, start to create and go from there.
I would rate it an eight out of 10.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Senior Associate at a consultancy with 1,001-5,000 employees
Big range of connectors but the OCR capabilities not as evolved
Pros and Cons
- "Technical support is responsive."
- "Their OCR capabilities are not as evolved as the other tools."
What is our primary use case?
In our organization, the solution is popular where there is a need for attended automation or user. That "human in the loop," as we call it. There it is more popular than the other tools.
What is most valuable?
The most valuable feature we have found with the solution is the AI Builder. And they have a big range of connectors that we are finding useful.
What needs improvement?
One area of improvement needed for the solution is regarding the cloud source versus desktop flows. The desktop flows are not as absent, and there are other limits in features when it comes to comparison between the two solutions that Power Automate provides. So perhaps the desktop could also start including features like Connectors and Builder because these are the more frequently used. But both of the tools have their own utility.
It's evolving well. I have seen Power Automate eight months ago and have seen it now. So there is definitely a big step ahead. It's improved and it's rather helpful.
There is one feature I'd like to see added in the next release. Their OCR capabilities are not as evolved as the other tools. They do allow some AI Builder methods to achieve that. But in the desktop tool, the OCR functionality is not very useful. Everything has to be done on our text-based outcome. I'm sure they're already working on it.
For how long have I used the solution?
Power Automate is relatively new. I've been working with the solution for eight to nine months.
What do I think about the stability of the solution?
The solutions that we have built are going well. They are used, and we've not heard of any breakages there. I would say they are stable.
What do I think about the scalability of the solution?
The scalability of the solution is something we are still working on. Currently, we have a use case where we are trying to make it more scalable and there are means of doing it. Sharing up the flows and all of those things do add to the scalability. It's relatively new compared to UiPath, but I don't think they'll take very long to come up to speed.
How are customer service and support?
When it comes to technical support, I'd like to draw a comparison between UiPath that's more popularly used. UiPath has a very good forum and we get most answers on the forum itself. However, the technical support itself is not that strong.
Whereas in Power Automate, it is just the other way around. The forum is bad; we don't get anything there. But technical support, they're pretty responsive. And any queries you write to them, they usually do come back quite promptly. I'm happy with the technical support.
How was the initial setup?
The initial setup of the solution is pretty straightforward.
What other advice do I have?
Due to the pricing model, the solution is more convenient than any other tool. That is one plus that Power Automate has over the others.
It's very easy to use. Like we say, it's a "no-code solution." So even though all solutions do claim that, there is a little level of skill that is required when it comes to learning the other tools. But Power Automate is relatively the easiest to pick up.
UI Automation is something that they have made very easy, but editing both selectors is a challenge in Power Automate. There is not that much of a need to edit the selectors. But in case there is, then it is a challenge to edit them.
This solution is capable of doing pretty much everything that the other tools are capable of, and they have extremely competitive pricing. It is definitely an advantage. Their approval systems and interactions with the other tool. We have even tried some inter-vendor solutions, integrating UiPath along with Power Automate, for example. Those things work pretty well with Power Automate. It's convenient, not just for the end-user, for the business user, and it is also convenient for the developer. It's very simple and approachable to use as a solution.
I would rate the overall solution a seven out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
Download our free Microsoft Power Automate Report and get advice and tips from experienced pros
sharing their opinions.
Updated: January 2026
Product Categories
Robotic Process Automation (RPA) Process Mining Agentic Automation Business Orchestration and Automation TechnologiesPopular Comparisons
UiPath Platform
Automation Anywhere
Fortra's Automate
Blue Prism
ABBYY Vantage
Tungsten RPA
Pega Robotic Process Automation
WorkFusion
Tungsten TotalAgility
IBM Robotic Process Automation (RPA)
Nintex RPA
VisualCron
Buyer's Guide
Download our free Microsoft Power Automate Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- How do I choose between UiPath and Microsoft Power Automate?
- What are the main technical differences between Microsoft Power Automate and Blue Prism?
- RPA Governance and Business Continuity requirements for a large multi-national corporate financial services provider
- Which one to choose, Power Automate or UiPath, for unattended and attended bots implementation for a simple RPA use case?
- How is Automation Anywhere compared to Microsoft Power Automate?
- Should I choose Blue Prism or Microsoft Power Automate?
- Thoughts about Softomotive for RPA?
- How easy is it to migrate from RPA to MS Power Automate?
- When evaluating Robotic Process Automation, what aspect do you think is the most important to look for?
- RPA that Bots can run without centralized control?
















