Microsoft Power Automate Reviews

We are a solution provider and this is one of the tools that we implement for our clients.

We have been automating several tasks using this product. They include things like comparing Excel worksheets with the contents of databases, automation in database security, and we have internal logs that can be used to help developers pinpoint errors.

This is a cost-effective RPA solution.

WinAutomation is missing a lot of options that are available in UiPath. One limitation is that for logs, the only option is a CSV file. There is no option, for example, to work with an Excel file.

There is a limitation in setting up loops, where it does not support multiple conditions.

We would like to be able to write code, the way you can inside of UiPath.

We have been using WinAutomation for the past two months.

This solution is stable.

This is a scalable product, although it is best for mid-sized industries.

The technical support is good. We had an issue and they were able to resolve it.

The installation and initial configuration were straightforward, taking not more than 10 minutes.

I deployed the product myself.

WinAutomation is cheaper than competing tools.

Our choice for using WinAutomation depends largely on the client. We will continue to use it, although if our client does not agree then we would have to use another tool.

This is definitely a product that I can recommend. The price is cheaper than other tools and it has a lot of features.

I would rate this solution a six out of ten.

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.

Our primary use case is the automation of tasks.

The most valuable feature is the ability and ease of linking multiple connectors within the same flow. For example, you can have the same flow connections with Outlook, SharePoint, and DLLs.

It is a low-code environment, which means that it is more agile in terms of automation. You are able to start with one automation and then easily modify it for other uses.

The interface is user-friendly. It took me perhaps a month or two to understand what the dynamic is and how it works, and then how it can be linked to the sprint. I would say that it takes two or three weeks to learn the basics, but then it becomes easy to work with. The more you learn, the more you can evolve the flow, and you can implement additional scenarios.

I would like to have chatbot assistance available, where you can open it and receive help on the spot. For example, if you are struggling in the middle of implementing a flow, you can easily communicate with the chatbot, perhaps providing the error message, and it will search for a resolution. In my case, I posted my error message on Google and saw that other people had similar problems. I was able to check the community platforms and I found the solution in one of the posts.

The documentation can be improved because although they do have a manual of about 500 pages, it does not cover all of the possible scenarios. It would be good to have one that covers different scenarios or different commands, provides basic knowledge about the commands, and even basics about JSON. Also, the user manual and learning guides that they have can be made more user-friendly.

I have been using Microsoft Power Automate for about six months.

I have had some issues with stability where I received a surprising error message and still don't know why it happened. While it has been primarily stable, so far, we are not yet in production so I am not fully certain how it will perform. If the performance is good and there are no glitches or automation errors, then I will feel confident in the stability.

My impressions at this point, from what I have experienced, is that the stability is high.

With respect to scalability, because we haven't implemented the solution yet, I am not sure if it will scale or not. My feeling is that it will scale because it already has multiple connectors for what most organizations frequently use.

It is fully designed but until it is implemented and I see the results, I will not feel comfortable commenting on whether it will scale well. My feeling at this point is that it is of medium scalability.

At this point, as the solution architect, I am the only one who is using it. In the future, we will have other people in my team using it.

I have not posted to the community, so I don't know how reactive they are. From what I have seen, as I searched the forums, it seems that people are responsive. My feeling is that community support should not be an issue.

At the same time, I still think that they should have more friendly documentation and chatbot assistance.

I would rate the support a three out of five.

I would say that the initial setup is easy and user-friendly, but you should still have basic knowledge in advance to do it properly.

Power Automate is included with Office 365.

In terms of resources and in terms of cost, this solution is efficient.

I see Power Automate as a quick-win solution for many enhancements that can be used in any organization. Rather than a task that involves heavy coding on a third-party application, such as a CRM or with Salesforce, Power Automate can be leveraged for good results.  Overall, I would say that my experience using this product has been good.

My advice for anybody who is considering this product is to create a prototype or a proof of concept, first. At the end of the day, management needs to buy into the solution. They should see, however, that it brings value to the business. It is a product that I recommend, although they do need to fix the small glitches that I experienced in the flow.

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.