Microsoft Power Automate Reviews

The solution has helped our company with automation. 

Microsoft Power Automate is an easy-to-understand solution. 

The tool should improve its price. 

I have been using the solution for three months. 

I rate the product's scalability an eight out of ten. 

We haven't activated technical support since it's expensive. 

Microsoft Power Automate's setup is easy. 

I rate the solution an eight out of ten. 

We primarily use the product for credit card operation customer complaints.

The solution is great for some of our backend processes, for example, accounting and financial processes, and also for IT batch processes. 

The solution is very easy to set up.

The initial setup isn't too difficult. 

I heard from my team that it's quite immature. If you compare it against Automation Anywhere and Blue Prism, it seems there is less experience in the product. The desktop version of the on-premise solution seems as if it's not as mature as Automation Anywhere.

We need a more powerful desktop option.

We started using the product this year. We've used it for about four months at this point. We're using it for three processes. 

We haven't used the solution for too long. We are at the beginning of automation. We are not ready to escalate just yet. However, we do plan to increase usage in the future. 

We've contacted local support in the past. At the time, it was just a simple question, as we have developed a simple process. We've just had small questions and issues.

Currently, we are also using Automation Anywhere. 

The product is easy to set up. Actually, we're a very large Microsoft customer. All of our solutions are mostly Microsoft. All of the security fields are already solved by Power Automate, which makes it easy to implement and to set up. It's not a problem at all.

Each process took us about two months to set up. Since we define them, it's quite easy. The operational processes are very easy to maintain and to operate. There are no issues with that. It's a simple three-step process, it's not a complex task.

We are looking for automation and are looking at options such as UiPath and Blue Prism.

We are looking for some solution for logistics.

We are a customer and an end-user. 

We are using the solution on our desktops, however, I don't know which exact version we are using. 

I'd advise other users that it is very simple to implement Power Automate, however, new users have to be careful with how they expand it and develop complex processes. That said, we don't have experience with processes more complex than a one or three-step process.

I'd rate the solution at a seven out of ten.

We primarily use the solution for testing. For example, we made a website solution and we're open to trying new things because it's not on production yet. We use your flows in order to make some data automation. We fill our flows with some data and test to see if it's all correct.

The RPA robotic process automation is a good feature. We can make a flow within a flow. We just made a UI flow. The flow is to run every day so far it's been quite helpful.

There's good Microsoft documentation that makes setup easy.

I am now a member of the digital transformation team, so we are making various products. We are just making the new projects, and developing them in the store. However, everything is new to us. We have are not working with this tool for more than six months. Therefore, it's hard to really know how well it works or what is lacking.

The solution needs more features so that it can better compete with competitors that have been on the market longer and are more mature.

Tech support could be more hands-on. Right now, they simply direct users to documentation instead of directly dealing with issues.

We've only just started using the solution. We have been using it for six months so far. It's been less than a year.

The stability of the solution is quite good. We're not in production, so we can't verify it 100% as we're just testing its capabilities. It's a rather new tool as well, so I don't know how much it's been tried and tested overall. However, overall, from what I've witnessed, it's been good.

The solution is quite new, both for us and on the market. I can't speak to the scalability as we haven't tried to scale it, and I don't know if many companies have really tried.

Although we have about 1,500 employees, we're still testing the solution, so not everyone has access to the product. Maybe five or six of us are actually on it and trying it out. We're all programmers.

As a developer, I can open a ticket with Microsoft, even though our DBA did teach us a lot about the solution. There's a lot of documentation and support online, so there's rarely a reason to have to actually open a ticket. So far, we've been satisfied with the arrangement, although, for the most part, their assistance is simply directing users to specific documentation.

Currently, we're just testing this solution, however, our organization is also using UiPath.

The initial setup isn't too complex. It's rather straightforward. You can just follow the documentation provided. Microsoft makes it very easy.

The solution is offered as part of a larger Microsoft license. It came as a solution in a bigger package. I'm not sure what the exact cost of it it, as it's not my area of expertise.

We have the Microsoft Dynamics Customer Enterprise license, and that covers for Automate and VI. Right now, we are doing some tests.

We're just working with four workflows. We're just really starting and haven't begun any big projects yet. We have 15 ongoing small projects.

I'm not sure of the exact version we are using.

I'd rate the solution seven out of ten. We're still testing it in production. We need more time with it to really get a sense of what it can do.

We are using Microsoft Power Automate for automating approval.

The most valuable features of Microsoft Power Automate are user-friendliness and low coding functionality.

When you try to create a flow or work on the flow in Microsoft Power Automate you cannot undo changes. There are no options to edit or, undo an action. This feature would be useful. The editing option within the flow can be enhanced.

In a future release, they could extend the flow run limits. When the flow is running it will be terminated.

I have been using Microsoft Power Automate for approximately three years.

Microsoft Power Automate is reliable.

I rate the stability of Microsoft Power Automate a nine out of ten.

We have five developers and IT managers that are using the solution.

The solution is scalable.

I rate the scalability of Microsoft Power Automate a nine out of ten.

We opened a few tickets with support from Microsoft Power Automate. The support is responsive.

I have not used a solution similar to Microsoft Power Automate.

We did the implementation of the solution in-house.

The solution is managed by the global tenant. We have three people who manage it.

I would recommend this solution to others.

I rate Microsoft Power Automate a nine out of ten.

We are using it for automating legacy systems as well as email verifications. I haven't touched on the APIs yet, but the use case is for user accessibility to and from data sources.

The solution is still in the development phase. It is not in the production run at the moment. Therefore, at the moment, there is not a significant visible improvement.

In terms of deployment, it is a mix of hybrid cloud and on-premises. Microsoft is the cloud provider. It is a single environment deployed over multiple branches in each province of the country. Currently, the version that we are using is the latest Microsoft release.

Its ease of use is most valuable. A lot of the bulk functionality is done either through standalone or custom connectors and standard API processes. 

There are two versions of the automation suite. You've got your cloud functionality, and you have got your on-premises functionality for legacy systems. There are a lot of functionalities between the two systems that don't cross-correlate with each other. A lot of the functionality in the cloud system is not there on the production side in the on-prem system. If they could implement some of the similar functionalities and streamline them for integration, it would be a lot easier. There should be seamless integration between the two systems.

I have been using this solution for three months.

It is highly stable with good performance.

It is extremely scalable. It integrates with a lot of existing systems, both Microsoft-related and non-Microsoft-related, and it is extremely extensible. The additional support validation and software integrations that are available are limitless.

Our experience of the technical support on the solution has been minimal because there have not been a lot of technical issues with the implementation. The turnaround time for any type of technical query is usually a day to two days, but before that time period is up, they either have a solution or a guaranteed workaround.

We previously used Automation Anywhere. We switched because of the ease of use. The functionality of Automation Anywhere is for a very specialized use case scenario. They focus on a lot of areas, but Power Automate has a lot of simpler solutions and easier approaches. For example, we have a solution in place that has three or four RPA scripts for a single process. With the Power Automate solution, we have a single script running for maybe five sub-processes. It is a lot more streamlined and consistent.

At the moment, it is still in development and is a matter of integration. It does require a bit more technical know-how, but it is mainly done from the environment perspective and from an administrative point of view. 

From a development point of view, the crossover is pretty much the same for going, for instance, from Blue Prism to UiPath, or UiPath to Automation Anywhere. There's a transition period level of difficulty. So, from a development point of view, it's fairly the same, but from a technical point of view, Microsoft does require a bit more technical know-how to get the environment set up.

With some of the integration conversions we've done from one platform to the other, from a development standpoint, it has taken us close to a month in the development environments, and this is interrupted. If we had an uninterrupted conversion, I would estimate a maximum of a week. We just need to get it converted and implemented.

We've been doing everything in-house with direct help from a Microsoft representative. We have a single person to take care of it. It doesn't require a massive deployment team.

So far, based on the development calculators that we've been running, it's running far smoother and far more efficiently and faster. So, the estimated return on investment over the past three months that we've been calculating has been looking far higher than the Automation Anywhere solution.

At the moment, from our experience with the two, Power Automate is a lot more expensive solution than Automation Anywhere, but it is also a far more reliable solution. 

With the price increases and with the current pandemic situation going on worldwide, a lot of the prices have fluctuated, but the packages and the all-encompassing features you get with the Microsoft package far outweigh the benefits from the Automation Anywhere side. Each package on the Automation Anywhere side is cheaper, but we need to continuously purchase subsequent packages to continue with our automation to the extent that we require. So, the Power Automate solution is a bit more pricey, but it does offer us a far better range of capabilities.

There are different development plans that you can use. Additional licenses might be required for additional features, such as your Azure Logic or your Dataverse capacity. There is a limited capacity package that you can purchase, and then you have to have an additional license for added capacity.

I would advise paying critical attention to the environment that you're setting up. User access roles, either through Active Directory or through the database control method, should be the key focus. After that, you need to assign roles and licenses as necessary. From there on, you need to integrate the system. 

The Microsoft documentation portal for both cloud and on-premises is going to be the easiest to follow. All the solutions are there. For technical assistance from the Microsoft side, contact details are available on the documentation portal for any type of query.

I would rate it a solid eight out of ten. For me to give it a ten, there should be seamless integration between both the cloud and the on-premises solutions. There should be the exact same or similar functionality between the two to make the entire automation process a bit more streamlined.

I like that Power Automate gives us a connector to be able to connect different data sources or different software. 

It is very easy to connect, authenticate, and automate our daily routine tasks.

There are many things that need to improve, but not with the cloud side, it's desktop automation.

When you are doing desktop automation, they do not have a clear structure to create the code. This means that we have a poor chance of creating the project.

When creating sub-flows, there are no separate parameters. Instead, they are all combined together on the main page.

I would like to see improvements made to the Power Automate Desktop.

I have been exploring this product for one month.

Previously, I worked with Blue Prism and UiPath.

In my opinion, Blue Prism is far better than Power Automate, and UiPath is better than the desktop version.

Power Automate has the power to connect with different cloud sources, which is something that Blue Prism and UiPath do not have.

You can also create reusable code with Blue Prism and UiPath.

We are using the cloud version. There is nothing to install on our machine.

If you need to automate more on the cloud side, I would recommend Power Automate. If it's a third-party application they are trying to automate, I would try Blue Prism or UiPath.

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

We use Microsoft Power Automate for various personal initiatives of people to automate their own work.

It is used in a laboratory environment to connect the laboratory systems and to automate the connections between them.

The most valuable features are that it is low-code and simple.

For simple use cases, it is easy to use but as soon as it becomes complex then it doesn't fulfill the requirements.

It doesn't have any OCR capabilities. It doesn't really work with our ERP system, where we can log into the ERP system and have a robot updating it directly.

Microsoft is early on in this game and not really very far yet. They just need to mature their solutions.

In the next release, I would like to see a centrally-governed system, where you can access fully automated processes. This would include the ability to connect to other systems and log into them.

I would like to see it as a centrally managed solution.

I have been using Microsoft Power Automate for six months.

We are using a local partner of Microsoft in the Netherlands, and it's going quite well.

At the moment, we're using both Microsoft Power Automate and Microsoft Power Apps. We also use Kofax.

If you are using it as a user, I'm not aware of how complex it is for setting up central governance on it. But with proper RPA, you very much need the central-governance to ensure that things are conforming to standards. 

As soon as it starts being involved in business-critical use, then governance is very important.

I haven't seen that the central governing of it to be easy.

We use a local partner to help with the implementation and it's going quite well.

I am not aware of the pricing, but the problem is something we run into often. As soon as you want to use a data service, all of a sudden the license cost goes up. 

It's more fragmented licensing, where every little thing that you add, you get an extra license cost.

Microsoft is gradually becoming better, but for RPA, it's not fully there yet.

If you are looking for a low-code, simple to deal with email and extract a spreadsheet, then Microsoft is a good option. However, if you have a complex RPA use case where optical character recognition or PDF ingestion is needed then Kofax is a better choice.

I'm responsible for the center of excellence running Kofax as an RPA solution, and not for the Microsoft Power Apps.

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

We use the solution for integrating Microsoft Team and SharePoint. Also, we use it to manage document libraries and automation processes.

The solution's most valuable feature is cloud flows.

They should improve the solution's features for data and process mining. It is easy to run small automated tasks but difficult to build large complex flows. Also, it is challenging to scale it horizontally across multiple branches.

We have been using the solution for a year.

I rate the solution's stability as a seven. Its error-handling feature needs improvement.

We have three developers and ten end users of the solution. It is a scalable solution, and I rate its scalability as a six. But it could be better for large and complex cloud flows.

We often take help from online forums to fix errors instead of the solution's support documents.

Neutral

We use our in-house software as well.

The solution's initial setup process is straightforward and takes a day to complete. I rate the process as a nine.

We evaluated UiPath. It has better functionality and scalability. But, Power Automate is more accessible as our systems are integrated with Microsoft ecosystem.

I advise others to take some YouTube courses on how to build solutions for desktop and cloud flows.

I rate Microsoft Power Automate seven out of ten.