Microsoft Power Automate Reviews

The solution is bundled together with many Microsoft products.

The solution is stable.

The solution offers a lot of documentation and tutorials for users to learn about various aspects and features.

The pricing is very reasonable.

The solution is not actually satisfying the complex programs that we want to execute. We're looking for alternatives right now.

Currently, Power Automate has, if I'm not wrong, about 500 actions per workflow, and my team is not satisfied as they want something very complex that automates a process end to end. That would need a lot of iteration and loops being implemented. The 500 steps in a workflow don't seem to serve our end goals.

The solution doesn't integrate very well with non-Microsoft products.

We've been using the solution for about nine months or so.

With the processes that we've been able to implement, it has been stable. There are no bugs or glitches and it does not crash or freeze on us. 

I am not sure about the scalability aspect of it as the kind of processes we've been executing has been very simple and straightforward, to be honest. We haven't tested the solution's limits.

So far, we have not had an experience where we had to get in touch with the Microsoft team to resolve any issue. There is documentation that is available online and tutorials provided by Microsoft, and the community has been pretty helpful for our IT team to design these solutions. We've been able to use those resources in order to mostly figure everything out ourselves. Therefore, I can't speak to their level of helpfulness.

We are using Power Automate, as it has come with the Microsoft Office 365 bundle. We aren't satisfied with it and therefore are looking for alternatives. This is our first experience with an RPA, and I don't like the app.

I didn't directly deal with the initial implementation. I'm on the management side. I get in touch with the IT team who work with Power Automate directly.

The pricing is absolutely reasonable as you're getting a lot more than just this solution. You're not just paying for Power Automate when you're paying for it. You're paying for the bundle itself. It was basically an add-on for whatever other services we're buying. Therefore, it was more or less free for us.

We are currently looking to explore other RPA options.

We have, for example, lightly explored UiPath as an option. Currently, there are a lot of processes that are being run on SAP and other infrastructure like Salesforce. Power Automate doesn't seem to be integrating well with them. We've been talking to other organizations or other partners that are using UiPath, and they've said they were able to implement somewhat similar tasks and were able to integrate easier. If the UiPath integrations are beyond the scope of Microsoft, it would be a better option.

We are a customer and an end-user of the product.

I have very little experience working with Power Automate. I'm the management person who gets in touch with the IT team who works with Power Automate directly.

I'm not sure which version of the solution we're using.

If your organization is running on Microsoft, and purely on Microsoft architecture, Power Automate is the way to go. If you're a very big company that wants to have complex tasks executed, however, it's not the best option. We're at a stage where we're trying to reevaluate where we want to go in ahead with the RPA journey. Power Automate doesn't look like the right option, at least for us right now.

I'd rate the solution at a seven out of ten.

I was using this product to create a basic workflow and trying to integrate it with Outlook.

We use it along with Microsoft Power Apps to help identify and automate tasks. We have many tasks in Outlook, SharePoint, Calendar, and Teams, and we use Apps to manage the tasks.

We are also using a feature in Microsoft Power Apps, which is the productivity backup

It has some basic components that are able to communicate with different platforms within Microsoft.

The interface is simple and it's easy to use.

It servers our purposes in bringing together all types of applications, being able to automate them with the right intelligent output from the data that we plugin.

While using this solution, we found it to be basic.

The integration with other applications can be made simpler. That said, it has almost everything in it.

I have only been using Microsoft Power Automate for a couple of weeks.

We were using an older version. A version from when it was first released, to help with the learning process.

This a stable solution

Microsoft Power Automate is scalable. We have a very large organization with at least 70 people who are using this solution.

Recently we have engaged with Microsoft to conduct a four or six-week training period. During the training session, there were approximately 180 participants.

I have not contacted technical support from Microsoft.

They do have support on their website and have documentation available for learning through the portals, which is very helpful.

I have experience with UiPath for RPA. I am leading and heading a small team that is building automations, and we have been primarily working on UiPath for this.

The initial setup was simple.

It only took a few minutes to deploy.

I completed the installation on my system myself.

I am not aware of the recent pricing model, but during the time that I was using this solution is was reasonable.

They have certain options that are available at a minimal cost and I am sure that if you buy more components of the Power platform then there are certain pricing models that are catered to the needs of all kinds of companies.

What happens in the Microsoft platform is that users cannot be self-sufficient with one product. You require Power Automate, PowerBI, Power Apps, and different components of the Power platform. If you have the entire set of applications then things become easy, and they can rate this tool highly. If, however, they don't have all of the tools, then the capability is reduced.

We have plans to continue using this solution in the future. We will continue by integrating all of the Microsoft components. This is very helpful, and we can also use different platforms for different clients.

This is definitely a product that I can recommend.

I would rate this solution a 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.

We are using it for automating legacy systems as well as email verifications. I haven't touched on the APIs yet, but the use case is for user accessibility to and from data sources.

The solution is still in the development phase. It is not in the production run at the moment. Therefore, at the moment, there is not a significant visible improvement.

In terms of deployment, it is a mix of hybrid cloud and on-premises. Microsoft is the cloud provider. It is a single environment deployed over multiple branches in each province of the country. Currently, the version that we are using is the latest Microsoft release.

Its ease of use is most valuable. A lot of the bulk functionality is done either through standalone or custom connectors and standard API processes. 

There are two versions of the automation suite. You've got your cloud functionality, and you have got your on-premises functionality for legacy systems. There are a lot of functionalities between the two systems that don't cross-correlate with each other. A lot of the functionality in the cloud system is not there on the production side in the on-prem system. If they could implement some of the similar functionalities and streamline them for integration, it would be a lot easier. There should be seamless integration between the two systems.

I have been using this solution for three months.

It is highly stable with good performance.

It is extremely scalable. It integrates with a lot of existing systems, both Microsoft-related and non-Microsoft-related, and it is extremely extensible. The additional support validation and software integrations that are available are limitless.

Our experience of the technical support on the solution has been minimal because there have not been a lot of technical issues with the implementation. The turnaround time for any type of technical query is usually a day to two days, but before that time period is up, they either have a solution or a guaranteed workaround.

We previously used Automation Anywhere. We switched because of the ease of use. The functionality of Automation Anywhere is for a very specialized use case scenario. They focus on a lot of areas, but Power Automate has a lot of simpler solutions and easier approaches. For example, we have a solution in place that has three or four RPA scripts for a single process. With the Power Automate solution, we have a single script running for maybe five sub-processes. It is a lot more streamlined and consistent.

At the moment, it is still in development and is a matter of integration. It does require a bit more technical know-how, but it is mainly done from the environment perspective and from an administrative point of view. 

From a development point of view, the crossover is pretty much the same for going, for instance, from Blue Prism to UiPath, or UiPath to Automation Anywhere. There's a transition period level of difficulty. So, from a development point of view, it's fairly the same, but from a technical point of view, Microsoft does require a bit more technical know-how to get the environment set up.

With some of the integration conversions we've done from one platform to the other, from a development standpoint, it has taken us close to a month in the development environments, and this is interrupted. If we had an uninterrupted conversion, I would estimate a maximum of a week. We just need to get it converted and implemented.

We've been doing everything in-house with direct help from a Microsoft representative. We have a single person to take care of it. It doesn't require a massive deployment team.

So far, based on the development calculators that we've been running, it's running far smoother and far more efficiently and faster. So, the estimated return on investment over the past three months that we've been calculating has been looking far higher than the Automation Anywhere solution.

At the moment, from our experience with the two, Power Automate is a lot more expensive solution than Automation Anywhere, but it is also a far more reliable solution. 

With the price increases and with the current pandemic situation going on worldwide, a lot of the prices have fluctuated, but the packages and the all-encompassing features you get with the Microsoft package far outweigh the benefits from the Automation Anywhere side. Each package on the Automation Anywhere side is cheaper, but we need to continuously purchase subsequent packages to continue with our automation to the extent that we require. So, the Power Automate solution is a bit more pricey, but it does offer us a far better range of capabilities.

There are different development plans that you can use. Additional licenses might be required for additional features, such as your Azure Logic or your Dataverse capacity. There is a limited capacity package that you can purchase, and then you have to have an additional license for added capacity.

I would advise paying critical attention to the environment that you're setting up. User access roles, either through Active Directory or through the database control method, should be the key focus. After that, you need to assign roles and licenses as necessary. From there on, you need to integrate the system. 

The Microsoft documentation portal for both cloud and on-premises is going to be the easiest to follow. All the solutions are there. For technical assistance from the Microsoft side, contact details are available on the documentation portal for any type of query.

I would rate it a solid eight out of ten. For me to give it a ten, there should be seamless integration between both the cloud and the on-premises solutions. There should be the exact same or similar functionality between the two to make the entire automation process a bit more streamlined.

I use it for robotic process automation.

It is a low-code platform. It is easy to use and good for automating small tasks such as expense approvals, timesheet approvals, etc.

I would like more integration with other tools. It integrates well with Microsoft products, but there should be more integration with other platforms and tools, such as chatbots.

I have been using this solution for two years.

It is stable.

It depends on the use case. For my use cases, it is scalable.

We have over 10,000 people in my organization. In my branch, we have 100 people, and almost all of us in this branch have Microsoft Office, Microsoft Teams, and other solutions. We have approximately 20 users who use Microsoft Power Automate.

Any increase in its usage would depend on our clients. I work for a consultancy firm, so it depends on what our clients want. For our office work, we will keep using it.

I have not had to ask for technical support because the tasks that I do are easy.

I also use UiPath.

My company has a Microsoft package, and it was a part of the package. I didn't have to do any installation.

They have the community edition that people can use for free, and they also have the enterprise edition. My company uses the enterprise edition, and I don't know how much they pay.

It has been good so far. I would rate it an eight out of 10.

Our use cases are everything from replacing Excel macros to replacing WINAutomate to larger initiatives to use RPAbox to fill in different back-office systems and so on. We have a huge range of solutions.

In terms of the most valuable features, the RPA is really great.

The license cost could be better.

The PMU connectors we can use cost extra, and the RPA also costs extra. So hopefully they can let go of that way of working and allow us to use the entire tool in a better way. That's what we're looking for.

I've been using the solution for approximately three years.

The stability is great. I know we don't have a problem with stability in this case.

To implement the solution or share the solution with others, you can scale it up; but we don't scale in that perspective when it comes to add more functionality. We have other solutions when it comes to larger initiatives. Microsoft platform is used for something happens over here, do this. Or we are using Box, but when it comes to larger initiative, we're using Nintex. It's longer processes and longer workflows. It's easier to use. So when we scale up, we switch to another application actually.

We have talked to Microsoft. We're a large company and we're talking to Microsoft on a regular basis. We have a partner we talk to when it comes to Automate. We are absolutely satisfied with technical support.

The initial setup was quite simple, actually.

We implemented both with help from the vendor and within the company. Some using our own expectation in Office, but we have some vendors we had contact with.

We need to keep track that we are compliant regarding the license, but other than that, it's quite easy to maintain and govern. We have approximately 50 users in different countries in Europe.

Microsoft is connected very well with Microsoft products. Everything in the master suite is really easy to connect to, and the Blue Prism is for large initiatives. What I heard from the developers using Blue Prism is it's easier to overview quite complex scenarios actually. Power Automate is a little harder to have the overlook of what you have done in the script.

I'd rate the solution a seven out of ten.

Start using the solution at a small scale, and create some smaller script of your own. Then you can see what can be done and easily grow with a task and try features for the department you're working in to share with your colleagues. You'll have an understanding of how to automate, and you can see the business from the other's perspective. That's what we have done. Start small and go big.

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

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

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

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

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

Their technical support is okay.

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

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

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

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

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

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

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.