Microsoft Power Automate Reviews

The use cases for the solution would be banking related, typically, and specifically surrounding BFS, Banking Financial Services.

The sequencer programming mode's ease of use is its most valuable aspect. The ease of calling out the functions in a sequence, basically from the functional side, is great.

The solution lacks certain items.

I'm not really qualified for judging the solution. A developer could give better pros and cons. 

We would not miss Microsoft Power Automation that much. As still has a long way to cover tasks when it comes to the ease of use like UiPath, which is pretty user-centric.

The solution needs to improve its integration with SAP and Oracle models.

The solution's automation is still evolving and still has a way to go.

The solution could benefit from mirroring Oracle's use of videos and community forums to help users get acquainted with the product. It could use better online training and/or documentation.

We've been using the solution (as Softomotive) for four years now. It's only recently become Microsoft Power Automate. Previously, Microsoft didn't have a similar solution.

The solution is pretty stable.

The solution is scalable, but there are issues. It's not perfect.

We have about 100 users on the solution currently.

We do plan to increase the usage of the product in the future. However, we do have our own internal tool we also plan on using more often.

I myself have not contacted technical support. It's the development team that does any outreach, so I cannot answer on their behalf.

The initial setup was not complex. It was pretty straightforward.

In terms of deployment, how long it takes varies. It depends upon the nature of the use case. Usually, it ranges between six weeks to 12 weeks. We used ten to 12 people for the deployment process.

We handled the implementation internally with our own team members. We didn't need the assistance of integrators, or consultants.

There are licensing costs, however, I do not know the exact pricing. It's not part of my scope of work.

We're simply customers. We don't have a business relationship with the solution.

We use the solution, however, not in its full capacity. It's just there as and when there is a need. The product earlier was in Softomotive. Microsoft just took over Softomotive, which has WinAutomation, so yes, technically, it is now Microsoft.

We're using an earlier version of the solution, not necessarily the latest.

I'd recommend the solution. We don't have very complex use cases to compare it to, however, for small to medium complexity projects, it would work well.

Overall, I'd rate the solution seven out of ten.

We use this product for automation.

Using WinAutomation helps us to reduce our resource costs.

The most valuable feature is that you can run multiple automations at the same time, in parallel.

It is possible to capture the video, which is better than saving only a snapshot or an error message.

It would be helpful to have features that are fine-tuned for Microsoft products because most of our clients are using products like SharePoint and OneDrive.

The OCR functionality needs to be improved. We are not getting the same accuracy as other tools when reading things like PDFs.

I have been working with WinAutomation for six months.

One of the biggest features is scalability, as we can run multiple activities in parallel.

We work with several RPA tools including UiPath, Blue Prism, Automation Anywhere, and we are also implementing Microsoft Power Automate.

UiPath has a very good OCR that can read PDF files well. It is more accurate than WinAutomation.

The initial setup is straightforward. It is easy to install, and it works in a plug-and-play fashion.

My advice for anybody who is considering WinAutomation is that it is a very good tool. They definitely need to use it. 

I would rate this solution an eight out of ten.

The most valuable feature is that it is integrated into the browser, which means that you don't need a development environment.

Power Automate is intuitive and easy to use.

There is a broad community so you can find a lot of information on the web about how it works. It is also well-documented.

The licensing model is difficult to understand and is something that should be improved.

When you are implementing a project, it's quite difficult to comment on what it is that you are doing. For a simple project it is fast, but to have a better overview then it gets complicated.

I would like to see more integration with other products.

We have been using Power Automate for about two years.

The stability is good.

Power Automate is a scalable solution. We have between five and ten developers who are using it.

The technical support from Microsoft is good.

We primarily use UiPath for our automation.

The initial setup is straightforward and it took us about two hours to deploy.

There are many different ways to license it.

This is a good product and one that I recommend. For anybody who is considering it, my advice is to do a proof of concept at each phase.

I would rate this solution a seven out of ten.

The primary use case of this solution is for IT service checks within our daily process automation. 

It monitors consoles and raises alerts when things need to be alerted. For example, when a business rule is broken then an alert is raised, or if we are looking at the backup management and server availability and there is a problem with the backup then we raise an alert.

The most valuable feature is the ability to integrate across multiple systems. For example between web portals, excel and email. 

The ability to write a process that covers all of those different areas of technology.

One of the challenges is dealing with OCR text recognition. They link out to Google, IBM, and Microsoft AI services for text recognition. This area needs to continue to improve because recognizing forms and what's on a form, and then when you try to translate that into information that you can use, is very difficult. I have not been able to make that work. I think that the technology is there, but it would require too much coding and it would be too much of an investment of time to make it work.

WinAutomation doesn't have the management abilities for remote management, but we are using Splashtop to access the device that is running the software.

In the next release, I would like to see form recognition added. AI form recognition for processing things like invoices and timesheets would be number one.

I have been working with WinAutomation for two months.

It's a stable solution.

We are not scaling it much beyond a single work station, but it does seem to be scalable.

We have two users in our company. There are plans to increase our usage.

I have only used technical support a few times but they have been good.

Previously, we were not working with other similar products.

The initial setup was straightforward and it only took a few minutes to deploy.

This solution is reasonably priced and offers a free trial period.

We looked at some other tools, but we chose WinAutomation because it was a low cost of entry and a free trial.

It takes slightly longer than you would expect to set something up that's resilient. Building resilience takes as long as building in the logic.

I would rate this solution an eight out of ten.

We use Power Automate to build applications for businesses uses such as workflow applications and process applications. We copy the data or get the data from other systems and use Power Automate to do some lightweight RPA tasks.

The Power platform has several features and Power Automate has two features. One is Flow and the other is UI Flow. Flow is used for workflow automation and UI Flow is the RPA solution.

We simplified the business processes and improved the efficiency of business user operations. As an example, we used to manually copy data between systems or to other files, and by using the RPA part of this solution, it now automatically copies and manipulates the systems and the files.

It provides business workflow features and application features, but the most valuable component is the RPA.

It is easy to set up and use.

For people who already use Office 365, Power Automate is very easy to integrate and use.

In the future, I would like to see more focus on AI and third-party integration.

Compared to other RPA solutions, there is a little bit of a feature gap.

I have been using Microsoft Power Automate for one year. The name changed a couple of months ago from Power Apps and Flow and we were using it for several months before the name change.

We have a direct connection to support.

I have worked with UiPath as an RPA solution, which has more features than Microsoft Power Automate. As an RPA solution, UiPath has been a market leader for several years.

It's a Microsoft Public Cloud solution and if you already have a subscription or have an account then it is very easy to use. You don't have to do any initial setup. If you don't have an account, it's still easy because you just have to purchase a subscription online.

We implemented Power Automate using our in-house team. We did not use the help of a vendor or an integrator.

Power Automate is a new solution from Microsoft. It provides business workflow features, application features, and RPA features. It's an all-in-one solution and if the customer already uses Microsoft Office 365 they can easily integrate it with Microsoft products.

If you want to integrate it with other platforms, such as virtual solutions it's also a good choice.

Overall, it is a good solution, but there is still a feature gap when compared to other RPA solutions.

I would rate this solution an eight out of ten.

Our primary use for this product is actually for a variety of reasons in conjunction with a few different products. We use it mostly for our accounting and invoicing purposes.  

From a development point of view, I found UiPath to be more valuable in flexibility. But Power Automate has been very easy to use in deploying most of our development, so because of that, it has become our preferred automation product.  

I think that the thing which needs the most improvement is really just their documentation. It should have better details of the processes. Right now it is on the lower end of the scale and does not have enough depth. So just adding more details and examples in the documentation would be helpful to users.  

It could really use some more capabilities with the OCR and UI functionality of the automation. Right now it is pretty good, but with that, it would be great and easier to use.  

I have been using this solution for probably about four months.  

 Power Automate is a stable product.  

I think Power Automate is a scalable solution and it works very well for my purposes.  

Our company is quite small at the moment. We have just over a hundred users. But that is constant use and it is changing daily. We have not done a lot of scaling but it seems like there are no problems so far as we grow slowly over time.  

Before really adopting Power Automate, I did have some experience with UiPath.  

The main difference between Microsoft Power Automate and UiPath is that I think UiPath just has a wider variety of opportunities for integration. By that I mean there are more products it can work well with. So even non-Microsoft-based products work well with it, like integration with Citrix platforms. This can function without a lot of extra work. I think that is really one of the main advantages.  

Power Automate is a much less expensive product than the competition and you can still accomplish a lot with it.  

I think the price points for Power Automate are very good in comparison to other products in the category.  

The advice that I would have for people considering the solution is that it is better for use with multiple, smaller projects and solutions. If that is what you want to accomplish then Microsoft Power Automate is a good target product.  

On a scale from one to ten where one is the worst and ten is the best, I would rate this solution overall as somewhere between a seven or an eight. Probably closer to a seven.  

Our primary use for this product is for the automation of manual tasks that may require some small integrations between systems. An example would be something like automatically sending an email from an action that is performed on our online system. Another might be writing data to our CRM database based on the input from an online form.  

The thing that this product has provided is a solution for quickly developing prototypes. We can create some new solutions really fast, test it to understand exactly which data is needed and then deploy the solution moving forward quickly through the process. That has been important for us. It is not necessarily that we all use Power Automate as a production-ready solution. It is more that we can use it to make prototypes that we can test with.  

I think the most valuable thing about this product for me is that it is really quick and easy to use. You do not need to have a lot of development skills to be able to create solutions. There is very little code involved, which is great, and it is very logical. It has also got great reporting. You can see the success and failure of each item that has been run through it. There are a lot of out-of-the-box connectors as well that make things easier.  

To improve the product, I think it would be great to see even more connectors available out-of-the-box and more maturity in that direction. I would also like to see some readiness for creating test and production environments so that you can differentiate which environment is you are working in.  

As far as additional features I am not sure what could really improve the product. It could maybe do with some more insights like triggered alerts.  

We have been using this product for about a year.  

So far we find that the stability of the product is really good. There is also good reporting if it is down for any reason. We have not really experienced stability problems or had any complaints about that.  

The scalability is really good. We have been able to use it for lots of different kinds of things. We do think that Power Automate is more for prototyping than for production-ready applications. You should probably upgrade to using Power Apps if you need something production-ready. You can build something quickly as a prototype in Power Automate and then upgrade to Power App to create a more refined application. Using those together means that what you develop is more production-ready. But in general, I think it is really scalable. There are lots of different use cases and lots of different solutions you can build and make available.  

There are not a lot of people currently using the product in the company — maybe like 10 or 12. We really want more and more people to use it, but it is not our job to roll it out to everybody. We just found it and thought it was interesting. We share it with people when they want to know how to try and automate something. But it is not something we had planned to really roll out company-wide as a solution initially.  

We will eventually roll it out to more people as we grow with it and discover more uses.  

We did not really use a different solution before Microsoft Power Automate. We were using Flow originally, which is what the same product was called before it became Power Automate. The name change was just within the last two months.  

The initial setup is really straightforward. It is immediately available out-of-the-box when you have Microsoft Cloud. You just click on the button and it is there ready to use.  

Our deployment took maybe a week or so. Most of that was just to play around and get familiar with it and become ready to start doing actual projects. Because you are building your own little mini-applications inside of it and the framework is available already, it is just a matter of learning how to work with the tool. You need to learn how to use it to build what you want to build.  

There were only two people involved in the deployment process. It did not require a lot of effort. It was just a couple of minutes to be ready to start using it and a week to get to the point where we could be productive.  

The framework for the product is maintained by Microsoft. Any applications that we build inside of it is all we need to maintain ourselves. So we do not have to maintain the framework at all.  

Power Automate is really cost-effective. You pay for use and if you want a premium connector then you just pay for a premium connector. But a lot of things are available for free. If you want to use an adapter that is not available for free, then you have to pay the provider for it. I do not know how much that costs.  

My advice to people who are considering implementing Microsoft Power Automate is that I think it is a really great tool that allows you to get started quickly on prototyping and integrating solutions that will simplify some redundant tasks. The best idea would be to just get started with it and experience what it can do.  

The biggest lesson we have learned from using Microsoft Power Automate is that there is just so much that is possible to automate. Thinking about the potential scope of what the tool can do, we now look at a problem and think that maybe we can use Power Automate to resolve the issue.  

On a scale from one to ten where one is the worst and ten is the best, I would rate Microsoft Power Automate as a nine-out-of-ten at this point. To become a ten they would just need some more maturity with the test and production environments and making things more production-ready. Also, some additional guided help would valuable for new users to orient them and get started building their own applications. But other than that, it is perfect.  

We are implementation service providers and this is one of the products that we provide to our clients.

There are several use cases for this solution including automating tender processes, compliance-related processes, and in finance, we have automated some invoicing processes.

The most valuable feature is the ease of automation.

The development time for ProcessRobot is very good compared to other solutions.

There are some limitations when it comes to automation with Excel.

Better support is needed for building custom components on top of ProcessRobot.

We have been working with ProcessRobot for about one year.

The stability is okay. We haven't had any major issues, although there have been some hiccups here and there.

The scalability is good.

We have clients of all sizes, although ProcessRobot is best suited for small and medium-sized business, and not for enterprise-level customers.

Technical support for ProcessRobot is good.

We are working with UiPath and Blue Prism as well. We began with ProcessRobot at the end of last year, but the other two solutions we started with about two years back.

Generally, the development time is less when compared to UiPath and Blue Prism, although Excel automation is better in those solutions.

We have also worked with Automation Anywhere.

ProcessRobot does not support custom components, which is really bad because all of the other solutions do.

The initial setup is easy.

My advice is that this solution is good for small and medium-sized businesses that want to automate processes that do not require much coding. If there is a requirement for building custom components or custom modules then I do not recommend this solution. For an enterprise-level client, this capability needs to be there.

I would rate this solution a seven out of ten.