What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
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.
What do I think about the stability of the solution?
Stability, it's fairly stable. They released a large number of fixes.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
How was the initial setup?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.