Microsoft Power Automate Reviews

We are using Power Automate to send notifications when working with items in SharePoint. It is used to send notifications when a document is moved or needs to be approved. When a document needs to be approved in SharePoint, we send a notification to the user who needs to approve that document. I also use Power Automate to create a work item in another system, such as Azure DevOps.

I like Power Automate because it is very easy to use for users who don't have IT knowledge.

They can improve the description of errors and provide more details. Sometimes, when I receive an error, I can't understand what is wrong.

It would be useful to have a desktop version to modify or edit workflows. Its scalability can also be better.

I have been using this solution for five months.

It is stable.

It is scalable, but its scalability can be better. We have 10 to 20 users of this solution.

We have a contract with Microsoft for premium support. We have support all the time, and they are good.

Its initial setup is easy. The deployment duration depends on the complexity of the deployment. It can take a week or a month.

To know about the best practices for this solution and how to make it more secure, I would advise others to read the information on the web.

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

The solution can be primarily used small process automation of day-to-day activities, such as routing of emails, Excel sheet manipulation, and more.

The solution is very scalable.

The solution is easy to use. 

The initial setup is pretty straightforward. 

Technical support has been great so far. 

If a company already uses a lof to Microsoft applications, this solution is great. 

The solution should offer similar features that users can easily access if they use Automation Anywhere or UiPath.

It would be great if it was able to integrate more with various other platforms. It would make development easier. 

I've been dealing with the solution for two years at this point. 

The product can scale well. If a company needs to expand its use, it can do so.

Technical support has been great. They are helpful and responsive and I have no complaints. 

I'm also aware of solutions such as Automation Anywhere and UiPath. They, at this point, are much more feature-rich.

As a cloud-based solution that is very easy to implement. It's not overly complex or difficult. It doesn't take too much time to deploy.

You only need two or three people to deploy and implement the product in an organization. You don't need a big team. 

The solution offers a yearly subscription package. 

I'd rate the solution at a seven out of ten. Currently, we have ten customers that are using the solution. 

I would recommend the solution to other companies and users, however, only if they have a Microsoft suite of products that are in use and they already have a license based on that usage.

This solution is used for the automation of simple processes that are repetitive and very low on decision branching and error handling.

It's easy to learn.

The barrier to entry is low. The downside is the lack of orchestration and supplemental tools such as capturing existing processes and using them to build out.

I worked on a demo side by side with UiPath Automation and Power Automate.

I didn't see any issues with the stability of Microsoft Power Automate.

I would say that scalability is probably a weakness.

It's an area that needs improvement.

If you have a good enough support plan, it's fantastic, but most businesses don't.

When I was working at a customer site that was a premier customer, we had onsite Microsoft service providers, and we were able to leverage their worldwide support. At that point, you can have round the clock, follow the sun support on a critical problem. 

But in 35 years of working with Microsoft, I've only seen one customer site that had that level of support. If you don't have that level of support then you are basically on your own.

The setup for me was almost non-existent because we already had Office 365. 

When it comes to the admin side of that, I don't know.

The price is right. If you have Office 365, it's included.

If you're looking for entry-level, inexpensive, and you're already an O365 customer, then this might be a consideration. But if you're looking for an enterprise tool, you should probably keep looking.

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

We are system integrators so we provide this solution and deal with the automation for our clients. Power Automate is mainly suitable for small and medium size companies. 

Power Automate is good for automation. For example, if a client requires a format for invoices, we set up the module - invoice number, container, quantity, product details. After that, whenever we load bulk invoices, it automatically identifies the invoice format and accepts the data. This is one of the best features of the product.

Power Automate is not suitable for connecting other applications like browsers and third party applications and there are a few features not available on this solution. They are working on improving that. Power Automate cannot handle high end projects and, from a developer's perspective, it's a little difficult for enterprise size companies. 

We are partners with Microsoft and I'm a technology lead.

It's a reasonably stable product but because it's a new tool they need to keep working on it. If you're a small setup, and you need it for Excel or Word or some desktop kind of access, it will be stable. But if you're looking for web automation it's not currently suitable.

This is a scalable solution. 

We have tried to contact technical support many times, but there is no way to contact or reach out to the Microsoft team. We recently had many questions on Power Automate so I tried the Winautomation but there are many activities that are missing and there are bugs in it. We also had an issue with the ongoing live projects. We developed the project in Winautomation and they were later converted into Power Automate. Winautomation isn't working so we need to migrate all the projects which is a complicated process and requires reworking. We can't get any help from them and that's a problem. 

It's very easy to set up because it only requires downloading one xFi file from Power Automate. It then automatically connects with an email account and the solution is automatically synced with that email account. From the customer's perspective, there is no maintenance. As the service provider, whenever new features are included, we update it for our clients.  

Compared to other automation tools, Power Automate is very cheap although the price has increased recently. 

We also integrate UiPath for our clients. This solution offers regular updates and is more mature than Power Automate. Each month they release a new module. Initially, they were only accessing desktop and web applications, Word and Outlook, those kind of things. Nowadays, UiPath has all the features connected to the cloud, whether it's Azure or Google. They are trying to automate everything and they're working on all this because of AI. When choosing a product for our clients, we take numerous variables into account. If you're offering all the features in your tool and the cost is reasonable, we're likely to choose it.

I'm not sure I would recommend this product now, perhaps in a year or two when the solution is more stable. We struggled with a project recently and that was difficult.  

I rate the solution a five out of 10. 

The primary use of the product is for automating business processes.

The templates on offer are very good. It's quite helpful to have them.

The initial setup is fast as there really isn't anything to implement if you use the cloud.

Overall, it's been a positive user experience.

I've had some issues with the stability.

I've only been using the solution for a few weeks. I don't have a lot of experience with the solution just yet. It's still quite new to me.

The stability is not very reliable. I've had some issues. 

I can't speak to the scalability of the product. I haven't used it for that long just yet and have not attempted to scale it. Therefore I can't really speak very well to its potential capabilities. 

I've never been in touch with technical support. I cannot speak to how responsive or knowledgeable they are as I have not had an opportunity to communicate directly with them just yet.

I did previously use another solution. I've used UiPath in the past.

Only the desktop version has an installation process. You do not need to install anything if you use the cloud version. It's quite straightforward. 

I'm a student and an end-user. I don't have a business relationship with Microsoft.

I'm writing my thesis about RPA, but I don't have much developing experience.

I'm using the latest version of the solution. I am unsure of the exact version number.

I'm using the trial version of the product.

I have not decided if I will keep using the solution going forward. 

Although the solution is still new to me, from what I have experienced, I would recommend the solution to other organizations.

I would rate it at a seven on a scale from one to ten.

Internally, we're doing a lot of workflow automation. This includes creating documents inside of SharePoint, updating SharePoint lists, taking templates in Microsoft Word, and then pulling data from SharePoint to populate different fields in the Word doc using the approval workflows.

When somebody is done reviewing a document, they click a button, and then it goes to the next person in the workflow. It sends me emails, sends notifications, posting from an email, stripping out all of the extra content in the text message, manipulating it, and then posting it to Microsoft teams, channels.

The most valuable feature of this solution is the native integrations with other Microsoft products. These include SharePoint, Office 365, and Microsoft Teams. 

The integrations that are built into Power Automate for those different Microsoft functions are good.

This solution has many areas that have room for improvement.

There are many features that are lacking compared to other Automation tools.

There is an inability to group different variables. When you have to establish all of your variables, you can't group them all.

The notifications when there are failures need improvement, as well as being able to start a process midstream.

The licensing is convoluted in understanding what license is needed.

There's just not enough error handling natively, so you have to build in a lot of workarounds for error handling. 

When compared to other workflow automation tools out there, it's just not as mature.

I have been using Power Automate for one year.

We are using the latest version, it's a cloud solution.

For the most part, it is pretty stable. We made one change that created a licensing error just out of the blue that stopped all of the processes that were in progress.

It created a problem, where we had to restart all of them and do a lot of manual cleanups, and backtrack to the ones that were canceled.

If there's a licensing issue, there should be some notification versus saying, "your licenses are out of compliance," and shutting down that process. When we checked the licenses, there was no issue.

I don't know if it was a bug or what that was, but that happened one time. Luckily it was when we started the rollout, and we didn't have as many processes in flight.

If we had hundreds of different processes in flight and that canceled my flow, that would not be acceptable for a production-type solution.

It's not scalable.

For some of the processes that we're building right now, we are asked to add a button for this additional piece, and it adds so much more complexity with the way that I have to build it out. It doesn't allow me to break up a process into multiple processes, and then call sub-processes, which would make it a lot easier to scale. When I break up these different processes, I have to redefine every variable. 

I can't take information from one process and then pass those variables to the next process.

Your workflow then becomes this very long, single process, that can't be started from the middle. It has to be long and convoluted, and it doesn't make it simple to scale and have sub-processes to make it more complex.

Currently, we are limiting the number of additional features and functionality. 

We don't want to add to it because it adds complexity and doesn't give us the ability to call a sub-process.

The couple of times that we have called, they haven't been able to solve anything.

In many cases, we try to figure it out ourselves or rebuild the workflow, if we can't reproduce the issue. 

The initial setup is pretty straightforward.

We built out the workflow, completed the testing, the user testing, and completed a production rollout. 

I would say part of the challenges was with the production rollout. The tool is not as easy to work with because it's a hundred percent cloud-based.

A lot of the error handling and some of the things you would normally have aren't built-in, and so we ended up finding a lot of bugs and issues and things after the fact.

For example, it was set up where we needed to send an email, and if you put the two email addresses, but you don't put a semicolon between it, then it was just killing the process, saying, "that it couldn't send the email," so it just failed. The entire process failed.

It didn't send a notification and we had to find out two days later.

Those are the types of things where it just needs to have better handling for those types of situations to be able to say, "this is an error that happened," or let me kick off that same process from that point, and then restart the process from there; whereas, right now I have to restart the entire process.

All the steps that happened before, need to be able to go manually and clean up. It eliminates the point of automation.

The price depends on the features that we are using.

The licensing cost for us at this time is between $8 and $20 per user, per month.

It's a monthly cost for every user that touches one of the flows or is kicking off a workflow.

Licensing can get expensive.

There are premium connectors, where if you want to connect to external data sources, there is an additional cost for that.

I think one of the big issues was for an Azure SQL database or for SQL databases that used to be part of the standard connectors, and then they converted those to premium connectors, which increases the cost and limits the functionality for what you would be paying for it.

Use it for basic workflows, but I wouldn't recommend it for anything that is mission-critical. I don't think that it is ready for mission-critical type processing. 

It's a good product. They just have a lot of functionality they need to add.

People have posted on their feature request board, and on their community board.

The vast population that is using it asks for the same features. They are either very slow to implement those features or they are not interested.

I would rate this solution a six out of ten.

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.