Try our new research platform with insights from 80,000+ expert users
Owner at maricau consulting
Real User
Easy to use solution with automated reporting capability
Pros and Cons
  • "This solution improved the reporting in our organization. The financial department was doing a lot of copy pasting from different sources to create financial reports. Through ProcessRobot, we were able to automate all those copy pasting and produce all those financial reports overnight."
  • "Some automation features on some programs did not work smoothly."

What is our primary use case?

It's an RPA (Robotic Process Automation), so it's a robot and we use it to automate a lot of financial reports.

How has it helped my organization?

This solution improved the reporting in our organization. The financial department was doing a lot of copy-pasting from different sources to create financial reports. Through ProcessRobot, we were able to automate all those copy-pasting and produce all those financial reports overnight. Our financial department was able to free up a lot of their time. They no longer need to invest their time in the work, particularly in creating the report. They can focus their time on analyzing the data more, rather than exerting more time in report creation.

What is most valuable?

This solution is easy to use. It was one of the easiest to use, plus the price-quality was the reason why we selected this. Its features for its price were the best fit for our company.

What needs improvement?

As for what could be improved in this solution: I tried to do some automation on Microsoft Dynamics AX and it was not successful. The integration with Dynamics AX was not really a success, but for the rest, I don't have problems with.

Some automation features on some programs did not work smoothly, so that's a negative feature. That might be solved now with the newer version because Microsoft took over Softomotive. I hope they have improved that feature and that it now works better with their own software.

I'm not really missing features I'd like to see on the next release because we only use it for a really small target area. We just use it for reporting. It's not like we're using it extensively on test automation and other similar processes, but I know we can do a lot more with this solution.

Buyer's Guide
Microsoft Power Automate
January 2025
Learn what your peers think about Microsoft Power Automate. Get advice and tips from experienced pros sharing their opinions. Updated: January 2025.
832,138 professionals have used our research since 2012.

For how long have I used the solution?

We've been using this solution for three years now.

What do I think about the stability of the solution?

This solution is really stable.

What do I think about the scalability of the solution?

About the scalability of this solution, we're using the desktop version now, and I know that there's some other version. We can scale it up to use more robots, but we don't have a requirement for it currently.

How are customer service and support?

The technical support for this solution was really okay. Information on the website was documented well e.g. there were nice manuals. I didn't use their technical support, but the website where I could find all the technical documentation was really good. Because it was well-documented, it was self-explanatory and I could start from there.

Which solution did I use previously and why did I switch?

We used two different solutions, but we switched because they were too expensive for the purpose we wanted to use those solutions for.

How was the initial setup?

Setting up this solution was really straightforward. It just needed a little bit of clicking. It only took a few minutes to install as it's a really simple program. It's not complicated.

What about the implementation team?

Implementing this solution was self-explanatory. I did the implementation myself.

What was our ROI?

We saw a significant return on investment because we were able to save a lot of time from our financial and human resources staff, so this saves a lot of money and the return on investment on that 1,000 euros is quickly felt.

What's my experience with pricing, setup cost, and licensing?

We paid for one license for this solution. It was a lifetime license for this version (version 8), and we paid around 1,000 euros. At the moment, as long as we use this version, there is no additional cost, but when we upgrade to the new version, it will be a monthly subscription.

We bought the license from Softomotive, so we had one license and that license was restricted to version eight. When we upgrade to the newest version, we would need to buy that upgrade, because Microsoft has taken over Softomotive and they no longer sell licenses. They only sell monthly subscriptions.

We have to transfer our license to a Microsoft subscription, and though they will give a redemption, the cost will change, so this is also one of the reasons why we didn't change to the new version yet.

Which other solutions did I evaluate?

We evaluated other solutions: UiPath and Kofax.

What other advice do I have?

You're using an older version. Now, Microsoft has taken over this version and they're calling it Power Automate desktop. I think a lot of improvements have already been done to the newest version, so what I'm going to tell you about the old version will no longer be relevant. We need to upgrade to the new version then check if the problems we were having have been fixed in the new version. Overall, we are satisfied with what we use it for because I think it's quite okay for our use case.

The name ProcessRobot doesn't exist anymore. Softomotive has been taken over by Microsoft so this solution has been rebranded by Microsoft to Power Automate desktop.

It's a robot, so it's operating on a server on its own. There's no real user, but it's trying to replace users. There's only one developer who is creating the tasks on that system. We also don't require anyone for its maintenance.

At the moment, we're using this solution to create a report of 50, so we have 50 data scripts running each night. We're planning to extend its use with a couple of reports, but for now, there's no need to further use it for other tasks.

My advice to others looking into implementing ProcessRobot is to try it first because it's free now, so you can test it. You can test it for free on the Windows 11 version. It's delivered by Microsoft for free. Go ahead and test it. The solution is nice and fast.

I would give this solution a rating of eight or nine. Let's say nine out of ten. I couldn't find any pictures for my use case. I think this was the best choice we could make, and ten is too perfect for rating a solution.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Technical Analyst at Miral
Real User
Top 10
Good document reading, and is scalable, but has complex reporting
Pros and Cons
  • "I believe document reading has been beneficial when dealing with Microsoft."
  • "The technical support has room for improvement."

What is our primary use case?

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.

What is most valuable?

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

What needs improvement?

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.

For how long have I used the solution?

I have been using the solution for six years.

What do I think about the scalability of the solution?

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.

How are customer service and support?

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.

What about the implementation team?

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.

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Microsoft Power Automate
January 2025
Learn what your peers think about Microsoft Power Automate. Get advice and tips from experienced pros sharing their opinions. Updated: January 2025.
832,138 professionals have used our research since 2012.
IT Team Lead at Kantar
Real User
An RPA specifically for Microsoft applications, but very limited in process complexity and integrations
Pros and Cons
  • "The most valuable feature is that it is very easy to use."
  • "The tasks that can be automated are limited to Microsoft applications only."
  • "Any task that is automated needs to be very simple. This tool does not seem to handle complicated tasks very well."

What is our primary use case?

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.  

How has it helped my organization?

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.  

What is most valuable?

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.  

What needs improvement?

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.  

For how long have I used the solution?

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

What do I think about the stability of the solution?

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.  

What do I think about the scalability of the solution?

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.  

How are customer service and technical support?

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.  

How was the initial setup?

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.   

What's my experience with pricing, setup cost, and licensing?

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

Which other solutions did I evaluate?

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.  

What other advice do I have?

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.  

Which deployment model are you using for this solution?

Hybrid Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Architecte Entreprise Collaboration at a transportation company with 10,001+ employees
Real User
Good integration with the Office 365 ecosystem and globally stable, but needs better licensing model and support for visual process editing
Pros and Cons
  • "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."

What is our primary use case?

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.

What is most valuable?

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

What needs improvement?

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.

For how long have I used the solution?

I have been using this solution for three years.

What do I think about the stability of the solution?

It is globally stable.

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

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.

How was the initial setup?

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

What's my experience with pricing, setup cost, and licensing?

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. 

What other advice do I have?

I would recommend this solution to others. I would rate Microsoft Power Automate a seven out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Maria Irimias - PeerSpot reviewer
Data, Analytics & AI | Business Hyperautomation | Intelligent Workplace Service Manager at Accesa
MSP
Top 10
Advance automation with user-friendly no-code platform templates
Pros and Cons
  • "Microsoft Power Automate is a no-code platform which is very easy to learn, allowing businesses to build their own small automations."
  • "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."

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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

How are customer service and support?

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

How would you rate customer service and support?

Positive

How was the initial setup?

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

What was our ROI?

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

What's my experience with pricing, setup cost, and licensing?

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.

Which other solutions did I evaluate?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

Hybrid Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: My company has a business relationship with this vendor other than being a customer:
Flag as inappropriate
PeerSpot user
Head of IT/Department leader at Apoteksverk
Reseller
Top 20
Allows employees to create and automate workflows and tasks across various applications
Pros and Cons
  • "The solution has saved us hours of work."
  • "I would like to see better data integration with different sources."

What is our primary use case?

We mainly use it in connection with our drug inventories. We use Power Automate to import the files we get from various wholesalers. We also check the prices in our back office.

We are a pharmaceutical compounds organization and also get prescriptions. We have a portal where GPs and doctors can prescribe patients. At the moment, we are looking to put more data into the database so that we can see some statistics from Power BI.

How has it helped my organization?

The solution has saved us hours of work. The solution does the work instead of employees.

What is most valuable?


What needs improvement?

We are looking for more data integration with various resources. Our plan is to have a deeper look at it in November when we are in Seattle for the two conferences. We would like to consolidate the data from various sources and extract it in order to analyze it. We used an RPA tool and looked at the ML part of it as well. 

I would like to see better data integration with different sources. 

For how long have I used the solution?

I have using Microsoft Automate for a year and a half. 

What do I think about the stability of the solution?

It is a stable solution. I rate the stability an eight out of ten. 

What do I think about the scalability of the solution?

It is a scalable solution. Presently, three to four hundred users use the solution and all our clients are small organizations. I would rate it a seven out of ten. 

How are customer service and support?

The technical support team is good. 

How would you rate customer service and support?

Positive

How was the initial setup?

The initial setup is moderately straightforward. The deployment takes a week's time. I would rate the initial setup a seven out of ten. 

What about the implementation team?

The deployment is done by consultants. 

What's my experience with pricing, setup cost, and licensing?

The solution's price is reasonable. I rate the pricing a five out of ten. 

What other advice do I have?

I recommend the solution but I would advise people to get a consultant even if they know someone who has knowledge of Microsoft Power Automate, as it is the fastest way to automate it. I would rate the overall solution a seven out of ten. 

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer:
PeerSpot user
DJ Kim - PeerSpot reviewer
CEO at BigxData
Real User
Top 5
Easy to use, cost-effective solution to automate internal processes
Pros and Cons
  • "The solution is relatively easy to use and cost-effective."
  • "The UI of the solution is not so good."

What is our primary use case?

We use the solution to automate internal processes like leave applications.

What is most valuable?

The solution is relatively easy to use and cost-effective. It is also easy to learn and understand. It is part of Microsoft 365, so it's free. Additionally, it is easy to integrate Microsoft Teams with the solution.

What needs improvement?

The UI of the solution is not so good. Power BI's reporting functionality should be improved. 

The next release should include more functionalities and better reporting.

For how long have I used the solution?

I have been using the solution for three years.

What do I think about the stability of the solution?

I rate the stability an eight or nine out of ten.

What do I think about the scalability of the solution?

I rate the scalability a seven or eight out of ten. Around 50 people in the organization use the solution, including five to seven administrators, 30 to 40 engineers, and nine to ten sales and marketing staff.

Which solution did I use previously and why did I switch?

Previously we used Google Suite in collaboration with many other solutions. We needed it for process automation and for creating electronic signatures. It required us to subscribe to multiple solutions. However, we wanted only one or two platforms. So, we switched to Microsoft.

What about the implementation team?

The solution is not so difficult to deploy. The deployment takes up to two hours. I could deploy the solution myself. One engineer is enough for the maintenance of the solution.

What's my experience with pricing, setup cost, and licensing?

The solution is free with Microsoft 365.

What other advice do I have?

I would recommend Microsoft Power Automate to those who use Microsoft 365. We search the instruction manual, FAQs, and other online documents when we face issues with the solution. Overall, I rate the product a nine out of ten.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Deepak Thomas - PeerSpot reviewer
Technical Lead at Standard Bank South Africa
Real User
Top 20
Stable and scalable; third-party integrations are relatively easy
Pros and Cons
  • "Third-party integrations with third-party applications are quite easy."
  • "The speed of the application could be improved."

What is our primary use case?

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

What is most valuable?

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.

What needs improvement?

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. 

For how long have I used the solution?

We've been using this product for five years. 

What do I think about the stability of the solution?

We haven't had any issues with stability. 

What do I think about the scalability of the solution?

The scalability is good, we have around 25 users. 

How are customer service and support?

Microsoft provides very prompt support. 

How was the initial setup?

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. 

What was our ROI?

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

What's my experience with pricing, setup cost, and licensing?

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

What other advice do I have?

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

I rate this solution nine out of 10. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free Microsoft Power Automate Report and get advice and tips from experienced pros sharing their opinions.
Updated: January 2025
Buyer's Guide
Download our free Microsoft Power Automate Report and get advice and tips from experienced pros sharing their opinions.