Microsoft Power Automate Reviews

The solution is easy to understand and to develop connectors. You can always extend your own connectors. The ability to go outside and develop your own APIs is a real benefit. Microsoft is heavily investing and developing new features. It is well integrated into the CRM, SharePoint, and other Microsoft platforms.

I had some experience in the past with the solution having some difficulties with large loads, it is already better but it could still be improved.

Another area that needs to be improved is when calculating the quotes of your API calls and flow steps, they are currently not available on the dashboards where you can follow. The API limits will be enforced at some point, at this point you should buy all the add-ons to extend them. This was promised by the end of last year, but it is still not added. Every community is waiting for when this is going to be inforced. It is important because it will contextually be a big step to understand the economics behind your flows and steps, etc., and how to do it more efficiently to save your API calls and steps. The question is, what is the real end cost of how much add-ons you will need to purchase.

In an upcoming release, it would be nice to see bigger integration of cloud and desktop flows.

I have been using the solution for approximately two years.

I have been dealing with Microsoft support for like 10 years or more now. Their support is similar to Office. It is Microsoft of course, I had experience with the premier support. The first level support agents will try and help but sometimes on the first levels, the knowledge shift is a bit lacking. You will sometime have to strain yourself explaining what you exactly want and then you will need to be transferred over to the higher level product team. When it comes to Power Automate, they have a dedicated team, which more or less understands the product.

When making good architectural decisions it is best to understand what kind of scenarios you are solving, especially when it comes to the loads. Try to calculate what is the overall load that will be used, and all flows per day, per minutes, per hour, etc. It is important to do some testing.

Keep in mind the enforcement of API quotas, etc. It is important to start thinking about this and start calculating your flows, to get to the real cost for usage, excluding the initial license. It is critical to know how fast you consume your assigned API calls and when you have to buy extra. This is all in a way stored in the licensing documents, but it is not physically enforced, this is something to keep in mind.

I fully recommend this solution.

I rate Microsoft Power Automate an eight out of ten.

We used it internally to automate certain workflows for our daily business and validate our commercial proposal. We used its latest version.

Its complete integration with Microsoft tools and the inclusion of the CRM are the most valuable features.

It is embedded directly in the Office package, so clients have direct access to it. It has a lot more functionality than other standalone solutions, such as UiPath or Blue Prism.

It is mostly integrated with the Microsoft environment. Unlike UiPath, we cannot really use external tools with Microsoft Power Automate. There should be a possibility to integrate it with external tools or systems.

I had some experience with it two or three years ago, and I used it again about two months ago.

It is absolutely stable.

We have not scaled it.

It is straightforward. The deployment duration depends on the complexity. For our use case, it took a couple of weeks.

It is free for us. It is embedded directly in the Office package.

Our clients prefer using UiPath because it is easier to use and has more functionalities than some of the other solutions. It is also more economical. In the Tunisian and West African markets, UiPath is used more popular, and the customers prefer a solution that is implemented in their market.

At the moment, Microsoft Power Automate is suitable for automating a few processes on each desktop. It is a small solution, but Microsoft has a clear roadmap for this solution, and it would be an interesting one in a few months or years.

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

We're currently exploring the solution. We're doing some planning and testing. We're looking at data transformation and flows.

There's the potential to save a lot of time by reducing the time it takes to do processes. It may even save us costs.

We're looking to monitor more projects in the future, however, right now, we're mostly in the testing phase. 

The tool is very good at implementing automation within processes. It's saved us from doing a lot of manual processes.

The tool is very effective. 

The features on offer are very good.

The product gives us a lot of very useful metrics that we can use.

The entire solution is extremely user-friendly.

There's good documentation online and I find the solution offers pretty good overall communications.

There are some gaps and a few areas of the solution that are still a bit complicated and confusing.

I've had issues with reordering columns. When I tried to do it, it seemed to take a long time, and then, later, it gave me some kind of error. 

We've only been using the solution for the last two months or so. 

The solution is quite stable. We haven't had any issues in that sense. It's reliable. It doesn't crash or freeze. It's not buggy. It's been good.

I'd say the solution can scale. We haven't had any issues in that sense. If a company needs to expand it, it can do so.

In our case, right now the users are minimal. We have maybe five users in total. Some are in IT and a few are in other departments.

We likely need support at this time. Mostly we've been dealing with online assistance and documentation. We're testing the product. To get it up and running, we'll likely need some help and may need to reach out to technical support to get asssitance.

The initial setup isn't as straightforward as we hoped it would be. We had some issues specifically with the initial configuration. It was a bit difficult.

Deployment times vary. For us, it might have taken about four weeks or so.

We handled the implementation ourselves. We did a bit of research and tried to tackle it internally. It was just to get started. When we do a bit more of a complicated setup, we will get some consultants to help us with the process.

I'm not sure of the cost of this solution. Licensing and billing are not aspects of the product I deal with at this time.

While we know there are other tools on the market, currently, we're just playing with this particular tool to see what we can do.

We have looked at UiPath, however, we haven't tried implementing it yet. We just know it is an option.

We have a partnership with Azure. 

I'm using the platform from the desktop version coming with Microsoft 365. I assume it's the latest version of the solution.

Based on our preliminary usage, I do recommend the solution. It is easy to start with and to try out. It's pretty user-friendly and, and there's so much documentation on how to use it. There is other information about use cases as well and some pretty good videos on how to do certain things. The community seems to be pretty strong, which is helpful for when you are starting out.

In general, I would rate the solution at an eight out of ten.

We primarily use the solution for automation purposes. It can offer an alternative desktop option, and therefore it can automate a lot of stuff. It's part of the application. It also can connect us to a number of data sources and that helps us a lot. However, it's difficult to get into specifics due to client privacy.

It's a very stable product. We find it to be quite reliable.

The solution is very easy to use. There's a bit of familiarity with the product due to the interface they have. We use other Microsoft Office products, for example, and it has a similar look and feel that's recognizable if you are familiar with the Microsoft Suite. 

The look and feel and user interface make training new users a fairly easy process.

The solution offers a variety of very good features.

There is an exhaustive amount of templates that users have access to.

You do need to either get a bit of IT support or do a bit of coding in order to implement the solution successfully.

Something lacking is Microsoft Office plugin, however, it's my understanding that their Office plugin is out now or coming soon. We're just trying to understand the use case. 

If they can make it integrated into Microsoft's Office Suite, that would be great. It would be better than lining it up with the Office plugin application. I'm sure it exists in some form, however, maybe not for the mainstream things.

The solution is still maturing very quickly and it's going to take no time for this to be Enterprise RPA.

I've used the solution for the last year and a half or so. 

The solution is stable. There aren't really any bugs or glitches. It doesn't crash or freeze. It's good.

The solution is very scalable. As a cloud product, it makes it very easy for users to expand if they need to. When a company needs to scale, they can do so, no problem.

We do plan to continue to use this solution, and we'll continue to use other Microsoft solutions as well.

We end up using a lot of community resources. Microsoft has a huge community, and it's really helpful in terms of finding answers and asking questions.

I've used the previous generation of this technology, such as Logic Apps and other products of that nature.

We didn't use any other products really. We had some in-house and also some VBA Macros, PowerShell scripts and others which we had created. However, this was the first proper solution we've invested in.

The initial setup is pretty straight forward. It's not overly complex. You do need a bit of IT support, however, you could put it in and save it and other people can use it and probably tweak it quite easily.

While there is a bit of coding needed, once you have everything set up, there are lots of templates that make the implementation of different processes very easy.

The deployment is quick. There's just a bit of needed configuration with the cloud. We didn't activate all of the features; we only activated what was required. I can't recall the exact amount of time it took to do this.

It is fast to implement, does not depend on the changes to existing systems to implement. It save hours that a team spend on performing the process manually. Mostly importantly it is easy to training business users since users are very much familiar microsoft and windows interface (UI).

The licensing set up depends on your organization. If it's an enterprise, it's based on their user department and how do you want the solution to be distributed.

Many companies already have Microsoft Office licenses, for example, and this is part of that. 

It's not too expensive as a license. At least, that's my understanding. 

In comparison, an RPA tool with Outreach costs $5,000. You can use it, however, it's expensive.

I'm using the latest version of the solution.

We are a consulting organization, and we do help clients.

We've helped large organizations. We don't have just one use case for this product. We have many.

You can't build an application with this solution. This is more for automating within a department or in an area, for example, a finance area, where they have all sources lined up and it takes almost three or four days for an accountant to go through the data to create templates and updating templates, etc. Those kinds of things. This solution makes the processes happen faster.

I'd recommend the solution to other organizations.

I would rate the product at an eight out of ten. There's a bit more maturity that needs to happen, however, all of the elements are there to make for a great product.

I primarily use the solution for automation. I also use it for invoicing.

To automatically register some data has saved me a lot of time. In the past, I would look in an Excel sheet every day at 8:00 am and I would have to download a spreadsheet and match some values with another spreadsheet. That kind of task took me almost three hours. Now in almost three minutes or two minutes, it's done.

I also find that it's helped with invoicing in relation to taxes. I can download the invoice, and match it with my ERP system and they match the values with the invoice and the system. If it matches, it gets saved in a spreadsheet with many invoices. I could have 10, 20, or even 30 invoices a day or 100 invoices a week. With this solution, I don't need a person to review that. The robot handles that task.

One of the most valuable feature that Power Platform has is the integration with Power BI and the AI Builder, in the firts one, you ca create visualizations and show indicators of revenue, execution, progress, ranges, of whats going on in the solutions, in the second one, you can create an intelligent model to show projections in a matter of minutes, it's so ieasy o create a robot in these software

The issue lies more in how you learn the solution. The information is very generalized. It could be extremely useful to have more specific information about how to use various features within the platform. The solution has a lot of moving parts and aspects that need to be understood. Making the training process easier would help people onboard faster.

The desktop interface is a little rough to manage. You can't view the bottoms or the menu or the characteristics of what you need to use. It's very unclear in the desktop application. That said, the cloud application it's more useful. It's much neater and more organized.

Their AI builder has improved, however, it could be interesting to look into how to build a project that can make projections about a task or a process. If that feature could be more user-friendly, that would be ideal. Right now, it's not very clear how to use it. Maybe a person that has more knowledge wouldn't be as confused. I'm not like a developer. I'd need it simplified for me.

I've been using the solution for about a year to a year and a half so far. It hasn't been an extended period of time.

I haven't experienced any issues with the stability of the solution. There aren't bugs or glitches. It doesn't seem to crash or freeze. It's been good so far.

The product can integrate with other solutions, and therefore it can work with high workloads or low workloads. It's very scalable. 

We have anywhere from 100 to 500 users.

The technical support of Microsoft has been good. It's not often that we call into Microsoft directly, however, at least, not so much for this particular solution.

The initial setup is not complex. It's quite straightforward. We found the process to be very easy.

The deployment is very fast. It only takes a minute or two.

It's a subscription. Therefore, you only need to log in and make a project, and if you already know how data deploys it's within minutes that you can start.

The solution is subscription-based.

I have evaluated Automation Anywhere, among other solutions. There are many, however, I'm more comfortable with Microsoft.

We're a Microsoft partner.

I have used Flows and it's very easy to use it, however, not in advanced terms.

I'm not sure which version of the solution we're using. It's my understanding that it is the latest, however, I don't know the exact version number.

I'd warn new users that they have to know about the concept of RPA. It's very difficult to get on board with this kind of solution if you don't know about RPA. You have to make everything step-by-step. You have to know how to make a diagram flow. You need to understand what comes first and what's in the middle, and what's next. In order to successfully dive into using the solution, a user must be familiar with these kinds of concepts and labels.

If you don't know about the process or haven't read about BPM, it could make it very difficult to implement RPA. I suggest new users if they aren't familiar, read a little about RPA in the beginning and then learn about the processes.

It's a good product. I would rate it nine out of ten.

Currently, we are in an active search with a provider for on-premise, and therefore we use it to automate our process of moving our permits to electric housing and preparations.

We use the solution for building processors and it's really easy to use for this task. It gives you another way to move the path. 

With Microsoft, there are a lot of great process management tools. 

The initial setup isn't too difficult.

The availability could be a bit better.

Technical support needs to be able to respond quickly to queries. Right now, they are much too slow.

I'd like it if it were possible to have the solution as an on-premises installation, however, that is not possible. It only is available on the cloud.

I've been working with the solution for the last six or seven months. It's been less than a year at this point. We haven't used it for very long yet.

Power Automate, compared to Softomotive's product, offers the most in terms of versatility. Stability is not an issue. It has been very good for this product. We did not have that kind of problem with our customers or any installation. We don't seem to have to deal with bugs or glitches. It doesn't crash or freeze. We're happy with it.

At the moment, we have 80 professional developers on our team that work with the product. On top of that, we have various companies that use it. We have 50 or so different customers using the cloud.

We use the product regularly. We're on it on a daily basis.

Scalability is very, very easy to accomplish. If a company needs to expand the solution, it can do so easily.

The solution's technical support isn't that great. They could be better. They're slow to respond when there are issues. They really need to be faster in this regard.

We also work with Softomotive WinAutomation as well as ProcessRobot. Using more than one solution allows us to cross-manage better.

The initial implementation wasn't too hard, or, at least, that was my understanding. I didn't directly participate. However, I did not notice the team dealing with any complexity. It's pretty straightforward. Any organization shouldn't have too many problems setting it up.

The maintenance of the license is largely handled by Microsoft. We handle everything else.

We handled the implementation in house. We did not need outside help and we did not hire an integrator or consultant or any person of that nature. We handle the implementation for the customers if we need to.

The licensing itself isn't that great. That said, the solution is very cheap. It's on the lower end in terms of price, if you look at the entire market. It's rather affordable.

We're Microsoft partners.

We're using the latest version of the solution right now.

I would definitely recommend the product to other organizations. Overall, we've been pretty happy with it, even though we haven't used it for too long.

In general, I would rate the solution at an eight out of ten.

We carried out a successful POC on Power Automate Desktop. It was right after they launched and we were the first to demo it. We used it in a project for one of our clients. We used the desktop version but it's stored in Power Automate cloud. The solution is used for banking processes such as credit and debit transactions. We are partners with Microsoft and I'm the CTO.

We jumped onto this solution because it's very reasonably priced. The solution was for a medium size organization and they didn't want to spend a lot on such a product. It's a good solution for small to medium size organizations. 

Looping can be a bit tricky in Power Automate. In addition, the solution doesn't provide an option to view two to three conditions, you can only view one condition. It's not like that in UiPath. Deployment should be improved so that it integrates with WinAutomation. We can't write .NET code and we can't schedule the bot without using WinAutomation. If they could include that it would be helpful for our users. Right now we do the development in WinAutomation and later integrate with Power Automate.

We had good technical support. 

Installation is pretty straightforward. As mentioned, we were the first company so we had a call with Microsoft and worked with them. We're a start up so we had a maximum of six people using the solution. 

We use it to monitor the net flow of all the emails. It is really helpful.

It is stable. 

It should be faster and more user-friendly. 

I have been using Power Automate for around three years. 

It is stable and scalable. We have around 300 users. It doesn't require any dedicated IT to help run the appliance. 

We don't need much of their support. We have opened a ticket and their support was handy. It's very easy for us to communicate with them via email. 

The initial setup was easy. It was very easy for people to pick up. The deployment took a few hours. 

I would recommend it.

I would rate Power Automate an eight out of ten. 

We are a solution provider and this is one of the tools that we implement for our clients.

We have been automating several tasks using this product. They include things like comparing Excel worksheets with the contents of databases, automation in database security, and we have internal logs that can be used to help developers pinpoint errors.

This is a cost-effective RPA solution.

WinAutomation is missing a lot of options that are available in UiPath. One limitation is that for logs, the only option is a CSV file. There is no option, for example, to work with an Excel file.

There is a limitation in setting up loops, where it does not support multiple conditions.

We would like to be able to write code, the way you can inside of UiPath.

We have been using WinAutomation for the past two months.

This solution is stable.

This is a scalable product, although it is best for mid-sized industries.

The technical support is good. We had an issue and they were able to resolve it.

The installation and initial configuration were straightforward, taking not more than 10 minutes.

I deployed the product myself.

WinAutomation is cheaper than competing tools.

Our choice for using WinAutomation depends largely on the client. We will continue to use it, although if our client does not agree then we would have to use another tool.

This is definitely a product that I can recommend. The price is cheaper than other tools and it has a lot of features.

I would rate this solution a six out of ten.

We are a solution provider and one of the services that we perform is to build automations for our clients. Softomotive is a product that we use to automate multiple processes for use by our customers on their data, based on their needs.

The interface is user-friendly.

This product is cost-effective, which is the main reason we are using it.

We are looking to see more features implemented there are already available in UiPath or Automation Anywhere. This is one of the main drawbacks.

We have been using Softomotive for between three and four years.

It is stable, and we don't have any issues with this particular product as of today. We plan to continue using it in the future.

We have more than 600 customers who use this product.

We get very good support from Softomotive.

We have used Softomotive for the past four to five years, although in the interim we tested Blue Prism. The cost of that product is too high.

The installation is straightforward and we haven't seen any complexity. It will take 15 minutes, maximum, to deploy.

This is a product that I can easily deploy on my own. We have less than 15 people on-site who are responsible for deployment and maintenance.

This is a cost-effective product and now that it has been acquired by Microsoft, we don't expect the cost to increase with the next release.

Considering the kind of experience that we have had with Softomotive, we would always recommend this product.

Since this product was acquired by Microsoft, naturally the expectation has gone up. We are not expecting too much of an architectural change, but rather, a few of the small features should be added. The reason is that you like to stay competitive in terms of cost. We have already deployed it to more than 600 customers and if we are going to charge them more, then they'll be inclined to use another product.

I would rate this solution a nine out of ten.