Microsoft Power Automate Reviews

Our use case is for presenting price regeneration. I'm the technical lead for robotics and we are customers of Microsoft. 

As a part of the Microsoft suite, this is a convenient product for us because it integrates well with other Microsoft products. We've also found third-party integrations with third-party applications is quite easy.

I think the speed of the application could be improved. If you're looking at Power BI dashboards, for example, the back-end processing is fine, but when you look at it from a UI point of view, which is what the client sees, the speed of execution could be improved. 

We've been using this product for five years. 

We haven't had any issues with stability. 

The scalability is good, we have around 25 users. 

Microsoft provides very prompt support. 

The initial setup is relatively straightforward and takes a couple of weeks. There's not much maintenance involved because it's part of a larger solution. 

We have seen ROI on investment although it's difficult to quantify. 

The product is fairly priced; the cost is part of the enterprise solution. 

I recommend doing a POC to ensure the product is fit for purpose. 

I rate this solution nine out of 10. 

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.

The primary use cases we are focusing on are applying automation to processes and integrating systems with API uploads. We have developed a module to handle private information related to the applications and API uploads to ensure the process is feasible without any challenges.

I believe document reading has been beneficial when dealing with Microsoft. 

There have been some challenges. We have struggled to take advantage of the power of the program due to the complexity of the reports we want to send to Microsoft. This includes client complaints, large discrepancies, and delays from data centers to solve the issues. As a result, we have faced both advantages and disadvantages. After some time, I believe Microsoft may have made changes to the backend that we are not aware of. This could cause issues, and the client has experienced instability in the current process. To address this, we need to make sure that any changes to the backend are documented and communicated clearly to avoid any potential issues.

The technical support has room for improvement.

I have been using the solution for six years.

I give the scalability of the solution a seven out of ten. The licensing is not bad but scaling requires additional work on the solution.

The solution is intended more for small and medium-sized organizations, not for large more complex companies.

We have 5,000 people using the solution.

The technical support attempts to address any queries, but their knowledge is limited. They try to come up with solutions for new problems and document them if they yield results so that if someone else has the same issue, they can get the same solution. However, they are technically struggling. To resolve the issues, Microsoft created a system where their internal technical team works with a mediator who understands the problem but may not understand the technical details. This mediator then takes the ticket up to the technical team analyzes the issue and provides a resolution. This system has saved them time in responding to and resolving the issue.

The initial setup is great. We're currently building with the connectors. However, automating the process may require additional hardware, which can take time to implement. We have to apply the policy and see how their applications access information. To accommodate the additional hardware, our plan has to be adjusted, but if we don't involve any alternatives, we can deploy more easily. 

The automation portion if required is a different department but for the basic setup, we only require two to four people.

The license is 20 million rupees per month. The cost is okay but we are paying per month. Microsoft is providing a license that is automatic which is very helpful. But we know that of the solution, we don't have any annual subscriptions. We pay monthly, otherwise, we choose another solution.

Microsoft is providing an automatic license with a cost of $20 million per month, which is reasonable. However, we don't have any annual subscription options, so we must pay monthly or choose another solution.

I give the solution a seven out of ten.

Microsoft is predicting that improvements will come in the future which will be better than what's currently available in the market. Even if they can build simple and medium processes, they still need to add certain elements and acquire certain licenses in order to run the machine from one place to another. We need to let go of the keys, such as a community rotation which we are automating. I don't believe updates should be pushed for those who are happy with the version they are using because that version is capable and we have fixes for any issues that may come up. Microsoft is now focused on automating development processes. It is important that Microsoft give the community rotation back to users, as we are all users. Regardless of size, we need to be aware of the upgrades that are being made.

We don't believe additional personnel is required for maintenance. We currently have adequate processes in place and automation. In total, there are fifty processes running, two for every system. Therefore, we do not anticipate needing to increase personnel for maintenance purposes.

The other departments have implemented the AP60 and are currently working on it. In my department, we are using Power Automate which is working but I need to check what progress the other departments have made and if they are facing any challenges to determine if it is easier to build with AP60 or with Power Automate.

There are many alternative solutions to Power Automate that also are cloud-based that I believe offer an annual subscription but I am not sure.

I would suggest starting with simple or medium processes, rather than complex ones. Begin with a pilot project to determine if it is profitable or not. We should also try to find a way to automate the process, as it could otherwise become stuck. Additionally, it is important to consider any issues that could arise with the elements that are currently working; the same elements may fail tomorrow. Ultimately, if we can handle these issues in the development phase, the solution will function great.

To me, what's most useful in WinAutomation by Softomotive is that it's quite intuitive, especially because most of the capabilities of the older WinAutomation remain. You also don't need to do or know hard coding, and this is another useful feature of the solution.

I also like that WinAutomation by Softomotive integrates very well with Microsoft products, especially Microsoft Office, and this is great news because most companies use Microsoft Office. Having a very good integration with the Microsoft Office suite covers a lot of bases, and is one of the advantages of WinAutomation by Softomotive.

What needs improvement in WinAutomation by Softomotive is its stability. Stability is quite important to me. Another area for improvement in the solution is robot scheduling because it's not 100% accurate, in particular, it's 90% accurate. The monitoring of the robot could also be improved because it's not very straightforward, and you have to look in a few places or at least two places which means that monitoring is not a one-glance process.

I've been using WinAutomation by Softomotive for one and a half years.

WinAutomation by Softomotive is not a very stable product. It used to be a desktop application and was installed locally. It's a desktop application, but it's a cloud application at the same time, so the main problem is the integration with cloud services, the updates, and the refresh rate, plus its compatibility with other Microsoft applications. This means that WinAutomation by Softomotive requires frequent updates, and this is not bad. It's okay, but the point is that it's not very stable in the short run. The WinAutomation by Softomotive team usually addresses this issue, so if my company has a problem today, for example, within a few days, that issue will be solved, but in the short run, the solution is not very stable.

WinAutomation by Softomotive is a scalable product.

I didn't use the technical support for WinAutomation by Softomotive much. At the very beginning, I used it because of the licensing requirement when I transferred my account from WinAutomation by Softomotive to Power Automate. Currently, the documentation is pretty good, so I didn't use the technical support even through chat, phone, or email correspondence, so I'm unable to evaluate support for the solution.

In terms of the installation of WinAutomation by Softomotive, it wasn't as straightforward, specifically for the license administration because you have to be enrolled on the portal. I'm referring to the new version of WinAutomation which is now Power Automate, but the original WinAutomation by Softomotive only took ten minutes to install. The Power Automate version, on the other hand, wasn't impossible to install, but it wasn't straightforward.

I could say that my organization has ROI from WinAutomation by Softomotive.

My company switched to a monthly payment for the WinAutomation by Softomotive license. I don't have the exact figure, but it roughly amounts to 500 Euros a year which isn't bad.

I use WinAutomation by Softomotive, but the solution was bought by Microsoft, so it's now a part of Power Automate.

In my company, about twenty people use WinAutomation by Softomotive daily. I belong to a small company.

My advice to people looking into implementing WinAutomation by Softomotive is that it's a good solution, and I would recommend it for small-scale operations, for example, to automate back office operations. I would not recommend it for large-scale or for critical operations because it returns quite a lot of errors, not only automation errors, but also errors when liaising with other applications, so in some cases, those applications may not run properly, resulting in errors. From my point of view, I will not recommend WinAutomation by Softomotive for critical operations, unless it's stabilized in the future, and at the moment, the "transformation" of WinAutomation into Power Automate is still ongoing.

My rating for WinAutomation by Softomotive is nine out of ten.

Repetitive interactions between legacy systems and Excel managed by human resource. By collecting small tasks, there would be tons of time/effort we can replace with RPA. However, my challenge was major RPA solutions are not so much cheap to be applied to these small tasks. I believe Power Automate would be sufficient and cheap enough as Microsoft announced it will be free for Win 10 users (with basic functionalities).

It is still a persona trial phase so not much change has been brought. However, I have convinced Power Automate Desktop can be enough for many use cases where much investments are difficult.

Interaction with Microsoft Excel is good and will be more better in the future.

More detailed explanatory manuals are desired. As new features are introduced every month, I would like to know what is new and what is changed recently.

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

I'm not sure whether the desktop version is stable. It is relatively new. It was launched in May. I haven't really tried it. But the trial version I'm using has been stable so far. 

I haven't tried to scale it, so I'm not quite sure. 

So far, the tech support has provided me with good enough support and knowledge. 

Power Automate has two versions. The initial setup of the trial version is really easy. All you have to do is just activate the environment and you can start working on it. However, for desktop version, you need to install the software. It should be as easy to download and install as the Office 365 environment. 

How long it takes to deploy will depend on how confident you are with your development. The development itself is not easy. 

I live in Japan and there are not very many consultants available for the latest Power Automate yet as Microsoft is investing quite a lot and new versions are released every month.

Should be high, as unattended RPA capabilities are available at almost free as I can utilize it under o365 license. No extra costs to start small and you can pay extra if you need premium services.

I would recommend Power Automate. Those will small use cases can use a free license. 

We evaluated Blue Prism and Pega. However, Pega was a bit difficult to use for citizen developers. It requires some support from consultants or engineers, so it's a bit of an investment. They're small and if we introduced consultants or engineers, then it wouldn't pay off. So for that use-cases, yeah, users lost interest. 

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.

Our clients utilize Power Automate for data collection and management in various ways. One primary use is integrating Customer Engagement (CE) with finance, operations, or other business systems. Additionally, we employ Power Automate to facilitate additional processes, such as automating workflows.

Firstly, enhancing Power Automate to work synchronously instead of asynchronously would eliminate the need for additional coding, saving time in project implementation. Secondly, addressing the limitations on the number of processes in Power Automate tracking would enhance its usability and flexibility for various scenarios. Incorporating a more intuitive user interface or experience would be beneficial for overall solution implementation. While PowerApps can provide this to some extent, it faces limitations, particularly with large datasets. Overcoming these challenges through enhancements or optimization would be valuable for implementing enterprise-class solutions effectively.

We have been using Microsoft Power Automate for 2 years.

I rate the platform's stability an eight out of ten.

Certain limitations apply to product scalability in enterprise environments or critical systems. We work with medium-sized businesses.

The deployment time depends on specific project requirements. Complicated configurations take three to four months to complete, while certain simple projects can be completed within two weeks.

I rate the process an eight out of ten.

When we purchase the Microsoft Dynamics license, the Power Automate license is often free, albeit with some limitations, such as a certain number of transactions per user. Given the substantial allocation provided, this arrangement typically suffices for most users. However, if premium features are desired or the project demands exceed the allocated resources, additional charges may apply accordingly.

I rate the pricing a six out of ten.

One of the automations we've implemented with Power Automate that significantly saves time involves discount application on quotations. When a discount is applied at the quotation level, we utilize it to automatically apply line-level discounts to the respective lines, distributing them equally.

The feature most useful for integrating different applications is its ability to create flows. Specifically, we use flows to integrate with finance and operations.

The cloud-based nature of Power Automate has greatly benefited our workflows. It operates exclusively on the cloud, eliminating the need for on-premises deployment. It enables low-code development, eliminating the need to create plugins. It saves a significant amount of time, reduces efforts, and enhances reliability in our automation processes.

I rate it an eight out of ten.

We use the solution for dashboard reporting, RPA, and account management.

The product has helped us with support generation. We supported a client who required 42 hours of manual work every month. The solution enabled us to automate the process and save time.

The solution is integrated with Microsoft. It can be integrated with different platforms. The product is very reliable and very easy to use. Anyone can learn to use it.

The product should improve its RPA capabilities.

The product should add AI capabilities.

I have been using this solution for four to five years.

I rate the solution’s stability a nine out of ten.

I rate the solution’s scalability an eight out of ten.

The initial setup is easy. I rate the ease of setup a nine out of ten.

The time taken for deployment depends on the project. A small project would take a week to deploy. RPA, on the other hand, takes two months.

I use the latest version of the solution. We use the solution daily. People using the solution should maximize their usability to get a good return on investment. Overall, I rate the solution a ten out of ten.