Microsoft Power Automate Reviews

The best feature is that it doesn't require any other connectivity. As a standalone solution, it works well.

It should work better for Angular websites, as it has a lot of problems. It is not able to read the data from them as expected. In general, it should work better with modern websites.

Scalability needs to be improved so that it can support multiple bots.

There used to be a Process Watch feature, but it is now gone and should be put back.

I have been using WinAutomation by Softomotive for six months.

This is a stable product.

This is not a scalable product. The option is not there for adding multiple bots is not there. Because of this, we are moving to Power Automate. It is not advisable to have one bot that handles 10 missions.

The initial setup is easy.

We are transiting to Microsoft Power Automate because of the scalability.

If WinAutomation had Process Watch capabilities then it would be better than Power Automate, but without it, this solution has become very weak.

Due to the issues with scalability, I do not recommend this product.

I would rate this solution a seven out of ten.

The solution is easy to understand and to develop connectors. You can always extend your own connectors. The ability to go outside and develop your own APIs is a real benefit. Microsoft is heavily investing and developing new features. It is well integrated into the CRM, SharePoint, and other Microsoft platforms.

I had some experience in the past with the solution having some difficulties with large loads, it is already better but it could still be improved.

Another area that needs to be improved is when calculating the quotes of your API calls and flow steps, they are currently not available on the dashboards where you can follow. The API limits will be enforced at some point, at this point you should buy all the add-ons to extend them. This was promised by the end of last year, but it is still not added. Every community is waiting for when this is going to be inforced. It is important because it will contextually be a big step to understand the economics behind your flows and steps, etc., and how to do it more efficiently to save your API calls and steps. The question is, what is the real end cost of how much add-ons you will need to purchase.

In an upcoming release, it would be nice to see bigger integration of cloud and desktop flows.

I have been using the solution for approximately two years.

I have been dealing with Microsoft support for like 10 years or more now. Their support is similar to Office. It is Microsoft of course, I had experience with the premier support. The first level support agents will try and help but sometimes on the first levels, the knowledge shift is a bit lacking. You will sometime have to strain yourself explaining what you exactly want and then you will need to be transferred over to the higher level product team. When it comes to Power Automate, they have a dedicated team, which more or less understands the product.

When making good architectural decisions it is best to understand what kind of scenarios you are solving, especially when it comes to the loads. Try to calculate what is the overall load that will be used, and all flows per day, per minutes, per hour, etc. It is important to do some testing.

Keep in mind the enforcement of API quotas, etc. It is important to start thinking about this and start calculating your flows, to get to the real cost for usage, excluding the initial license. It is critical to know how fast you consume your assigned API calls and when you have to buy extra. This is all in a way stored in the licensing documents, but it is not physically enforced, this is something to keep in mind.

I fully recommend this solution.

I rate Microsoft Power Automate an eight out of ten.

We used it internally to automate certain workflows for our daily business and validate our commercial proposal. We used its latest version.

Its complete integration with Microsoft tools and the inclusion of the CRM are the most valuable features.

It is embedded directly in the Office package, so clients have direct access to it. It has a lot more functionality than other standalone solutions, such as UiPath or Blue Prism.

It is mostly integrated with the Microsoft environment. Unlike UiPath, we cannot really use external tools with Microsoft Power Automate. There should be a possibility to integrate it with external tools or systems.

I had some experience with it two or three years ago, and I used it again about two months ago.

It is absolutely stable.

We have not scaled it.

It is straightforward. The deployment duration depends on the complexity. For our use case, it took a couple of weeks.

It is free for us. It is embedded directly in the Office package.

Our clients prefer using UiPath because it is easier to use and has more functionalities than some of the other solutions. It is also more economical. In the Tunisian and West African markets, UiPath is used more popular, and the customers prefer a solution that is implemented in their market.

At the moment, Microsoft Power Automate is suitable for automating a few processes on each desktop. It is a small solution, but Microsoft has a clear roadmap for this solution, and it would be an interesting one in a few months or years.

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

We primarily use the solution for automation purposes. It can offer an alternative desktop option, and therefore it can automate a lot of stuff. It's part of the application. It also can connect us to a number of data sources and that helps us a lot. However, it's difficult to get into specifics due to client privacy.

It's a very stable product. We find it to be quite reliable.

The solution is very easy to use. There's a bit of familiarity with the product due to the interface they have. We use other Microsoft Office products, for example, and it has a similar look and feel that's recognizable if you are familiar with the Microsoft Suite. 

The look and feel and user interface make training new users a fairly easy process.

The solution offers a variety of very good features.

There is an exhaustive amount of templates that users have access to.

You do need to either get a bit of IT support or do a bit of coding in order to implement the solution successfully.

Something lacking is Microsoft Office plugin, however, it's my understanding that their Office plugin is out now or coming soon. We're just trying to understand the use case. 

If they can make it integrated into Microsoft's Office Suite, that would be great. It would be better than lining it up with the Office plugin application. I'm sure it exists in some form, however, maybe not for the mainstream things.

The solution is still maturing very quickly and it's going to take no time for this to be Enterprise RPA.

I've used the solution for the last year and a half or so. 

The solution is stable. There aren't really any bugs or glitches. It doesn't crash or freeze. It's good.

The solution is very scalable. As a cloud product, it makes it very easy for users to expand if they need to. When a company needs to scale, they can do so, no problem.

We do plan to continue to use this solution, and we'll continue to use other Microsoft solutions as well.

We end up using a lot of community resources. Microsoft has a huge community, and it's really helpful in terms of finding answers and asking questions.

I've used the previous generation of this technology, such as Logic Apps and other products of that nature.

We didn't use any other products really. We had some in-house and also some VBA Macros, PowerShell scripts and others which we had created. However, this was the first proper solution we've invested in.

The initial setup is pretty straight forward. It's not overly complex. You do need a bit of IT support, however, you could put it in and save it and other people can use it and probably tweak it quite easily.

While there is a bit of coding needed, once you have everything set up, there are lots of templates that make the implementation of different processes very easy.

The deployment is quick. There's just a bit of needed configuration with the cloud. We didn't activate all of the features; we only activated what was required. I can't recall the exact amount of time it took to do this.

It is fast to implement, does not depend on the changes to existing systems to implement. It save hours that a team spend on performing the process manually. Mostly importantly it is easy to training business users since users are very much familiar microsoft and windows interface (UI).

The licensing set up depends on your organization. If it's an enterprise, it's based on their user department and how do you want the solution to be distributed.

Many companies already have Microsoft Office licenses, for example, and this is part of that. 

It's not too expensive as a license. At least, that's my understanding. 

In comparison, an RPA tool with Outreach costs $5,000. You can use it, however, it's expensive.

I'm using the latest version of the solution.

We are a consulting organization, and we do help clients.

We've helped large organizations. We don't have just one use case for this product. We have many.

You can't build an application with this solution. This is more for automating within a department or in an area, for example, a finance area, where they have all sources lined up and it takes almost three or four days for an accountant to go through the data to create templates and updating templates, etc. Those kinds of things. This solution makes the processes happen faster.

I'd recommend the solution to other organizations.

I would rate the product at an eight out of ten. There's a bit more maturity that needs to happen, however, all of the elements are there to make for a great product.

Currently, we are in an active search with a provider for on-premise, and therefore we use it to automate our process of moving our permits to electric housing and preparations.

We use the solution for building processors and it's really easy to use for this task. It gives you another way to move the path. 

With Microsoft, there are a lot of great process management tools. 

The initial setup isn't too difficult.

The availability could be a bit better.

Technical support needs to be able to respond quickly to queries. Right now, they are much too slow.

I'd like it if it were possible to have the solution as an on-premises installation, however, that is not possible. It only is available on the cloud.

I've been working with the solution for the last six or seven months. It's been less than a year at this point. We haven't used it for very long yet.

Power Automate, compared to Softomotive's product, offers the most in terms of versatility. Stability is not an issue. It has been very good for this product. We did not have that kind of problem with our customers or any installation. We don't seem to have to deal with bugs or glitches. It doesn't crash or freeze. We're happy with it.

At the moment, we have 80 professional developers on our team that work with the product. On top of that, we have various companies that use it. We have 50 or so different customers using the cloud.

We use the product regularly. We're on it on a daily basis.

Scalability is very, very easy to accomplish. If a company needs to expand the solution, it can do so easily.

The solution's technical support isn't that great. They could be better. They're slow to respond when there are issues. They really need to be faster in this regard.

We also work with Softomotive WinAutomation as well as ProcessRobot. Using more than one solution allows us to cross-manage better.

The initial implementation wasn't too hard, or, at least, that was my understanding. I didn't directly participate. However, I did not notice the team dealing with any complexity. It's pretty straightforward. Any organization shouldn't have too many problems setting it up.

The maintenance of the license is largely handled by Microsoft. We handle everything else.

We handled the implementation in house. We did not need outside help and we did not hire an integrator or consultant or any person of that nature. We handle the implementation for the customers if we need to.

The licensing itself isn't that great. That said, the solution is very cheap. It's on the lower end in terms of price, if you look at the entire market. It's rather affordable.

We're Microsoft partners.

We're using the latest version of the solution right now.

I would definitely recommend the product to other organizations. Overall, we've been pretty happy with it, even though we haven't used it for too long.

In general, I would rate the solution at an eight out of ten.

We carried out a successful POC on Power Automate Desktop. It was right after they launched and we were the first to demo it. We used it in a project for one of our clients. We used the desktop version but it's stored in Power Automate cloud. The solution is used for banking processes such as credit and debit transactions. We are partners with Microsoft and I'm the CTO.

We jumped onto this solution because it's very reasonably priced. The solution was for a medium size organization and they didn't want to spend a lot on such a product. It's a good solution for small to medium size organizations. 

Looping can be a bit tricky in Power Automate. In addition, the solution doesn't provide an option to view two to three conditions, you can only view one condition. It's not like that in UiPath. Deployment should be improved so that it integrates with WinAutomation. We can't write .NET code and we can't schedule the bot without using WinAutomation. If they could include that it would be helpful for our users. Right now we do the development in WinAutomation and later integrate with Power Automate.

We had good technical support. 

Installation is pretty straightforward. As mentioned, we were the first company so we had a call with Microsoft and worked with them. We're a start up so we had a maximum of six people using the solution. 

We use it to monitor the net flow of all the emails. It is really helpful.

It is stable. 

It should be faster and more user-friendly. 

I have been using Power Automate for around three years. 

It is stable and scalable. We have around 300 users. It doesn't require any dedicated IT to help run the appliance. 

We don't need much of their support. We have opened a ticket and their support was handy. It's very easy for us to communicate with them via email. 

The initial setup was easy. It was very easy for people to pick up. The deployment took a few hours. 

I would recommend it.

I would rate Power Automate an eight out of ten. 

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.