Microsoft Power Automate Reviews

We are resellers and sometimes we implement solutions.

It's a component of Microsoft 365.

We use this solution to match some documents or spreadsheets, to match data from one spreadsheet with another, and to download and load invoices.

We also use it for an approval flow.

The most valuable features of this solution are the automation interface and the RPA automation.

The BPM component needs improvement.

Microsoft doesn't have certification training for Microsoft Power Automate, like other solutions such as UiPath, Kofax, and Automation Anywhere. All of these products have certification training available.

Power Automate is part of a suite called Power Platform.

Power Automate can integrate into a business intelligence component like Power BI, a flow component like Flow, and a bot component like Virtual Agents. 

Power Automate can make that cross to these components for better results of all the data that the client wants to see, and wants to automate.

I have been working with this solution for almost two years.

It's very stable, it doesn't have any crashes. 

The only issue is when we don't have an internet connection, it crashed because it's a cloud solution and not on-premises.

It has many connectors to other vendors or other components or other programs that make the solution scalable.

It is very easy to deploy with other vendors like Power Automate versus SAP. You can connect SAP with Power Automate very easily and extract information from the SAP environment.

It's a scalable solution.

Our clients are medium-sized companies. We have anywhere from 16 to 100 users.

Microsoft has the team to analyze every incident. In my experience, they have teams that can process incidents for my clients.

I am satisfied with technical support.

The initial setup was easy and it took a week or two weeks to deploy.

We have a team of two or three people to deploy and maintain this solution.

Our clients also evaluated UiPath and Automation Anywhere.

UiPath and Automation Anywhere are leaders in Gartner Magic Quadrant. Microsoft is the challenger. 

Our clients are aware of these evaluations.

I would recommend this solution to others, but first, they should evaluate it. Do a PoC of the tool and evaluate the business purpose. Review the results before making the purchase.

In the beginning, Power Automate was called Flow, and it was very basic to easy to manage. During the last year, there have been many improvements from Microsoft that have taken it to the next level and can compete with UiPath and Automation Anywhere.

I would rate Microsoft Power Automate an eight out of ten.

We're currently exploring the solution. We're doing some planning and testing. We're looking at data transformation and flows.

There's the potential to save a lot of time by reducing the time it takes to do processes. It may even save us costs.

We're looking to monitor more projects in the future, however, right now, we're mostly in the testing phase. 

The tool is very good at implementing automation within processes. It's saved us from doing a lot of manual processes.

The tool is very effective. 

The features on offer are very good.

The product gives us a lot of very useful metrics that we can use.

The entire solution is extremely user-friendly.

There's good documentation online and I find the solution offers pretty good overall communications.

There are some gaps and a few areas of the solution that are still a bit complicated and confusing.

I've had issues with reordering columns. When I tried to do it, it seemed to take a long time, and then, later, it gave me some kind of error. 

We've only been using the solution for the last two months or so. 

The solution is quite stable. We haven't had any issues in that sense. It's reliable. It doesn't crash or freeze. It's not buggy. It's been good.

I'd say the solution can scale. We haven't had any issues in that sense. If a company needs to expand it, it can do so.

In our case, right now the users are minimal. We have maybe five users in total. Some are in IT and a few are in other departments.

We likely need support at this time. Mostly we've been dealing with online assistance and documentation. We're testing the product. To get it up and running, we'll likely need some help and may need to reach out to technical support to get asssitance.

The initial setup isn't as straightforward as we hoped it would be. We had some issues specifically with the initial configuration. It was a bit difficult.

Deployment times vary. For us, it might have taken about four weeks or so.

We handled the implementation ourselves. We did a bit of research and tried to tackle it internally. It was just to get started. When we do a bit more of a complicated setup, we will get some consultants to help us with the process.

I'm not sure of the cost of this solution. Licensing and billing are not aspects of the product I deal with at this time.

While we know there are other tools on the market, currently, we're just playing with this particular tool to see what we can do.

We have looked at UiPath, however, we haven't tried implementing it yet. We just know it is an option.

We have a partnership with Azure. 

I'm using the platform from the desktop version coming with Microsoft 365. I assume it's the latest version of the solution.

Based on our preliminary usage, I do recommend the solution. It is easy to start with and to try out. It's pretty user-friendly and, and there's so much documentation on how to use it. There is other information about use cases as well and some pretty good videos on how to do certain things. The community seems to be pretty strong, which is helpful for when you are starting out.

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

We use the solution in insurance and pharma.

I use SQL Server connectors to connect SQL Servers for data integration.

The most valuable feature is the Office connector, which connects to Excel and Exchange.

There could be more communication with third-party cloud tools. Also, if they can use libraries, I can recycle functions without having to rewrite them in any Power Automate system.

I have been using Microsoft Power Automate since its inception.

The solution's stability is good. Everything works fine.

The solution is scalable.

When the first versions were released, some issues needed to be addressed. However, after those were resolved, everything started to run smoothly.

Positive

Deployment takes around three or four days, and one specialist is required.

I rate the initial setup as seven out of ten, where one is difficult, and ten is easy.

It is a low-priced solution and costs around 15$.

Overall, I rate the solution an eight-point five out of ten.

We use the solution as a business process automation tool. It allows one to automate an application in his organization. 

The solution is not only meant for SharePoint, but for everything.  It has millions of connectors. The best feature of the tool is that it is generic, so it allows one to do as he wishes. He can obtain data from Twitter and put it on his SQL Server. He can obtain data from WordPress and connect it with IBM. 

The solution could have more integration with different platforms. 

The licensing price is too high. 

Microsoft Power Automate has only been released recently, so I have been using it for the past three or four years. 

The solution is certainly stable. 

The solution is definitely scalable. 

Technical support is very nice. It's fast. 

As the solution is cloud-based, it does not require installation. 

The solution does not require deployment, but a team is needed for development and this will vary with the scope of the project. Every site would require around eight to ten people. 

The licensing price should be more cost-effective. 

As we are talking about a Microsoft product, the licensing can be purchased on a monthly or yearly basis. 

The solution is both cloud-based and on-premises. 

We are consultants of Power Automate. We do not use the solution ourselves. 

So far, we have handled 14 or 15 projects and are working on one at present. 

I would recommend the solution to others. 

I rate Microsoft Power Automate as 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.

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.

I really like the built-in integrations with other applications like Teams. The product is also straightforward and easy to use.

Sometimes it can be difficult to share flows for multiple users to edit. So, it is a potential area of improvement.

For additional features, it would be helpful to have a more collaborative building of flows.

I have been using this solution for four years.

It is a stable solution.

I never needed customer support for this product. It is easy to use.

The initial setup is easy.

Overall, Microsoft Power Automate is an eight out of ten.

It is currently being used by our customer service department. They're using it for tracking overtime, and they're also using it for reporting and automating their various service quality reports. So, automation of service quality reports and overtime management are basically two major use cases.

The ease of use and the integration with some of the existing products that we have would be its main takeouts.

From an improvement perspective, Microsoft just needs to make sure that they have a real enterprise RPA tool. PowerApps and Power Automate are still not at the level of UiPath and Automation Anywhere. It could be because Automation Anywhere and UiPath have been in the market for quite some time. It's just about Microsoft increasing their focus in terms of product reviews and development and making them competitive products that one can consider at an enterprise level. Right now, their use cases are limited as compared to what one would consider doing with UiPath and Automation Anywhere.

It is a stable solution.

It is scalable, but it is limited in terms of the processes that you can automate. If you have complex processes that you want to automate, it doesn't have that capability yet. So, it is scalable but to a certain extent.

Our organization is working with it actively. Its number of users could be between 100 and 200.

Technical support is given by Microsoft through the support model that they offer for customers. If you have an issue, you can log the issue in with Microsoft, and they would always attend to it. I would rate them a three out of five.

It was straightforward. There was nothing complex.

You don't need much staff for deployment and maintenance of it. You need a very limited number of people.

We used a partner.

Its license is a part of our enterprise agreement. It is a three-year contract, but we pay yearly. So, it is a yearly license. There are no additional costs.

I would rate it a six out of 10.