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.

We are using it for simple invoice management processing. We are using it for just storing documents with some workflows attached.

It is Microsoft. So, you get the integration capability.

The connectors and the integration capability can be improved. Microsoft RPA is a growing platform, and it is not yet particularly mature.

We just started to use Microsoft Power Automate. It has been a couple of weeks.

We haven't used it on a major scale at this stage. We're at the start of the journey. We have around 100 users.

Their technical support is okay.

Its initial setup was straightforward. It is a Microsoft product, so it is as simple as it can get as long as you've got the right licenses and permissions.

We use a third-party Microsoft partner. We have two developers for its deployment.

We are just using the free products at the moment. We are using the ones that come with the license that we have got.

We evaluated Automation Anywhere as RPA. We chose Microsoft Power Automate because Microsoft is part of our strategic solution. We've just implemented Dynamics, and that's why we started to investigate this solution.

I would recommend this solution. We are just at the start of our journey, and we are trying to understand its true capabilities. We plan to keep using this solution. We'll look for use cases.

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

Power Automate is a quite powerful tool. It helps you automate your daily processes. Being an RPA tool, it allows you to define certain logic and execute certain tasks at a scheduled time or for a certain event. I use it in conjunction with our SharePoint site to let our stakeholders know that something has been done or updated, and it kicks off another flow. We use it quite regularly.

Its usability is very valuable because it has a quite simple flow. It is very user-friendly. It provides you templates. I started learning with the help of Teams templates, and then I started providing them. It is always good to start with a template so that you understand how it works.

Its branches are quite user-friendly. You can put expressions in it. It allows you to link and test the flow so that you can check whether everything is running properly. From a business standpoint, Power Automate is quite good for a non-tech person. It is not like Java, HTML, or C++, which are very developer-driven. Power Automate is a more business-oriented kind of tool.

They can build more templates and more connectivity with other platforms. They can provide a more user-friendly way to connect with other platforms. They have their own in-built plugins for certain third-party vendors, but there are still a lot of third-party vendors that are not there.

I have been using this solution for over a year.

It is a stable product.

It is definitely scalable. If you want to integrate Power Automate with third-party software and other platforms, a technical person is needed. If you just want to connect Power Automate with Microsoft's suite of services, you can easily do it. They also have their own in-built plugins for certain third-party vendors. More and more plugins will come in the future because more and more people want to connect to Power Automate. I can already see Trello and Jira creating the plugins. There are still a lot of third-party vendors that are not there on it, but we can basically go ahead and create our own if needed.

Power Automate is a connectivity tool, so it has the ability to connect to other platforms. If they're able to do that, other platforms start making more money because I can get a flow that directly connects to another vendor and helps me achieve what I want to do, rather than having a tech person give me estimates and getting that done, which takes a longer time.

In terms of the number of users, we are a big organization with around 15,000 people globally. I don't know how many people use it, but the awareness is coming slowly within the organization and more and more people are becoming aware. I will continue using this solution.

I haven't actually reached out to technical support, which speaks for the usability of it. It is quite user-friendly, so I didn't really have to reach out to technical support.

I did attend a one-day workshop for Power Apps, which was great. For Power Automate, we actually have regular IT sessions. Our IT team has set up regular training sessions for learning different services from Microsoft, and one of them was Power Automate. That's where we got the awareness of Power Automate. That was a year and a half ago, and that was when we basically said, "Oh, wow, this is great!" At that time, it was called Flow. Now, it is called Automate.

We have it on our system. I don't really know if we need a separate license.

I would highly recommend Power Automate to anyone who is quite keen on RPAs and wants to automate certain processes from a business standpoint.

Microsoft is doing really well in this space. There are very few RPA tools, and Microsoft has been successful in penetrating the market. There are very few of them who are on every single PC. Any business, bank, or enterprise that has Microsoft on their PCs and has subscribed to this at an enterprise level are given Power Automate. The market penetration of Power Automate is really good. As more and more users start using it, they will obviously come up with issues. I definitely found a few challenges, but nothing with which Google Search couldn't help. More and more people are using Power Automate, and I can easily find answers on the web. It is already great, and it is going to go quite well if Microsoft goes ahead and starts building more of these tools.

I would rate Power Automate a nine out of ten. It is a great product.

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.

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.

We started using it just three months ago. These three months also include doing the proof of concept. We use it for IT operations where users can request for a software push by using a Microsoft Office 365 form. Using Forward Automate, I initiate the process. I have another department that is using it for requests for the PC team or for a contractor's visit to the main plant here in Panama.

It is basically free for me because it comes with my Office 365 subscription. The main feature is that there is abundant learning material on platforms like YouTube. You can find information about whatever you want to be done in Spanish or English without a problem. 

It is very easy to learn. Users can start using it on their own without any former training, which is something I like about this solution. 

It would be good to have some kind of on-premises solution for BPMN users, but I don't think Microsoft will ever go back to the on-premises solution. They all train their clients to use their online services.

It is easy, but it doesn't follow the industry-wide standards. I can only use the processes that Microsoft gives us. I can't map a business process by using other standards or notations, such as Business Process Management (BPM). I have to use whatever Microsoft gives us. I would like to have support for some standards because if we decide to use another BPM tomorrow, we will have to remap everything in notation to transfer from this solution. This is the only block or obstacle that I see in using this solution. It is closed in its infrastructure.

I have been using Microsoft Power Automate for three months.

I can't evaluate their technical support because I haven't had any issues. We have an enterprise license and subscription from Microsoft, which gives us 24/7 support in case we have any problem with the solution.

The most complex thing was setting up Microsoft Exchange Online. Our email solution was Google G Suite Email. Switching over to Microsoft was very difficult, and it took at least one week. We are a small company. We did everything in one day, but we had issues for at least one week after the migration because we transferred all mailboxes from Google to Microsoft. 

It is free with Office 365 subscription.

We have just started to use this solution. The next step is to have a dashboard to polish the KPIs from the data stored through this application.

I would suggest using this solution if you don't have any budget restrictions for automating processes. If you are a subscriber of Microsoft and you use Microsoft Office 365, I will advise using it right away. If you have a budget and you want a solution that designs specifically for business profits, I will suggest implementing some other solution such as the one from Pega systems.

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

We have clients in a number of different industries. We were evaluating Power Automate for a hospital in Kansas City. We were looking at a couple of different use cases with regards to their vendor onboarding and some of the back-office processes. 

The initial setup is pretty easy.

The entire product is pretty easy to pick up and learn. We've got some developers and some software engineers that have picked it up. We have RPA specialists that are are deep specialists in UiPath, and they picked up Power Automate relatively quickly. We have guys that are trained in multiple platforms such as Automation Anywhere or Blue Prism and they got it right away.

The solution lacks maturity. That will come with time.

The complementary suite of capabilities with regards to task capture and being able to self-document a process needs improvement. The whole document handling aspect, OCR recognition and capabilities, need to incorporate some more of an AI type of approach with document extraction and document handling. 

Being able to handle various types of forms and complex documents is important. Obviously, we handle a lot of documents like invoices that could have multiple formats and multiple pages of content, and very complex material contracts. That area is where it shows that UiPath has come a long way and Microsoft has a ways to go. 

If I look at the suite of tools that UiPath has, it's very robust and extensive. There are complimentary tools that help determine the applicability of a process. Being able to have tools that help assess things like a business case, savings, applicability, etc., relatively quickly, which we see with UiPath, for example, is integral to a good product. 

I've been using the solution for less than a year.

A criticism of Microsoft is that they typically bundle everything together, like with the Office 365 or Dynamics 365 or whatever the package of all the different options are. You get it whether you want it or not. The problem with that is, the content that you're giving away in the bundle is either not fully baked, or fully thought out or all that valuable. Some might be buggy or not do exactly what they are supposed to.

Clients are frustrated that they're getting stuff that they don't want. They'll ask us "why am I getting all these other packages as part of my bundle, that don't make sense?". I would rather see a really innovative and leading tool, rather than a whole bunch of tools that do lots of things. 

We haven't really reached out to technical support. We haven't really gone into production. Most of the issues, anything that we've had to do technically, we've figured out.

The initial setup is very straightforward. Our team picked it up really quickly. The question is if it's really solving the trickier problems on not. The more complex problems, is where the value is going to be. Process automation is becoming a commodity. Therefore, the differentiation is in really being able to handle the more complex problems, especially at an enterprise level.

We're able to handle implementations ourselves. We're a reseller and gold partner with Microsoft.

I'm unsure as to what the licensing costs are. It's not something that I generally deal with.

We're a vendor, therefore, we tend to use various solutions according to our client's needs. We've evaluated UiPath against Power Automate, for example.

We have evaluated Power Automate and we're trying to get some competency there. I don't believe it's to the same level as where you have the maturity as UiPath.

We've also looked at Blue Prism and found their capabilities quite mature.

I'm using the latest version of the solution.

We would typically evaluate the solution as an on-Cloud deployment. However, we would use either cloud or on-premises deployment models, depending on the situation. It's not implemented in our organization. We're a vendor or a partner. We provide services to implement it.

I'd advise other organizations that if you are looking for industrial strength, I don't think this solution is quite it. However, if you're poking around and are going to use it lightly, it might be a way to venture into process automation. It would allow you to try it out without a big commitment. If there are companies that are serious about it, it's probably not the right option. It's not ready yet. Microsoft is maybe trying other ways to build out the capabilities, through acquisition avenues. Therefore, I'm not sure if that's the platform to get. There will be too many growing pains.

Overall, I'd rate the solution five out of ten.

Microsoft Power Automate is a part of the Office 365 environment. Currently, 5% to 7% of our 19,000 employees use Microsoft Power Automate. It has already been connected to all the applications that our employees use, such as Outlook, SharePoint, OneDrive, and the ecosystem of applications that come with Microsoft Office. This is one of the primary reasons for using this solution. We are also using it for workflow approval and automated signature use cases to deploy a digital signature solution for some documents. It is all automated, from the client all the way to signing and storing the documents. 

It is a great solution for simple automation activities or simple automation of simple tasks.

It is also integrated with Office 365. Integration is an absolute breeze with any RPA software.

We expect Microsoft Power Automate to work like any other RPA software, but at present, it is fairly lax, especially in the RPA space. We have a very limited set of use cases today for Microsoft Power Automate. Microsoft should make it a full-featured RPA product like other solutions that we use, such as Automation Anywhere, Blue Prism, and UiPath. This is predominantly the area that they need to improve on. 

Microsoft Power Automate is quite complex to use as well, especially if you want to do advanced workflows or advanced automation. The regular simple workflows are quite easy and straightforward, but the moment you want to do something complex, it is almost impossible for one of our employees to work on it.

We have been using Microsoft Power Automate for about a year or so now. We are using the latest version.

It is absolutely stable.

It is definitely not scalable because we don't see this kind of use case. Scaling comes with the flexibility to use it everywhere, but we don't see that flexibility today. Therefore, scalability is definitely a question. We hope to see the product improve so that we can scale it, but today, we really can't do so. 

We don't usually call Microsoft for anything. There is absolutely no need for technical support. It is relatively easy. 

There is no installation because it is a part of our size offering purchase from Microsoft Office, so it was relatively straightforward to install. 

Microsoft deployed it for us, and they had a fairly large team. It took a long time, but I don't think it generally takes a long time. We had a very large deployment for around 19,000 employees. When I say deploy, I specifically speak of Office 365, which is the installation of Microsoft Office on these 19,000 end-user computing devices at the same time by using a new Active Directory. If you are specifically talking about deploying in Office 365 or Power Automate alone, it can be done in a matter of hours. You would need only one person to deploy it.

There is zero licensing cost. It comes with our Microsoft Office subscription.

We use both Automation Anywhere and Microsoft Power Automate.

I would recommend this solution for simple automation. We plan to continue using this solution if it gets better in terms of use cases, features, and scalability. It needs a full check-up in terms of functionality to be a fully functional RPA. 

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