Microsoft Power Automate Reviews

The solution seems to have a good drag and drop functionality. 

It's very well automated.

The solution is pretty customizable. Even big automation tasks are done rather simply. If you want to do more, we've found that anybody can do it. Even a business user that has no knowledge of IT can jump on and figure it out.

Two or three years ago, in all IT products, there were a lot of standards that were missing. Now, using the cloud and using some EA tools, there is a huge scope of possibilities. It's much better.

The biggest problem right now is the fact that, when you use only the trial version, you don't have the whole power or capacity of what you can do with the Power Automate. 

The price of the license isn't that cheap. We want to see what it can do, fully, before purchasing. 

If you get a license, you can only have one developer or one user on it.

If you want to be more precise and the jobs to be more complete, it's somewhat complicated and there are some complex tasks that can't be done so easily by a business user. You'll need to get someone that's more highly skilled.

You need to pay for the ability to customize the solution. That's not an option on the free trial. You also have to be able to read some code in order to customize it. You need to be slightly skilled. You can only customize it on your own, only for you, and not for the other users.

When it comes to using UiPath or Blue Prism, there are more tools you can use. For example, Java or tools. It's easy to interact with them with UiPath and not so much on Power Automate. While Microsoft has a way of integrating well with itself and its own internal tools, it could do more to include external options and add them to the mix.

I've been using the solution for one to two months. It's pretty new for us.

It's largely stable. When Microsoft updates, it tends to update everything at once. Your Excel, Work, Power Automate, etc., everything updates automatically. That makes everything align so that nothing is out-of-date and affecting the stability of everything else at any time. In general, stability seems to be absolutely fine.

If it's on the cloud, it's generally easy to scale. The volume of data is viable. However, we haven't really attempted to scale anything. I haven't put everything onto Power Automate at this time.

I haven't really reached out to technical support yet. I don't have experience with them, so I can't gauge if they are better than other options.

From my experience, for example, UiPath technical support was not that good. I've used Automation Everywhere and I didn't find them to be very good either. Each time we have a problem with Automation Anywhere, they wouldn't give any explanation. They would always blame the issue on a problem with Microsoft and never with their own problems. Therefore, historically, we haven't had a good run with support at other companies. I'm not sure if this will be the case with Microsoft.

We've looked at and worked with UiPath, Blue Prism, and Automation Anywhere. We're doing comparison POCs with UiPath and Power Automate now. We're not likely to just choose one solution; we may end up using two. We'd like to have options to choose a few depending on the needs.

The initial implementation is not that difficult. It's on the cloud, so there's nothing to install. It's not exactly user friendly, however. UiPath is much more user friendly if you compare it to Power Automate.

In any case, you just connect it with your Microsoft login. If you want to automate a task, it's easy as everything is connected due to the Mircosoft account. It's easy to set up and concentrate your automation tasks.

Since we are on the trial version, we haven't bought it yet, or paid for anything.

If you are a small company, you can have a Power Automate license for as low as $30/month if you want to run one bot per month. It's pretty inexpensive.

With solutions like Blue Prism or UiPath, you need to think in one or five-year terms and many small companies can't just throw down $10,000 upfront.

We're a Microsoft customer. We don't have a business relationship with the company.

We're using the trial version of the cloud deployment model. We haven't paid for it yet as they have to do a benchmark within or the solution for some POCs on UiPath and on Power Automate to see the differences. 

In a lot of companies, they use Microsoft products. It's easy to demonstrate how it's important to have a Power Automate type of solution on hand.

Overall, I'd rate the solution eight out of ten. Power Automate definitely offers the best automation scenarios due to the fact that it's a Microsoft product for Microsoft products. I tried automating something, for example, in SharePoint, using both UiPath and Power Automate, and Power Automate was the clear winner. It was just so easy and seamless.

It's also great from the perspective of a small company as there aren't high costs up front.

We are using it for approvals and flow history. We are using the latest version.

The approval feature is the most important feature. We also use the flow history feature.

It is a very useful product as compared to other products. We can automate easily when a list is updated. We can also handle approval-related issues and integrate it with emails.

It can have customizations like enterprise solutions. In the approval section, there should be an option to reassign approval to some other employee. It would be good if we are able to create custom tables by linking to an item, and there is an integration with the HTML table through HTTP calls or Swagger connectors.

I have been using Microsoft Power Automate for around three and a half years.

It is stable.

I don't know. We have only four users. 

I never contacted them. I am purely on the development side.

It is sometimes complicated and sometimes very easy. It requires integration with a lot of connectors, such as SharePoint, PowerApps.

I highly recommend this solution. I would rate Microsoft Power Automate a ten out of ten. I am a fan of this solution.

We use SharePoint to collect information from tests, exams, and similar things that we do in our office. When people complete the tests, we use Microsoft Power Automate to collect the results and email them to appropriate people. We are currently using the latest version of Microsoft Power Automate. 

Its integration with SharePoint and Outlook is the most valuable. 

I found it very easy to use. I could do everything that I wanted very quickly, and I didn't have any complications at all. I never had a problem in using Microsoft Power Automate.

If someone was just about to start using it, it would be better if it was a bit more user-friendly in terms of understanding function references. I come from a bit of development background. To me, it all makes quite a lot of sense, but someone using it for the first time would probably battle understanding how the functions work. This might be something they could improve on.

It would be really useful if it could publish data to Power BI. We like to use Power BI for our reporting, but we can't directly integrate the data across. If there was a way to automate the collection of the data and push it straight into the Power BI platform, it would be quite useful.

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

It seems to be very stable. It has been running now for about three months, and it regularly gets used, probably about 30 times per day. I haven't had a single missed event. I have received all the emails, and everything works great. Today, funnily enough, I have started building a new solution for something similar. So, I went back and actually checked the records for the last three weeks, and everything was perfect. I haven't had any issues with it at all. 

I am sure that it is going to be perfectly fine for what we need. We are looking at about 30 people using it in one day over the last three months, which is not a very high volume. We are not going to do more than probably a maximum of 50 users a day. 

I did not have any need to contact them.

Previous to this, I used Microsoft Flow, and before that, I used the SharePoint workflow. We switched from Microsoft Flow because Microsoft actually changed their product and went from one to the next. It used to be Microsoft Flow, and then they revamped it and re-introduced it with a new name. I just carried on basically using the same platform. It is better than what they used to have. That's for sure, but I'm still effectively using the same product. They had advertised through emails and other mediums that they have switched to a new product, and it has been rebranded. I thought I'm going to try it, and I just found it very friendly and easy to use. So, I just stuck with it.

It is integrated completely with our Office 365, so I didn't have to set up anything. Everything just works automatically. The security works from the first time. When I logged in, it straight away identified me. I could immediately get a list of all the people to whom I needed to send the stuff. It connected straight away to the SharePoint. I didn't have any problems at all.

The original product was set up by the consultant firm that looks after our IT. We don't do it on our own. They set up everything and configure it. All I had to do was just log in and make sure everything works the way I wanted it to do.

I don't deal with the financial side. I know that we pay for a per-user license. It is probably less than $20 a user, but I am not sure about the exact figures.

To use this solution, you need to maybe brush up a little bit on how to use the function references that are available in Microsoft Power Automate. The code that you use for the functions is a little bit different from what you would use if you were using Excel or anything like that. So, you just need to brush up on how the functions work. Once you understand them, it is pretty simple.

I would rate Microsoft Power Automate a ten out of ten. Everything has been perfectly fine. I am a happy user.

This is one of the solutions we sell to our customers. I'm an automater and we are customers of Microsoft. 

The connectors are a very good feature in this solution because they allow you to connect to multiple applications within the Microsoft environment. The solution is readily integrated. 

I'd like to see an improvement in the execution of workflows, which is currently an area of concern. It takes a lot of time and when you integrate these workflows, you have to be very careful because even a tiny error can break the workflow. Microsoft needs to make it more resilient.

An additional feature should be interoperability. It's the idea that you should be able to leverage other Microsoft technologies, let's say .NET, C#, VB macros, so that they can be integrated. It will make the solution more powerful, and they could provide a facility where we could run scripts written in other languages through Power Automate seamlessly. That would make this a very powerful product. 

I've been using this solution for 18 months. 

It's not stable yet, because it's still in development. There are a lot of things happening right now. If they bring in a new feature, an old feature can change and that's why we're not able to deploy it fully on all our client premises.

It's scalable because almost everything which is available within the Microsoft environment can be connected. But when you go outside the Microsoft environment, with respect to legacy systems and with third-party applications, the scalability is a somewhat limited right now. You can't connect very easily to Oracle or SAP or even third-party standalone custom applications. We don't have plans to increase usage for the time being. 

We haven't contacted technical support, mainly because we've been in a Microsoft related environment for the last 30 years. Most things that we solve ourselves, rather than talking to Microsoft.

We have not yet fully switched to Microsoft Power Automate. We still consider it an option for clients who are purely in a Microsoft environment. It's definitely an option, but we also have seven other RPA tools we use including UiPath, Automation Anywhere, Blue Prism, Kryon, Kofax. We also have an option for customers who don't want to go for any RPA tools that enables them to get custom automation.

The initial setup is complex. You need to know what you are doing, because it connects to so many things on your system which could be different for different systems. It took us about half a day to understand what we needed to do, and then after that it took just an hour. We did it ourselves. 

The solution is affordable and supportable, but the licensing is complex because you're paying for multiple services. You pay a license for Automate and a license for Azure Cloud. There could be a situation where you're managing more licenses than the bots.

We have evaluated 22 options in this area. 

Choosing a solution really depends on what the customer needs. If they're looking for something that's easy to maintain, we might go for UiPath or Automation Anywhere. And if we don't have the budget we tell them to look at Microsoft Power Automate. If you don't have a budget for that, then you look at a custom automation which doesn't need any RPA tool. It all depends on the customer's requirements and constraints.

This solution has the potential to go further, but for now I would rate it a five out of 10. 

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.