Microsoft Power Automate Reviews

Our primary use case for Microsoft Power Automate is in the direction of citizen developers, mainly small automations built by business people themselves. We also use it for automations in finance departments with Power Apps.

Hyperautomation strategies are built around UiPath and Microsoft Power Platform, improving service delivery. It is easy to learn for business users, facilitating quick setup of automations.

Microsoft Power Automate is a no-code platform which is very easy to learn, allowing businesses to build their own small automations. Templated flows enhance automation capabilities, and document understanding is also highly valuable. The integration with AI in process automation is anticipated.

The licensing model could be improved to make it easier to understand and follow, as it is difficult to determine if the embedded license provides all functionalities or if additional licenses are needed.

I have been working with Microsoft Power Automate since 2020, about four years.

Once you know how to build automations and bypass limitations, they are stable and work correctly.

Microsoft Power Automate is best suited for citizen developers. Managing it at the enterprise level with more complex business processes can be more challenging.

I am satisfied with Microsoft's customer support as we are a partner and receive fast responses.

Positive

The setup requires time for configuration and may require an administrator. It is time-consuming.

Our customers have seen return on investment with Microsoft Power Automate. However, it's important to consider licensing limitations to avoid high costs.

Costs depend on the automation complexity. Licensing can be based on per user or per flow, with the potential for high costs if not carefully managed. The cost for licensing can increase due to licensing fees.

When evaluating, it depends on needs. UiPath is more mature for enterprise-level automation but more expensive, while Microsoft Power Automate is a good start for small automations and for those already using Microsoft products.

I recommend trying Microsoft Power Automate. It is a low-code platform and is easy to learn, allowing quick start to automation.

I'd rate the solution eight out of ten.

Microsoft Power Automate has helped one of my clients to update a SharePoint list automatically. There was no need to open the SharePoint list every time and update it. Instead, a flow that runs and updates it.

The most valuable feature of the solution is that it easily integrates with Azure DevOps.

We need to buy a premium license for Microsoft Power Automate because some features are only available for premium licenses. It would be really helpful if Microsoft offered some premium features in the standard version. Instead of bringing everything to the standard version, it would be really helpful if Microsoft classified one or two important things as standard, which are regularly worked upon.

The solution's licensing model is very complex and not straightforward. The licensing model needs to be reviewed and changed. Sometimes, Microsoft Power Automate's portal becomes a little bit slow.

I have been using Microsoft Power Automate for one year.

I rate the solution a six out of ten for stability.

I rate the solution a six out of ten for scalability.

The solution's technical support responds generically, but we would need some issue-specific responses.

Neutral

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup a five out of ten.

The solution's implementation takes only a few minutes.

On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing two to three out of ten.

We have benefits with Microsoft Power Automate, like automatically updating records when they pop up. I would recommend Microsoft Power Automate to other users because it easily integrates with other Microsoft products, which is one of the big benefits to us. Microsoft Power Automate is easily acquirable.

The solution's licensing model is very complex. Compared to other RPA tools, Microsoft Power Automate is easy to work with. Other RPA tools are bought at a higher price, but Microsoft Power Automate is not very expensive.

Overall, I rate Microsoft Power Automate a six out of ten.

We have a few domain-specific use cases, primarily with BFSI customers and IT specialists, including some IT giants. We work with them to leverage Power Automate. They are primarily using it to automate the internal workflows that they perform on a day-to-day basis. They use Power Automate or an automated solution to simplify and streamline their processes.

Our primary focus is on new workflow development. We mainly handle the development of use cases, integration, and workflow development. While working on development, we also provide support for the use cases where the workflow is developed

Workloads could be optimized.

My team has been working with Microsoft Power Automate for one and a half years. We are using the latest version. 

Stability-wise, you should be fine if you configure Azure Monitor, Azure Log Monitor, and Azure Monitor should be timed. You'll get the right alerts, and at the right time, you can have a stable environment.

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

Scalability should not be a problem as it is supported by Microsoft, and its infrastructure is well-equipped for it. Additionally, Azure, the cloud, and BestFactors Incorporated are all available for scaling the solution anywhere.

My customers are mostly small and medium-sized businesses, with no large customers. The majority are within the range of 200 or fewer. I would rate the scalability a nine out of ten. 

For me, the support is perfect. It depends on the kind of support you have, like what kind of partnership you have. If you have premium partners, the support is really good too. It depends on what support or what kind of deal you have with them.

Positive

It is comparatively easy to install. I would rate it eight out of ten. It will require some knowledge due to the kind of setup it has. Also, considering the security reasons of Microsoft, it predominantly requires the infrastructure set within its domain. It cannot go out of its domain. So understanding all the nuances of it is essential.

Other platforms are not cloud diagnostic; they are on-premise also. But as an organization, Microsoft is not reporting that they would want to have everything on-premise on the cloud. So, understanding all the nuances and recommending that you get the right kind of security approvals done will be important because certain customers are not comfortable with having the PAT agent configured in such a way that it gives the data to the cloud. Microsoft is on. They are not comfortable with it.

The deployment process takes around a week or more. Typically, we have a complete person who serves as the leading architect for the project, along with two engineers to handle end-to-end deployment.

The maintenancedepends on the size of the workloads and how many production spots you have. For small deployments with 10-15 bots, one engineer should suffice. For medium deployments with 50-100 bots, you would need two to three people. And for large deployments with thousands of bots, at least four to five people are necessary. It also depends on whether bots are running during business hours or off-hours, in which case a 24/7 maintenance team may be required.

Power Automate is a better and more cost-effective solution compared to Automation tools. The pricing model is cheap. I would say they have played it very smart. It is cheap, but the connectors go for a task. So, you'll have to pay extra for the connectors.

I would rate the pricing model a two out of ten, where ten is very expensive. Moreover, Microsoft Power Automate has a per-user model. They don't require yearly payments. The licensing is for all updates per-user. So it's decently licensed. But it is a good amount. 

Predominantly, we pass our automated service from RPA technology upfront. We also work with UiPath and ServiceNow Automation Hub.

My advice would be that if you want to automate processes within your organization, this would be a good tool. If your organization's infrastructure is built on Azure or Microsoft, then Power Automate would be the best choice for automation within the organization.

Overall, I would rate the solution a nine out of ten. 

Microsoft Power Automate is deployed in the Azure cloud. Microsoft has a version of Power Automate Desktop to develop desktop flows and that's also saved in the cloud. We use Microsoft Power Automate on the project site. We have done a few projects on the site and the solution is used for video processing automation.

The most advantageous aspect of the solution is its cloud capabilities. With an E3 license, we can access Microsoft Power Automate at a reduced cost. If we are only using the application, we need the Microsoft Power Automate attended mode add-on. Other than that, the solution is free, since all customers are using a Microsoft-based license for their communication and an E3 license for the add-ons.

When it comes to cloud computing, there are many limitations when dealing with large amounts of data. For example, if we are managing more than 10,000 or 1 million records, the API layer has some redundancies. These limitations take a lot of time to process. For example, if we have 10,000 records, our cloud workflow will take more than three hours to complete. Clearly, there is room for improvement in the workflow process.

I have been using the solution for two years.

The solution is highly stable due to its use of Azure cloud services, boasting a 99.9 percent stability rate.

The solution is scalable; we can introduce multiple bots and a multiple-bot architecture is available. Therefore, scalability is possible with Microsoft Power Automate. We need to develop our own architecture to handle the multiple bots, share records, and share the workload with the bots.

We created a few tickets with Microsoft technical support regarding a time issue. We then created a workflow that initiated cloud workflow and handed it over to the Microsoft Power Automate desktop, which took some time. The flow worked, but after an hour and a half, it automatically disconnected due to either a lack of available sessions or an error. We created a ticket and Microsoft resolved it quickly, taking only one day. The issue was caused by the group policy, which had enabled a session timeout of between 30 minutes and an hour, resulting in the issue.

Positive

The initial setup is quite straightforward. We can create a production environment and a development box. We can then move our solution to the UID environment and then to production. The deployment process takes two to three days.

The solution is $150 per month for the unattended add-on, and the normal Power Automate comes with an E3 license.

I give the solution a nine out of ten.

The solution is more cost-effective. We were initially going to convert the customer's automation because they already use the Microsoft Platform.

Microsoft Power Automate has plenty of examples and templates. It is easy for new users to start development. I recommend the solution.

Our company uses the solution to process insurance claims and related activity. We have around 80 developers and three administrators. Depending on clients' needs, we might scale in the future. 

The solution is really easy to use compared to other tools. 

The western license is fantastic.

The solution integrates more easily and with more tools than Automation Anywhere. 

There are frequent version updates and that impacts different algorithms so we have to adjust our code. 

The solution should include connectors and DevOps capabilities with its standard package. 

I have been using the solution for three years. 

The stability is good so is rated a nine out of ten. 

The scalability is good with no doubts. 

We have been developing on Microsoft's data products from beta release onwards. They bought and merged an automation company into their product so we know the different methods. We diagnose things and that feedback ends up inserted within very big containers. 

Technical support is good but their response times are slow. 

The setup is straightforward. 

We implement the solution in-house. 

Our typical use cases can be handled by two or three developers and take about six to eight weeks to implement. 

First, we create the DDS. Then, we create software flows, standards, and login processes. We add efforts, exceptions, vendors, record reviews, and testing. Finally, we perform UAT and production. 

The pricing is reasonable and the western license is fantastic. 

They have a premium service that includes connectors and the SQL server sanitizer team. If they change this service to be standard, then pricing will be even better. 

We also use Automation Anywhere but there is some maintenance involved. 

The solution integrates with other tools better than Automation Anywhere. 

The solution is a good product. It integrates well with apps, virtual agents, and other tools. It has all the capabilities of Microsoft and Windows. 

I rate the solution an eight out of ten. 

We were a partner with Softomotive before they were acquired by Microsoft, and now, we are a partner with Microsoft. We have quite a bit of expertise in WinAutomation. Microsoft has depreciated it, and it's now a part of Power Automate, but we still help out clients with it even though it's deprecated.

Its use cases were the same as any other RPA product. It was basically used for automating any repetitive process, which could be anything from filings to transferring data between software to triggering different processes via email or databases and so on and so forth.

Triggering and scheduling were pretty good. There was no real commitment with WinAutomation because the licensing was very fair and you could trigger bots very easily. 

They've already improved it, but I guess a testing suite would be nice to be able to test your automations in real time.

It's pretty stable.

They had a second piece of software called ProcessRobot, which was kind of WinAutomation's big brother. That was a scalable solution, but all that is depreciated now.

At the time, the tech support was excellent.

Deployment was very easy. You just installed the software, and then you installed a couple of plug-ins and browsers, and you were ready to go.

The number of people required for maintenance depends on the size of the deployment. You can have one bot, you can have ten bots, or you can have a thousand bots. 

It provided an extremely high return on investment. When you automate processes, you're oftentimes being able to scale very easily, and you have a very high ROI.

It had by far the fairest licensing on the market. For the money, you got a very good value.

If you're planning on implementing the product, start off with simple automations and take your time to learn, understand best practices, and understand error handling. A lot of issues come out of improper error handling and no best practices. Start simple and don't be afraid to ask questions.

There are a lot of different products out there that are competitors to this. Microsoft now has Power Automate, which is basically WinAutomation with a lot more web connectivity and a much larger ecosystem. It's extremely powerful, and you have lots of UIs, front ends, chatbots, AI, and so on and so forth. I highly recommend it, and then you have UiPath, which is geared toward enterprises. The licensing structure is much more expensive, and they have some powerful tools over there. You have Automation Anywhere, which seemed to have been a direct competitor. It was more expensive, but it was also very powerful. You have Blue Prism. You have Robocorp. There are a lot of them.

Back in the day, I would rate it a 9 out of 10. For the money, it was an excellent deal. It was very low cost compared to the competitors, and it performed 75% of what the competitors did. If your use case could fit within its capabilities, it was an excellent deal.

I have different use cases for Microsoft Power Automate. I was automating one of the refund processes in my previous company. This involved getting data from an Excel spreadsheet and iterating all its entries. For each entry, the solution checked a particular website to verify values and released payments to the client if everything was okay. This eliminated the need for me to perform the same task repeatedly.

Microsoft Power Automate allowed us to save about eight hours daily, which gave people time to focus on more complicated tasks. Instead of manually triggering payments through the website, everything was done through robotic process automation (RPA), saving us a lot of time.

In our use case, we used a lot of website scraping, so I think that's probably the feature I like the most. The solution provided the possibility to check the website's content and navigate through it, which was very useful for me at the time.

There is room for improvement in web scraping. Specifically, automatic selectors that allow me to select parts of a website could be more adaptable. Currently, if you select one element, it only takes some parameters that might change in the future. This can cause issues because the bot may stop running without fine manual tuning, especially if the website also has active tags loaded.

In the next release, it could be useful to integrate data tables directly into the spreadsheet without having to go through a loop. Integrated databases could be a good addition.

I have been using Microsoft Power Automate for one year.  

Scalability was not really a use case here for us because we only ran it on a local PC.

In case of problems, I would go to the forum directly to check for any other solutions.

I switched to Microsoft Power Automate because it's free. In many cases, it's installed on the PC, I think, on the Windows server, and you can have the screen installed on your PC or download it for free while authorized. UiPath usually costs quite a lot. I think it's the most expensive one.

For the initial setup, I would rate it somewhere in the middle, so around seven out of ten. It's not too difficult, and with some tutorials and testing, it can be achieved quite easily.

The whole deployment process took around three weeks, end-to-end. It starts with gathering the requirements. I asked the ops team to give me their exact steps and techniques. Then, based on that, we build the documentation for the step-by-step process. We mirror this process and try to replicate those steps from the RPA. Then we move on to the UET cases and go through them. If everything goes well, we will provide a sign-off and release it into production.

I would rate it as a low price. While a paid version with a subscription allows you to run it on the cloud, I think the free version is quite good, even compared to the paid version.

I was using UiPath and Automate Anywhere (AA). 

It's important to experiment with the tool and not give up. Always remember that any problem you have has likely been solved before and can be found on the internet.

Overall, I would give it an eight. It's not difficult to develop with this tool and doesn't require a lot of knowledge to get started. However, the selectors on web scraping aren't perfect, so that's where it loses some points. But this may change in the future, and I might change my rating accordingly.

We are using Microsoft Power Automate for RPA.

We assessed the functionality of Microsoft Power Automate in streamlining repetitive processes that required human effort. Specifically, we discovered that the process of completing online loan applications for our customers was a prime candidate for automation. With Microsoft Power Automate, we were able to automate this process, enabling a single individual to log in to up to twenty loan applications. However, if we needed to scale up to two hundred applications per day, we would have required ten individuals to manage this process manually. With this solution, we were able to achieve this with only two people, as the software facilitated logging into the application master and extracting data directly into an Excel file, which could then be easily uploaded and processed within minutes. It has improved our organization's efficiency.

The most valuable feature of Microsoft Power Automate is the many functionalities, and ease of use. We had summer interns from college in their second year of engineering and they were able to start the building process quickly within a day.

More OCR and AI capabilities are needed to improve the solution. Other solutions have better features, such as Blue Prism and UiPath.

In a future release, they should add the running of multiple clients on a single machine. This is a critical feature. If not it requires multiple machines to run operations.

I have been using Microsoft Power Automate for approximately a year and a half.

I rate the stability of Microsoft Power Automate an eight out of ten.

We are not a large organization. We have approximately 10 clients using the solution.

The people who use the solution are back-end processing engineers.

We are considering increasing usage in terms of processes rather than personnel. Specifically, we are exploring automation for certain quick and simple processes, such as transferring data between Excel spreadsheets and performing calculations.

The solution has been scalable in our usage.

I rate the scalability of Microsoft Power Automate an eight out of ten.

We have standard support and it has been decent.

I rate the support of Microsoft Power Automate an eight out of ten.

Positive

It took us about fifteen days of training for our people to have the solution up and running. It was simple.

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

Initially, we relied on a third party for the proof of concept and comparisons. However, we eventually transitioned to completing the implementation in-house.

Our process or not complex and we used three people for the implementation.

Initially, we had a Microsoft account for Office 365. Later, we discovered that our license included access to Power Automate at no additional cost. There was a small fee for additional features, but it was negligible compared to the benefits. There are not any additional fees required to use the solution.

If we had purchased a UIPath or Blue Prism, it would have cost us a minimum of $10,000.

I rate the price of Microsoft Power Automate an eight out of ten.

We evaluated Blue Prism but we choose Microsoft Power Automate because it best suited our needs.

It is important to follow the typical software implementation methodology for Microsoft Power Automate. If .NET resources are available, you don't need to look outside. They can learn the software quickly and deliver it.

I rate Microsoft Power Automate an eight out of ten.

We have been very happy with the solution it is not costing us a lot and we can do the implementation in-house.