Microsoft Power Automate Reviews

We have various use cases because it is used at an enterprise scale. It is mainly used for document workflow management. It is used for validating and publishing documents. It is also used for validating the SharePoint page publishing, financial approvals, and investments approvals. It is a SaaS solution, so we have its latest version.

Its integration with the Office 365 ecosystem is most valuable. We use a lot of ready-to-use templates.

Its licensing model should be improved. The pricing should be more visible and transparent. When you consume services, there are too many criteria to figure out how much it is going to cost you to use the product to its full extent.

It should also support visual process editing, which is a standard feature for BPMN 2.0 compliance. They should improve the visual designer.

I have been using this solution for three years.

It is globally stable.

We haven't scaled it up. We have between 1,000 to 2,000 users. On paper, it is easy to scale, but it is under the condition of license purchase. It scales within the limits of what has been imposed by the licensing model.

I have been more in touch with their pre-sales people than technical support. We are a large enterprise, so we have direct access to their premium support team with SLAs. Their support is very responsive and efficient.

It is simple. It is a ready-to-use product, and there is no setup. It also doesn't require maintenance from our side.

It costs us nothing because we use it on the built-in cost that is a part of our existing license for 365. To use it more extensively, there are different pricing models.

Its licensing is complex. It is complex to evaluate the cost in advance. As a result, people don't use it because they don't know what overall cost they are going to incur. There are too many criteria to figure out how much it is going to cost you to use the product to its full extent. Its licensing model should be improved, and the pricing should be more visible and transparent. 

I would recommend this solution to others. I would rate Microsoft Power Automate a seven 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. 

The reason why we are using this product is that we like to use it where we have automation projects specifically for Microsoft products. We can automate to improve productivity and for those applications and simple tasks, it is easy to use.  

For example, suppose I get my email with Outlook. There are certain times I will get specific Excel files from a pre-determined output which I have to always place into a particular SharePoint folder. From there, some other automation gets triggered and the file is processed in a certain way. Those are the sort of things we can automate with Power Automate. It is very good at working with those simple Microsoft-product-related processes.  

We use it wherever we have workflow processes in which Microsoft products are interacting. Before using this solution, people would get those emails and the recipient had to download the file and then manually put it into SharePoint. Now, as soon as it comes into the inbox, Power Automate gets triggered and it automatically copies the file to the correct SharePoint. There is no reason that a repetitive task of this sort needs to be done manually.  

It offers a different option than using UiPath which is much more complicated and more expensive for simple tasks that Power Automate can do more easily.  

It is very hard to say what the most valuable features are in Power Automate because we are still exploring the product and utility. I like the simplicity of how we can create those automated activities quickly. For now, the most valuable feature is that it is very easy to use.  

There is definitely a lot of enhancement that Microsoft can incorporate into Power Automate. For example, we have quite a lot of .NET applications that we created. These are custom applications that we created using something like VB.NET or C#.NET. These are obviously applications that are not published by Microsoft. I would like it if Microsoft could enhance the capabilities of Power Automate to allow users to connect to other tools and applications in some way. That will help us create better processes without making them more complicated or having to use another automation tool. Right now, we have to use UiPath to help us make processes such as the one described. I have not seen any way that Power Automate can do that type of integration. So if we could get better integration with non-Microsoft solutions as a feature for Power Automate, that will be very useful.  

We have been using Microsoft Power Automate (formerly Flows) for the last three months.  

We have not created anything complex, so we have not faced any issues in the form of glitches or any bugs to this point. When we start doing more sophisticated workflows, that may end up being a different story.  

I have not really had much of an opportunity to test the scalability of the solution yet. If we find a particular workflow that requires a change or something, it is easy to drop that version and recreate something new from scratch. It does not take much time. Scaling the number of processes up or down at this point does not seem to be an issue.  

The number of users in our company right now remains pretty small. I think there are only around 15 to 20 of us are actually exploring the capabilities. Eventually, that group should be much larger.  

We have not had any reason to work with the technical support team at this point. One of my colleagues did drop them a note asking if there is a way we can use Power Automate to connect to any of the custom tools that we created. I do not believe that we have got an answer to that question yet, so it is taking some time.  

The initial setup was quite good and went smoothly. It was not complex at all. It is good that it was relatively easy because we understood that it would mostly be used for easy processes to do some small tasks. We went that way and are using the tool only for working with simple automation processes. We did spend some time trying to automate more complex processes, but as the processes became more complex the tool became more complex to use. It is much easier to use it to do non-complex things. The setup for the processes themselves is fairly easy to do.   

This solution can save money when used for simple tasks specifically using only Microsoft products.  

We are currently working on evaluations of various products. The thing is, we have just started to embark on our journey into RPA (Robotic Process Automation) and we have brought in UiPath to act in that capacity. We are very much, at a nascent stage of the discovery of what we can do and what the product is capable of. We are identifying processes that can be automated and we are planning to work mostly with UiPath on those solutions. We have already engaged in a contract with UiPath for use of their product at this point in time.  

Most of our work is going towards UiPath currently but we also have this Microsoft Enterprise licensing. There seems to be no reason we should not use that as well if there are ways it can provide an advantage. We are also exploring if the enhancements we would need to tie in other applications and processes to Power Automate are something that we could do internally. At this time we are working with a combination of solutions that falls somewhere between our existing processes and new capabilities with automation tools.  

I have a few comments and advice for people considering the addition of RPA in their workflows. I would suggest that they do as much streamlining of their processes as possible. If they can get smaller things up and running by creating the process with a simple tool it may help their efficiency as well as their bottom line. When you go for big tools like UiPath and all the other robust RPA solutions, the cost of creating those smaller processes will be higher than they need to be. If people have a Microsoft Enterprise license, they could actually use the Power Automate tool to make their processes much more lean and efficient. Doing the same thing by employing any of the RPA-related solutions and tools might be a lot more effort.  

On a scale from one to ten where one is the worst and ten is the best, I would rate Power Automate, overall as a product as a six-of-ten at this point. It has got a lot of room for improvement.  

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

The solution's most valuable feature is cloud flows.

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

We have been using the solution for a year.

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

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

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

Neutral

We use our in-house software as well.

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

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

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

I rate Microsoft Power Automate seven out of ten.

We are using Microsoft Power Automate for automating approval.

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

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

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

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

Microsoft Power Automate is reliable.

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

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

The solution is scalable.

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

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

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

We did the implementation of the solution in-house.

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

I would recommend this solution to others.

I rate Microsoft Power Automate a nine out of ten.

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.

It is currently being used by our customer service department. They're using it for tracking overtime, and they're also using it for reporting and automating their various service quality reports. So, automation of service quality reports and overtime management are basically two major use cases.

The ease of use and the integration with some of the existing products that we have would be its main takeouts.

From an improvement perspective, Microsoft just needs to make sure that they have a real enterprise RPA tool. PowerApps and Power Automate are still not at the level of UiPath and Automation Anywhere. It could be because Automation Anywhere and UiPath have been in the market for quite some time. It's just about Microsoft increasing their focus in terms of product reviews and development and making them competitive products that one can consider at an enterprise level. Right now, their use cases are limited as compared to what one would consider doing with UiPath and Automation Anywhere.

It is a stable solution.

It is scalable, but it is limited in terms of the processes that you can automate. If you have complex processes that you want to automate, it doesn't have that capability yet. So, it is scalable but to a certain extent.

Our organization is working with it actively. Its number of users could be between 100 and 200.

Technical support is given by Microsoft through the support model that they offer for customers. If you have an issue, you can log the issue in with Microsoft, and they would always attend to it. I would rate them a three out of five.

It was straightforward. There was nothing complex.

You don't need much staff for deployment and maintenance of it. You need a very limited number of people.

We used a partner.

Its license is a part of our enterprise agreement. It is a three-year contract, but we pay yearly. So, it is a yearly license. There are no additional costs.

I would rate it a six out of 10.

I am the head of RPA solutions at my company where we implement this product for our customers. These are insurance companies that have legacy systems and prefer to keep their RPA off the cloud.

The product allows us to alleviate customer pain points by automating their data entry processes and enhancing archiving capabilities. We are able to minimize the delays of various claims and policies while improving data entry accuracy. We also offer them the ability to archive various communications to a variety of archiving portals such as SharePoint.

The program requires no code, making it very easy to implement various functions.

During their merger, some key functions were eliminated which no longer allows it to run independently from the cloud as a standalone for other companies. For example, options to schedule and trigger have been removed. It would be nice to have these capabilities back.

The flow and the connectivity between databases and so on is a bit complex as well.

We were using Softomotive for approximately three years until they were purchased by Microsoft where it was then merged under the umbrella of Microsoft Power Automate and we have been using this since - it has been about a year and a half since the merger. 

Overall, I would say that it is quite stable, but with the merger, we are not ready to move to the latest version until we can completely replace all of the old functions. I would say the product is 90% stable.

We require five team members to maintain the product and assist our clients.

The product is quite scalable. When considering extending more processes, features, machines, etc. it is a much cheaper and easier option.

We are still communicating with the Softomotive support team that we have been using prior to the merge and they are perfect. Microsoft is supportive as well.

Positive

The initial setup was straightforward and easy, especially in comparison with other RPA's such as UiPath or Automation Anywhere.

We are able to see high returns thanks to having few machines with minimal implementation costs. We are able to present our clients with their ROI upon completion of each project and they see ROI's as soon as their first month.

This is the cheapest option among competitors. 

You can choose to have the RPA with attendance at $40/month with add-on's totaling about $190. There are standalone options that require someone to run the process and there are fully automated options that are integrated within the cloud.

We were trying some open source solution, but it was not really reliable so we did not continue with it.

The actions and functions are much easier than other competitors.

I would rate this product an eight out of ten.