Microsoft Power Automate Reviews

We use the solution to automate internal processes like leave applications.

The solution is relatively easy to use and cost-effective. It is also easy to learn and understand. It is part of Microsoft 365, so it's free. Additionally, it is easy to integrate Microsoft Teams with the solution.

The UI of the solution is not so good. Power BI's reporting functionality should be improved. 

The next release should include more functionalities and better reporting.

I have been using the solution for three years.

I rate the stability an eight or nine out of ten.

I rate the scalability a seven or eight out of ten. Around 50 people in the organization use the solution, including five to seven administrators, 30 to 40 engineers, and nine to ten sales and marketing staff.

Previously we used Google Suite in collaboration with many other solutions. We needed it for process automation and for creating electronic signatures. It required us to subscribe to multiple solutions. However, we wanted only one or two platforms. So, we switched to Microsoft.

The solution is not so difficult to deploy. The deployment takes up to two hours. I could deploy the solution myself. One engineer is enough for the maintenance of the solution.

The solution is free with Microsoft 365.

I would recommend Microsoft Power Automate to those who use Microsoft 365. We search the instruction manual, FAQs, and other online documents when we face issues with the solution. Overall, I rate the product a nine out of ten.

Microsoft Power Automate is used to automate tasks and schedule workflows.

Microsoft Power Automate has helped us automate tasks that have reduced human error and increased efficiency.

Microsoft Power Automate offers over 200 connectors that enhance the user experience.

Microsoft Power Automate is limited if we want to create a complex flow because we have to split the log into two flows.

The licensing cost is high and has room for improvement.

In a future release of Microsoft Power Automate, I would like to request the addition of a synchronous action, which would allow us to choose whether we want the solution to immediately synchronize any changes we make, for example, in an Excel document through SharePoint.

I have been using Microsoft Power Automate for five years.

I give the stability of Microsoft Power Automate an eight out of ten.

I give the scalability of Microsoft Power Automate an eight out of ten.

The technical support was able to resolve my issue but their response was delayed.

Neutral

I previously used UiPath before switching to Microsoft Power Automate.

The initial setup is straightforward and I give it a nine out of ten. We are working on a solution where each environment can have multiple solutions. Within each solution, we are creating a batch that includes Microsoft Power Automate, which can be easily deployed to higher environments. This allows for automated quality control of the pipeline, but data flow can also be manually imported and exported if necessary. There are several deployment possibilities, including importing it via pipeline or solution. One person is enough for the deployment.

The implementation was completed in-house.

The licensing cost is expensive. I give the cost a three out of ten.

I give Microsoft Power Automate an eight out of ten.

We have six developers that use the solution in our organization.

I recommend Microsoft Power Automate as an excellent automation tool. Our organization has successfully utilized this solution in various applications for automation, and it has proven to be highly effective.

Our use case is for presenting price regeneration. I'm the technical lead for robotics and we are customers of Microsoft. 

As a part of the Microsoft suite, this is a convenient product for us because it integrates well with other Microsoft products. We've also found third-party integrations with third-party applications is quite easy.

I think the speed of the application could be improved. If you're looking at Power BI dashboards, for example, the back-end processing is fine, but when you look at it from a UI point of view, which is what the client sees, the speed of execution could be improved. 

We've been using this product for five years. 

We haven't had any issues with stability. 

The scalability is good, we have around 25 users. 

Microsoft provides very prompt support. 

The initial setup is relatively straightforward and takes a couple of weeks. There's not much maintenance involved because it's part of a larger solution. 

We have seen ROI on investment although it's difficult to quantify. 

The product is fairly priced; the cost is part of the enterprise solution. 

I recommend doing a POC to ensure the product is fit for purpose. 

I rate this solution nine out of 10. 

We use Power Automate for applicant tracking. We automated around 80 percent of the process. 

Power Automate's out-of-the-box integration is nice. 

Microsoft could offer more AI education and training.

I have used Power Automate for a few years.

I rate Power Automate seven out of 10 for stability. 

I rate Power Automate seven out of 10 for scalability.

I rate Power Automate eight out of 10 for ease of setup. We did it in-house.

I rate Microsoft Power Automate four out of 10 for affordability. It's a little more expensive than average.

I rate Microsoft Power Automate six out of 10 overall. It has a lot of integration capabilities out of the box, but it isn't always accurate. 

I've primarily used some automations, however, it was just for practice. I automated a few activities here and there. I have not used it extensively. For example, I can use it to read some emails or share files, or pull information from Sharepoint, et cetera. It can help me create new records for auditing purposes. It can pull data to show we are in compliance. 

The most valuable features include its ease of use for automation creation. It's very easy to use. We can go online and watch videos and figure out how to use it. 

It can help us improve many processes and workflows. It helps with efficiencies. 

The functionalities are very similar to other types of languages. It's not hard to learn, which means we'll be able to make more workflows in the future. 

It is stable.

It can scale well.

The solution comes bundled with Microsoft 365. 

I haven't come across any downsides to the solution.

We'd like to see even more free courses to help people learn to automate smarter. 

For countries in our region, it's not very well known. Microsoft has to do a better job of advertising it and how it can help businesses so that it becomes more well-known and widely used. 

So far, the solution has been stable. The workflows have been good. There are no bugs or glitches. 

The scalability has been fine so far. I haven't come across anything that would make me think it wouldn't be. 

We plan to use it more to make more workflows in the future. 

I've never used technical support in the past. 

In our company, we have people looking for new opportunities and tools to help the sales force in automation matters. 

The pricing is not clear to me. I don't deal with that. We have Office 365 and the solution is included in that bundle. 

It's a good product. If a company needs to automate something, it's a very useful tool.

I'd rate the solution eight out of ten.

We could use it more. It's still new to me. 

We've primarily used it to update some legacy systems for our client, as well as government compliance systems and web-based reporting systems that don't have APIs.

With the desktop version, we can automate many things. The ability to do a lot of things is one of the most valuable features.  

For our clients with web-based reporting systems that don't have APIs. There was no other way to get the data into the systems than to manually enter it. We were able to automate that process entirely. We now collect information on a front-end power app, store it in a cloud database, and then push it into these external systems. 

The fact that we can do that for them is probably the most powerful piece for the people. 

We have removed an entire repetitive business process that didn't add any real value to the business but was required for compliance reasons.

There is a lot that could be done to improve the product. With debugging, sometimes things don't work because of timing, and just learning how to do that.

We were able to use a lot of JavaScript in that product using the desktop version, which was a huge help in terms of speed. 

The debugging tools require improvement as well as the monitoring which goes along with it. 

When things don't work as they should, it's usually because you're dealing with third-party websites. The importance of timing cannot be overstated. These are the areas that need to be improved.

One of the issues was that there wasn't a lot of documentation when we first started because Microsoft had purchased the product and began integrating it.

We started when Microsoft's product still used Selenium, and then they bought this product and switched over to it, which is a much better product. However, it is a third-party product. It has not yet been fully integrated.

We are using the most up-to-date version of Microsoft Power Automate.

We use Microsoft Power Automate both on the cloud and the desktop. We have done a lot more with the desktop than with the cloud.

Stability, it's fairly stable. They released a large number of fixes.

Scalability is the biggest challenge from my perspective because it is literally designed as a single-user product, at least the RPA piece of it is.

When you are trying to do what we are doing and running flows on behalf of people, trying to make it enterprise-ready and hardened is probably the most difficult challenge right now. 

Instead of running it on the client's desktop, we are running it on virtual gateway machines on their behalf, and they have support for that. We're doing it now for some other clients, and so far, we have done some pure RPA power automation.

Getting it enterprise-ready, and running it in the background on behalf of the users is probably the most difficult challenge.

I haven't used technical support at all.  have used mostly the web or we have figured it out ourselves.

I don't have a direct support contract with Microsoft. I've been doing the majority of this.

It's been a couple of years or so since it was set up, but I would say that it was pretty straightforward. It didn't take much to get it set up and running.

We believe it is a solid product that will continue to improve, and it is well integrated. It is integrated with the cloud, the database data verse, and power apps, with which we have a lot of experience and really like using power apps for doing things quickly. 

It's the first RBA product that I've really used. I've looked at it for a long time. We have done a lot of RPA work over the years, probably for the last six or seven years, just doing pure JavaScript, literally just writing JavaScript to automate these types of things. From our perspective, this is a huge step forward because we took a lot of pretty complex JavaScript code and logic and were able to put it in a format that we believe may make the code more maintainable and not just sort of stuck in the heads of one or two programmers.

We have completed a few projects, and just finished another one in which we were able to fill out 10,000 forms for a client who needed to do it as quickly as possible when a system went down. We reduced a process that would have taken weeks to four hours. We believe that the product has a lot of merits when used in the right places,  and I suppose we are still figuring out when it's the right tool.

I haven't used the UI path or some of the "higher-end" components. I believe one of the advantages of this device is its low cost. It's now built into Windows 11, it's a part of it.

When they say low code, no code, I would say the downside is that, while this is partially true, you still need to think like a programmer when trying to debug it or set up an enterprise-wide system.

I think it's functional, but I think it's got a way to go and it's hard for me to wait because I really haven't used those other products, We've been doing it mostly by hand for quite some time. I would rate Microsoft Power Automate a seven out of ten.

It's an RPA (Robotic Process Automation), so it's a robot and we use it to automate a lot of financial reports.

This solution improved the reporting in our organization. The financial department was doing a lot of copy-pasting from different sources to create financial reports. Through ProcessRobot, we were able to automate all those copy-pasting and produce all those financial reports overnight. Our financial department was able to free up a lot of their time. They no longer need to invest their time in the work, particularly in creating the report. They can focus their time on analyzing the data more, rather than exerting more time in report creation.

This solution is easy to use. It was one of the easiest to use, plus the price-quality was the reason why we selected this. Its features for its price were the best fit for our company.

As for what could be improved in this solution: I tried to do some automation on Microsoft Dynamics AX and it was not successful. The integration with Dynamics AX was not really a success, but for the rest, I don't have problems with.

Some automation features on some programs did not work smoothly, so that's a negative feature. That might be solved now with the newer version because Microsoft took over Softomotive. I hope they have improved that feature and that it now works better with their own software.

I'm not really missing features I'd like to see on the next release because we only use it for a really small target area. We just use it for reporting. It's not like we're using it extensively on test automation and other similar processes, but I know we can do a lot more with this solution.

We've been using this solution for three years now.

This solution is really stable.

About the scalability of this solution, we're using the desktop version now, and I know that there's some other version. We can scale it up to use more robots, but we don't have a requirement for it currently.

The technical support for this solution was really okay. Information on the website was documented well e.g. there were nice manuals. I didn't use their technical support, but the website where I could find all the technical documentation was really good. Because it was well-documented, it was self-explanatory and I could start from there.

We used two different solutions, but we switched because they were too expensive for the purpose we wanted to use those solutions for.

Setting up this solution was really straightforward. It just needed a little bit of clicking. It only took a few minutes to install as it's a really simple program. It's not complicated.

Implementing this solution was self-explanatory. I did the implementation myself.

We saw a significant return on investment because we were able to save a lot of time from our financial and human resources staff, so this saves a lot of money and the return on investment on that 1,000 euros is quickly felt.

We paid for one license for this solution. It was a lifetime license for this version (version 8), and we paid around 1,000 euros. At the moment, as long as we use this version, there is no additional cost, but when we upgrade to the new version, it will be a monthly subscription.

We bought the license from Softomotive, so we had one license and that license was restricted to version eight. When we upgrade to the newest version, we would need to buy that upgrade, because Microsoft has taken over Softomotive and they no longer sell licenses. They only sell monthly subscriptions.

We have to transfer our license to a Microsoft subscription, and though they will give a redemption, the cost will change, so this is also one of the reasons why we didn't change to the new version yet.

We evaluated other solutions: UiPath and Kofax.

You're using an older version. Now, Microsoft has taken over this version and they're calling it Power Automate desktop. I think a lot of improvements have already been done to the newest version, so what I'm going to tell you about the old version will no longer be relevant. We need to upgrade to the new version then check if the problems we were having have been fixed in the new version. Overall, we are satisfied with what we use it for because I think it's quite okay for our use case.

The name ProcessRobot doesn't exist anymore. Softomotive has been taken over by Microsoft so this solution has been rebranded by Microsoft to Power Automate desktop.

It's a robot, so it's operating on a server on its own. There's no real user, but it's trying to replace users. There's only one developer who is creating the tasks on that system. We also don't require anyone for its maintenance.

At the moment, we're using this solution to create a report of 50, so we have 50 data scripts running each night. We're planning to extend its use with a couple of reports, but for now, there's no need to further use it for other tasks.

My advice to others looking into implementing ProcessRobot is to try it first because it's free now, so you can test it. You can test it for free on the Windows 11 version. It's delivered by Microsoft for free. Go ahead and test it. The solution is nice and fast.

I would give this solution a rating of eight or nine. Let's say nine out of ten. I couldn't find any pictures for my use case. I think this was the best choice we could make, and ten is too perfect for rating a solution.

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.

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.

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.

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.

I have been working with this solution since October of 2019.

It can scale. We used it to track vaccinations for 90,000 employees.

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.

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.

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.