Microsoft Power Automate Reviews

We use the solution to automate internal processes like leave applications.

The solution is relatively easy to use and cost-effective. It is also easy to learn and understand. It is part of Microsoft 365, so it's free. Additionally, it is easy to integrate Microsoft Teams with the solution.

The UI of the solution is not so good. Power BI's reporting functionality should be improved. 

The next release should include more functionalities and better reporting.

I have been using the solution for three years.

I rate the stability an eight or nine out of ten.

I rate the scalability a seven or eight out of ten. Around 50 people in the organization use the solution, including five to seven administrators, 30 to 40 engineers, and nine to ten sales and marketing staff.

Previously we used Google Suite in collaboration with many other solutions. We needed it for process automation and for creating electronic signatures. It required us to subscribe to multiple solutions. However, we wanted only one or two platforms. So, we switched to Microsoft.

The solution is not so difficult to deploy. The deployment takes up to two hours. I could deploy the solution myself. One engineer is enough for the maintenance of the solution.

The solution is free with Microsoft 365.

I would recommend Microsoft Power Automate to those who use Microsoft 365. We search the instruction manual, FAQs, and other online documents when we face issues with the solution. Overall, I rate the product a nine out of ten.

We help clients integrate Power Automate into their processes. 

The solution is great for attended or unattended bots. It makes work easier. 

Most clients that use Office 365 find it very easy to use this solution. There are lots of great integration points. It can connect with various Mircosoft products, like Microsoft Dynamics ERP.

It allows clients to existing in one main environment, which is quite useful. 

The setup is very easy.

We use the connector to the cloud, and we have noted that sometimes there are delays. We've seen some scenarios hang. Sometimes there are issues with security policies within the company. Some parts get blacked. There are some drawbacks when we use it connected to the cloud. We need to convince clients to open some parts. This is often an issue that originates from the company itself, not Power Automate. 

Sometimes when we work with Microsoft Excel, the process is not much faster. The automation doesn't speed up as much as we would hope as they go through cells one by one. If it is a time-sensitive activity, that might be an issue and should be improved. 

I've been using the solution for two years. 

It is a stable solution. I'd rate the stability seven out of ten. The issue is that there are some security policies from the company side, or sometimes some updates that happen that can slow things down or stop the process altogether. 

The solution can scale well. I'd rate it seven out of ten. If a product is on a particular machine, if we want to scale up, we need to use another machine or account. 

The product can work for any type of company, from small to large. 

We've contacted technical support in the past, and it has been very good. We haven't had any issues with support and are happy with the level of service. 

I also use UiPath as well. We use either or, depending on the client or the requirement.

The main difference is the price. Microsoft is cheaper than UiPath.

The AI capabilities for Microsoft are very good. With UiPath, sometimes you even have to use modules from Microsoft. 

The initial setup is very simple. It is simple. It's similar to other tools.

We can help implement the solution for clients. 

The pricing is reasonable. I'd rate the affordability eight out of ten.

I'd rate the solution eight out of ten. We've been pretty happy with its capabilities. 

The primary use case for this solution includes automating process work with optical character recognition. Companies can also automate document processing with Microsoft Power Automate.

From my personal experience of using Microsoft Power Automate, I think that the automatic document processing feature is helpful for many organizations in streamlining administrative processes. It is a very good feature. It has helped many enterprises to process documents without spending much time on them.

I would recommend removing the AI Builder feature from the automatic document processing functionality. The tool can serve even better with free automatic document processing features, it shouldn’t only be available in the trial version.

I have been using this solution for a couple of months now.

I have found Microsoft Power Automate to be a stable solution.

It is a scalable solution but I also think that the scalability of this solution depends on the type of organizations that are using it. For instance, public enterprises like government organizations can make very good use of this solution. I plan to propose the tool to my organization. It’s still in the loading phase and I have not got any feedback on it.

I have not felt the need to contact the customer service and support team since most of my doubts were resolved through the tutorials and tech instructions available on the website, which are very helpful.

I have previously used Power BI. I came across Power Automate while looking for other Power platforms. I saw the different features that Power Automate offers and so I chose it.

It was easy to set up. Once you have access to the portal, navigate to the automatic document processing feature where you can see many examples. There are a total of just two or three steps that you need to follow for completing the entire setup process.

The setup took a couple of months. It requires much concentration like when you are training your model to analyze the documents. For example, when you are setting up the automatic process document, the tool will ask you to try with five documents. Also, we will have to look into the different fields from which we are going to extract the information from the documents.

Once the document upload is done and the training is finished, you will need to locate the locations where other documents are located. It’s recommended to use either the OneDrive or Sharepoint locations. Power Automate will locate the schema of the document, connect with it and the document upload will be done. When the upload is done, the AI Builder will apply the OCR. After the completion of the OCR, the information will be extracted and put on other documents like Excel. 

I am not sure about the setup cost, pricing or licensing since I use the trial version.

I would rate this tool a nine out of ten. 

I use both the on-premise version and web versions because they both have different tools. I use them both for different use cases and different scenarios.

I use Microsoft Power Automate to make reports and web scraping. I automate the reports with the desktop version because it works well. I use Microsoft Windows, to do some commands in the CMD, also known as the line assistant. When it comes to the web version, I mostly do reminders, scraping, extracting data from emails, and creating ticket systems. I take that data and put it in a list or create a table in Excel to extract information and automate that part. 

Microsoft Power Automate has helped our organization by making processes faster. I do some consulting on the side about Microsoft Power Automate. We realize we don't need as many people to work on something because you can automate it or at least semi-automate the tasks.

The most valuable feature of Microsoft Power Automate in the desktop version is web scraping because you can do a lot with it. I work in retail and you can study prices changes, which can give you a lot of information. The solution is no code which is a large advantage.

In the web version, the most valuable features are creating tickets, taking email information, and creating a ticket with it, similar to an IT ticket.

Microsoft Power Automate is a tool that is easy to learn. There is some basic logic that you will have to understand but overall it is not complicated.

I think the language Microsoft Power Automate uses when you do expressions could be better. What they use is not a popular programming language. It would be better for Microsoft to find a more popular programming language, such as Python. It would take away the whole no-code aspect of the solution but you don't need to write that many lines of code to improve something in a process. Instead of no-code, they could be a low-code environment.

I have been using Microsoft Power Automate for approximately seven months.

The stability of Microsoft Power Automate is good, I have not had a problem with the performance.

Microsoft Power Automate is scalable.

We have approximately 10 people using this solution in my organization. The solution is moderately being used. The more you use it, the more ideas come to you of what you can automate or what can you create. In the future, it's going to be used more.

I have not contacted the support from Microsoft.

The implementation of Microsoft Power Automate was straightforward. It took only hours to do the full implementation.

I did the implementation of Microsoft Power Automate in my company. Additionally, I do the maintenance and patching of the solution when needed.

The cost to use Microsoft Power Automate is approximately $15 per user per month, for the basic plan. However, the solution comes free with the Microsoft 365 Suite.

You have to pay extra for the scheduling of the automation tasks.

Microsoft Power Automate is a newer solution to the market. UiPath is a lot more popular and has more features than Microsoft Power Automate. There's a lot of potential in that Microsoft Power Automate because it connects well with other Microsoft programs inside the Suite which makes it even more powerful. UiPath connects with other applications, but the fact that if you use Microsoft in your organization, it's more seamless. It works better. 

I learned Microsoft Power Automate faster because I know how to use Microsoft Excel, and that teaches you how to think more logically when it comes to computers. If you have an Excel or programming background, it's going to be easier because the logic creates the flows. If you won't want your learning curve to be that steep, I would recommend learning Microsoft Excel and then going Microsoft Power Automate. You will have more ideas of what you can do with the tool.

I rate Microsoft Power Automate a nine out of ten because you have to pay to receive the schedule functionality of the automation, which is important.

We use Microsoft Power Automate when we need to automate manual processes in our automation, or when we need to send a document for approval, or when we need to integrate some beams channels and messages.

It's quite simple to use. You can automate almost everything in your organization by simply dragging and dropping and selecting a few options, whether it's an Excel spreadsheet or other on-premise data.

Power Automate is integrating artificial intelligence into the product, allowing us to automate future aspects, such as in pharma companies, medical agencies, and even banks, which are now using these products to automate their manual processes. And because robotic process automation is already built into Power Automate, these features make this product fantastic and accessible to everyone.

These products are intended low-code, no-code solutions. As a result, even a strategic developer can create and automate your day-to-day tasks at their workplace, whether it's management work or a developer is dealing with day-to-day issues with APIs.

In terms of IT, everything can be automated, but other things can also be automated. We can automate the reporting process, as we can with the help of an AI builder. Using Power Automate and Power Apps, we can generate sales reports on the fly.

In terms of issues, I haven't had any until now because automation requires you to complete a task in less time. These products have some limitations, such as the need to build some custom controls in PCF or use the JSON format. There are some limitations, but it's a mature Microsoft product, and we can do almost everything.

Third-party systems can also be added. We can create a beautiful dashboard if another software provides open APIs. Even when discussing complete Power platforms, four components must be mentioned: Power Apps, Power Automate, Power Virtual Agents, and Power BI. When we use all four, we can create a complete solution, whether it's a visualization dashboard, automated chatbots, or the rest, which we can achieve using Power Apps. Power Apps is also divided into three types of apps: canvas apps, model-driven apps, and data-driven apps. Another option is to use open-source, which refers to open projects known as portals. So we can actually do the same thing. When someone is creating a website, we can do the same thing here in the portal. So the things we can do with Power Apps are the same as the things we can do with the Power platform.

I have been working with Microsoft Power Automate for almost two years.

There are some limitations with the calls and other things, but it is a stable product.

Typically, we raise technical support through the Azure portal. If we have a basic plan in place, we can submit a request to Microsoft. 

Microsoft also provides Twitter support. If you have any questions or encounter any technical difficulties while deploying your Power App or configuring your Power Apps or Power Automate environment, you can raise a ticket on the portal and Microsoft will respond directly to you.

I also work with Power Apps.

The initial setup is a very simple procedure. We can deploy in any organization depending on their needs,  we can look into licenses to see what kind of license will meet their requirements. 

As it is in the cloud, it's very simple to deploy. It's ready-to-use software as a service, and we can use various connectors. In addition, if something is outside the scope of Power Automate, we can create a custom connector. How it is deployed is entirely up to the organization. If for example, they have three environments: development, testing, and production, we can easily switch, and we can use Azure DevOps to create CI/CD pipelines, and we can deploy that solution in any environment in the organization.

It is not a costly solution. You can have two types of licenses, one is user-based, and the other is app-based in the Power Platform. 

I work as a senior consultant for Microsoft technology as a developer, mains power developer, but I would love to explore other options.

It's a genuine Microsoft product, which is the main reason I would recommend it to someone.

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

The primary use case of this solution is for process automation.

With regards to the process on the server-side, you are giving the client the opportunity to run from a very small deployment and to take it from one office location to another, and globally.

The most valuable features of this solution are the cost and ease of use, it's very simple.

They have many, easy-to-use features.

When this solution is sold to the clients there is no automated process in place as many other RPA products have. I have to fully understand the product so that I can go over the processes with the client and all staff they may have. 

It would be good to record all of the processes and automate them.

The Kryon product has that option, where when you are doing something automatically it can record it on an AI interface. If they could have that feature included, it would benefit the client.

They need to come up with a little more on AI and precision discovery path to be able to record the processes.

I have been working with this solution for nine months.

This solution is scalable. It allows you to expand not only from one geography, but across as well.

I have not contacted technical support. I am not a part of the technical support, but an advisor. I have been asked to go in for implementation analyzing.

The deployment depends on the requirements of the client. For most of our clients, I recommend it in two processes.

A smaller process with approximately 50 users using it would take one and a half months to develop, depending on availability and time.

There is flexibility in pricing.

I studied five to eight different tools and narrowed it down to the two or three tools that I felt would suit our client's needs.

Some of the other products that were included in my narrowed down studies were Kofax, Automation Anywhere, and UiPath.

There is a very different approach when it comes to Kofax, and I wouldn't recommend UiPath because there is a lot of coding in terms of implementation. UiPath was one of the first ones to have the market and has now lost market share because there are too many available that are smaller, such as Kryon and Kofax.

One other solution that I am studying is NICE. I am trying to get a better understanding of it as an option for my clients.

I am a consultant who advises his clients about the solutions that are best for them. I make recommendations based on their requirements.

Clients have two options, one is the desktop solution and the other is an enterprise version.

For smaller clients what I recommend is to start with the desktop version. I ask them to try it out and if they think that it works in their organization and it's helping, they will get better ROI after proving it to them in the trial POC that I conduct. I have them try it out for six months to a year and then suggest they move to the enterprise version.

My philosophy is value addition. I have seen that with most of the products that we have purchased, we may use only 40% to 50% of the features. I want to change that and cause a disruption in the consulting industry. What I want to do is recommend products to my clients where I see value addition and minimum utilization of features and functionality of the product to 80%.

It's a very different approach and very difficult for clients to understand at first. I am using the years of experience that I have and doing what is in the best interest of the client.

My advice would be not to go directly to process robot. Instead, try the desktop version with smaller processes, small implementation, and get comfortable with it first. 

Start off small then go big. Going big is a huge investment if you are not sure.

Do it one step at a time. Get a few processes, try it out, develop the methodology of implementation, and make it a small mini project or a work in progress then decide. If you are in a hurry and you take a big bang approach without doing it systematically, however good the product is, it could be disastrous.

At the end of the day, this is going to cost you, not only in terms of dollars but in terms of time invested. You will be running with your production environment and existing systems, and there is going to be a lot of effort required to do this, so you have to be convinced that this works for you. Do a POC from three different vendors.

In terms of cost, ease of use, and comfort, I would rate this solution an eight out of ten.

We use this solution to automate small parts of procedures in our workflows. Particularly, linking when emails are received, as well as picking out documents and loading them into SharePoint folders. From there, it feeds things like Power BI dashboards.

In general, they are specific things that we automate in order to reduce manual tasks. We have not applied it to any sort of more sophisticate process, like an approval process, or a supplier engagement process.

Implementing Microsoft Power Automate has made our development team more efficient. They are the ones who tend to have used it and applied it to help automate micro-tasks. It has made their life easier. We have not deployed it beyond our development teams.

The most valuable feature is that it is pretty low-code, so you don't need much coding expertise to use it.

I like that Power Automate is bundled with Office 365 and that it integrates with it pretty well.

The user access level and user account part of this product needs to be developed.  For example, if I'm a line manager and I have multiple approvals that are automated then I can't log into a dashboard and see all of my requests. I would like to have a user account so that the staff can see all of their requests, including the status and other details for each one, on the dashboard.

This solution does not work well with external people who are outside of the organization, like suppliers. It needs support for external email addresses. It would be difficult to do a supplier onboarding with Power Automate, whereas you could do it with Nintex, and this is a big drawback.

I would like to be able to set security and permissions on who can see request-specific details.

I have been using Microsoft Power Automate for less than six months.

In terms of stability, I think that it is going to be fine. We use Power Automate on a daily basis.

I think scalability is kind of limited by its features. If you're doing lots of little bits and pieces then it's fine. However, if you want to scale it to engage external suppliers or vendors then you can't really do that.

The security aspects and lack of user accounts in the interface are challenges for scalability. For what it can do is fine, but if you want to scale out across a business then I think it will struggle to have that breadth of features that enable you to scale it properly.

We have fewer than ten people who use Power Automate in the company, and they are all SAP HANA developers.

I have not been in touch with technical support.

We use Nintex, which does the same thing, but better. We have not switches solutions. We are dabbling with Power Automate to see if it can do a better job, or alternatively, be a cheaper solution for the really simple stuff.

The initial setup was very simple. The deployment probably took about half an hour. It isn't deployed as much as you pick a process and automate it.

We did not have a deployment team for this particular tool. Rather, we have business users who just picked it up themselves. They were SAP HANA developers to start with, so they were predisposed to knowing about this technology and having some kind of technology skills.

The number of people required for maintenance depends on how widely you've deployed it. In our case, it is self-maintained because people have automated their own workflows and they just tweak them as they need to. If you have a widespread deployment then it would depend on how many processes were changing that needed to be updated. It really depends on the situation. In general, it is not difficult to maintain, but it does require maintenance.

This solution is bundled with our Office 365, so there is no additional licensing fee.

We did not evaluate other options before using Power Automate.

We suspect that Microsoft is going to invest pretty heavily in this area. It might be strategic to start using Power Automate now because I suspect it will develop a lot of features over the next few years.

The suitability of this solution depends on how complex the processes are. My advice to anybody who is considering Power Automate is to make sure that it has the capabilities to support that, particularly versus a more established player like Nintex or AgilePoint.

I would rate this solution a six out of ten.