Try our new research platform with insights from 80,000+ expert users
reviewer1268505 - PeerSpot reviewer
Digital and E-Business Analyst at a construction company with 5,001-10,000 employees
Real User
Top 20
Out-of-the-box connectors make it easy to use and it has good reporting
Pros and Cons
  • "This product is a really easy-to-use solution for quickly developing prototypes."
  • "If the product had onscreen help, it would be easier to learn and use."

What is our primary use case?

Our primary use for this product is for the automation of manual tasks that may require some small integrations between systems. An example would be something like automatically sending an email from an action that is performed on our online system. Another might be writing data to our CRM database based on the input from an online form.  

How has it helped my organization?

The thing that this product has provided is a solution for quickly developing prototypes. We can create some new solutions really fast, test it to understand exactly which data is needed and then deploy the solution moving forward quickly through the process. That has been important for us. It is not necessarily that we all use Power Automate as a production-ready solution. It is more that we can use it to make prototypes that we can test with.  

What is most valuable?

I think the most valuable thing about this product for me is that it is really quick and easy to use. You do not need to have a lot of development skills to be able to create solutions. There is very little code involved, which is great, and it is very logical. It has also got great reporting. You can see the success and failure of each item that has been run through it. There are a lot of out-of-the-box connectors as well that make things easier.  

What needs improvement?

To improve the product, I think it would be great to see even more connectors available out-of-the-box and more maturity in that direction. I would also like to see some readiness for creating test and production environments so that you can differentiate which environment is you are working in.  

As far as additional features I am not sure what could really improve the product. It could maybe do with some more insights like triggered alerts.  

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

For how long have I used the solution?

We have been using this product for about a year.  

What do I think about the stability of the solution?

So far we find that the stability of the product is really good. There is also good reporting if it is down for any reason. We have not really experienced stability problems or had any complaints about that.  

What do I think about the scalability of the solution?

The scalability is really good. We have been able to use it for lots of different kinds of things. We do think that Power Automate is more for prototyping than for production-ready applications. You should probably upgrade to using Power Apps if you need something production-ready. You can build something quickly as a prototype in Power Automate and then upgrade to Power App to create a more refined application. Using those together means that what you develop is more production-ready. But in general, I think it is really scalable. There are lots of different use cases and lots of different solutions you can build and make available.  

There are not a lot of people currently using the product in the company — maybe like 10 or 12. We really want more and more people to use it, but it is not our job to roll it out to everybody. We just found it and thought it was interesting. We share it with people when they want to know how to try and automate something. But it is not something we had planned to really roll out company-wide as a solution initially.  

We will eventually roll it out to more people as we grow with it and discover more uses.  

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

We did not really use a different solution before Microsoft Power Automate. We were using Flow originally, which is what the same product was called before it became Power Automate. The name change was just within the last two months.  

How was the initial setup?

The initial setup is really straightforward. It is immediately available out-of-the-box when you have Microsoft Cloud. You just click on the button and it is there ready to use.  

Our deployment took maybe a week or so. Most of that was just to play around and get familiar with it and become ready to start doing actual projects. Because you are building your own little mini-applications inside of it and the framework is available already, it is just a matter of learning how to work with the tool. You need to learn how to use it to build what you want to build.  

There were only two people involved in the deployment process. It did not require a lot of effort. It was just a couple of minutes to be ready to start using it and a week to get to the point where we could be productive.  

The framework for the product is maintained by Microsoft. Any applications that we build inside of it is all we need to maintain ourselves. So we do not have to maintain the framework at all.  

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

Power Automate is really cost-effective. You pay for use and if you want a premium connector then you just pay for a premium connector. But a lot of things are available for free. If you want to use an adapter that is not available for free, then you have to pay the provider for it. I do not know how much that costs.  

What other advice do I have?

My advice to people who are considering implementing Microsoft Power Automate is that I think it is a really great tool that allows you to get started quickly on prototyping and integrating solutions that will simplify some redundant tasks. The best idea would be to just get started with it and experience what it can do.  

The biggest lesson we have learned from using Microsoft Power Automate is that there is just so much that is possible to automate. Thinking about the potential scope of what the tool can do, we now look at a problem and think that maybe we can use Power Automate to resolve the issue.  

On a scale from one to ten where one is the worst and ten is the best, I would rate Microsoft Power Automate as a nine-out-of-ten at this point. To become a ten they would just need some more maturity with the test and production environments and making things more production-ready. Also, some additional guided help would valuable for new users to orient them and get started building their own applications. But other than that, it is perfect.  

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: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
reviewer1777569 - PeerSpot reviewer
Senior Consultant at a tech services company with 10,001+ employees
Real User
Reasonably priced, responsive technical support, simple to use and install
Pros and Cons
  • "You can automate almost everything in your organization by simply dragging and dropping and selecting a few options, whether it's an Excel spreadsheet or other on-premise data."
  • "These products have some limitations, such as the need to build some custom controls in PCF or use the JSON format."

What is our primary use case?

We use Microsoft Power Automate when we need to automate manual processes in our automation, or when we need to send a document for approval, or when we need to integrate some beams channels and messages.

What is most valuable?

It's quite simple to use. You can automate almost everything in your organization by simply dragging and dropping and selecting a few options, whether it's an Excel spreadsheet or other on-premise data.

Power Automate is integrating artificial intelligence into the product, allowing us to automate future aspects, such as in pharma companies, medical agencies, and even banks, which are now using these products to automate their manual processes. And because robotic process automation is already built into Power Automate, these features make this product fantastic and accessible to everyone.

These products are intended low-code, no-code solutions. As a result, even a strategic developer can create and automate your day-to-day tasks at their workplace, whether it's management work or a developer is dealing with day-to-day issues with APIs.

In terms of IT, everything can be automated, but other things can also be automated. We can automate the reporting process, as we can with the help of an AI builder. Using Power Automate and Power Apps, we can generate sales reports on the fly.

What needs improvement?

In terms of issues, I haven't had any until now because automation requires you to complete a task in less time. These products have some limitations, such as the need to build some custom controls in PCF or use the JSON format. There are some limitations, but it's a mature Microsoft product, and we can do almost everything.

Third-party systems can also be added. We can create a beautiful dashboard if another software provides open APIs. Even when discussing complete Power platforms, four components must be mentioned: Power Apps, Power Automate, Power Virtual Agents, and Power BI. When we use all four, we can create a complete solution, whether it's a visualization dashboard, automated chatbots, or the rest, which we can achieve using Power Apps. Power Apps is also divided into three types of apps: canvas apps, model-driven apps, and data-driven apps. Another option is to use open-source, which refers to open projects known as portals. So we can actually do the same thing. When someone is creating a website, we can do the same thing here in the portal. So the things we can do with Power Apps are the same as the things we can do with the Power platform.

For how long have I used the solution?

I have been working with Microsoft Power Automate for almost two years.

What do I think about the stability of the solution?

There are some limitations with the calls and other things, but it is a stable product.

How are customer service and support?

Typically, we raise technical support through the Azure portal. If we have a basic plan in place, we can submit a request to Microsoft. 

Microsoft also provides Twitter support. If you have any questions or encounter any technical difficulties while deploying your Power App or configuring your Power Apps or Power Automate environment, you can raise a ticket on the portal and Microsoft will respond directly to you.

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

I also work with Power Apps.

How was the initial setup?

The initial setup is a very simple procedure. We can deploy in any organization depending on their needs,  we can look into licenses to see what kind of license will meet their requirements. 

As it is in the cloud, it's very simple to deploy. It's ready-to-use software as a service, and we can use various connectors. In addition, if something is outside the scope of Power Automate, we can create a custom connector. How it is deployed is entirely up to the organization. If for example, they have three environments: development, testing, and production, we can easily switch, and we can use Azure DevOps to create CI/CD pipelines, and we can deploy that solution in any environment in the organization.

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

It is not a costly solution. You can have two types of licenses, one is user-based, and the other is app-based in the Power Platform. 

What other advice do I have?

I work as a senior consultant for Microsoft technology as a developer, mains power developer, but I would love to explore other options.

It's a genuine Microsoft product, which is the main reason I would recommend it to someone.

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

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
PeerSpot user
Buyer's Guide
Microsoft Power Automate
March 2025
Learn what your peers think about Microsoft Power Automate. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
844,944 professionals have used our research since 2012.
Co-Founder at Beta Edge Technology Limited
Real User
Integrates well with Microsoft products, includes pre-build templates that are easy to use, and the support is good
Pros and Cons
  • "The most valuable feature is that it easily integrates with other Microsoft products, so it has multiple connectors. You can create solutions that connect to Teams, Outlook, SharePoint, and OneDrive."
  • "There are some bugs or intermittent behavior in the Excel activities that require using workarounds."

What is our primary use case?

I am a solution provider and I implement RPA products and automate processes for my clients.

With this product, you create your workflows on the cloud. We've used this product for integrating with Microsoft solutions. For example, one of them is a document approval solution, where documents are sent to SharePoint and then pushed to different users within Active Directory for approval. This is done according to rules set by the client.

There is also a COVID application that was built around Power Automate and the Power Platform, where users within the organization can raise a request for a test and this would be pushed to managers for approval.

We are also looking at financial processes around bank reconciliations and interbank transfers.

What is most valuable?

The most valuable feature is that it easily integrates with other Microsoft products, so it has multiple connectors. You can create solutions that connect to Teams, Outlook, SharePoint, and OneDrive.

There are templates available for you to create your own flow, and it is easy to start creating a flow and automating a solution.

What needs improvement?

There are some bugs or intermittent behavior in the Excel activities that require using workarounds. For example, there is an Excel activity called Collect that fails once in a while. When you want to choose or select a particular cell, once in a while, it fails to do so. It doesn't happen all of the time and I don't know if it's a bug, but it's something that they can look into.

For how long have I used the solution?

I have been working with Microsoft Power Automate for approximately one year.

What do I think about the stability of the solution?

This is a very stable product.

What do I think about the scalability of the solution?

The scalability is amazing. This is a cloud-based resource, and there is no limitation in terms of scale or size. You can easily increase the scope of processes being handled.

The COVID use case is available for all of the employees, which is approximately 2,500. The documentation approval use case is used by managers and people making requests, which is approximately 2,000 people. The use case involving financial reconciliation is only for a small team that consists of about five people.

How are customer service and support?

The technical support is good. They are available and you can just call them. We have Microsoft Office online support, as well. This means that you can call them, or instead go to the forum and search for activities and resources. They have a lot of resources available online.

There are good tooltips available within the product itself. You can look at something and the tooltip will explain how it works and what you should do.

Overall, the support resources are good and I would rate the technical support a nine out of ten.

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

I also work with UiPath and WorkFusion.

How was the initial setup?

The initial setup is straightforward. Power Automate is a cloud-based tool, although I downloaded the Studio to my local machine.

The deployment takes one day. You just switch environments from UAT to production. You can easily export your solution and import it into the production environment.

What about the implementation team?

We were working with another company to implement the solution but we completed the implementation and deployment ourselves.

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

The licensing model is flexible in that you can pay per automation or per user. My client receives a discount because of the large number of users and pays approximately $15 for each one.

There are no costs in addition to the standard licensing fees unless other resources are being used. For example, Office resources are available on Azure, but that is a different product. It is related to Azure, rather than Power Automate.

Which other solutions did I evaluate?

Our client chose this solution. They already had Microsoft enterprise licenses, and they felt it was better to use a Microsoft product for their automation solution.

What other advice do I have?

Overall, this is a good solution and I like it. It's very scalable and easy to do so. Also, there are many connectors and they are quite useful. This is a product that I recommend.

My advice for anybody who is implementing Power Automate is to be cautious about how they distribute their flows, just to manage the licensing cost. Because it is cloud-based, it is an easy-to-use tool for both small and enterprise-wide solutions. There are no complications when integrating with Active Directory or the cloud platform, and this is good, in particular, because everybody is moving to the cloud. This product makes it easy to integrate things that people are already working with, such as Teams and Outlook.

I would rate this solution 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
Co-Founder & Director - Technology at a tech services company with 1-10 employees
Reseller
Execution of workflows could be improved; connectors are a good feature
Pros and Cons
  • "The connectors are a very good feature."
  • "Execution of workflows could be improved."

What is our primary use case?

This is one of the solutions we sell to our customers. I'm an automater and we are customers of Microsoft. 

What is most valuable?

The connectors are a very good feature in this solution because they allow you to connect to multiple applications within the Microsoft environment. The solution is readily integrated. 

What needs improvement?

I'd like to see an improvement in the execution of workflows, which is currently an area of concern. It takes a lot of time and when you integrate these workflows, you have to be very careful because even a tiny error can break the workflow. Microsoft needs to make it more resilient.

An additional feature should be interoperability. It's the idea that you should be able to leverage other Microsoft technologies, let's say .NET, C#, VB macros, so that they can be integrated. It will make the solution more powerful, and they could provide a facility where we could run scripts written in other languages through Power Automate seamlessly. That would make this a very powerful product. 

For how long have I used the solution?

I've been using this solution for 18 months. 

What do I think about the stability of the solution?

It's not stable yet, because it's still in development. There are a lot of things happening right now. If they bring in a new feature, an old feature can change and that's why we're not able to deploy it fully on all our client premises.

What do I think about the scalability of the solution?

It's scalable because almost everything which is available within the Microsoft environment can be connected. But when you go outside the Microsoft environment, with respect to legacy systems and with third-party applications, the scalability is a somewhat limited right now. You can't connect very easily to Oracle or SAP or even third-party standalone custom applications. We don't have plans to increase usage for the time being. 

How are customer service and technical support?

We haven't contacted technical support, mainly because we've been in a Microsoft related environment for the last 30 years. Most things that we solve ourselves, rather than talking to Microsoft.

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

We have not yet fully switched to Microsoft Power Automate. We still consider it an option for clients who are purely in a Microsoft environment. It's definitely an option, but we also have seven other RPA tools we use including UiPath, Automation Anywhere, Blue Prism, Kryon, Kofax. We also have an option for customers who don't want to go for any RPA tools that enables them to get custom automation.

How was the initial setup?

The initial setup is complex. You need to know what you are doing, because it connects to so many things on your system which could be different for different systems. It took us about half a day to understand what we needed to do, and then after that it took just an hour. We did it ourselves. 

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

The solution is affordable and supportable, but the licensing is complex because you're paying for multiple services. You pay a license for Automate and a license for Azure Cloud. There could be a situation where you're managing more licenses than the bots.

Which other solutions did I evaluate?

We have evaluated 22 options in this area. 

What other advice do I have?

Choosing a solution really depends on what the customer needs. If they're looking for something that's easy to maintain, we might go for UiPath or Automation Anywhere. And if we don't have the budget we tell them to look at Microsoft Power Automate. If you don't have a budget for that, then you look at a custom automation which doesn't need any RPA tool. It all depends on the customer's requirements and constraints.

This solution has the potential to go further, but for now I would rate it a five out of 10. 

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
Bryan Senter - PeerSpot reviewer
Strategic Alliance Manager, Public Sector at a tech services company with 5,001-10,000 employees
Real User
Poor scalability, expensive support, and has a lack of orchestration and supplemental tools
Pros and Cons
  • "It's easy to learn."
  • "The downside is the lack of orchestration and supplemental tools such as capturing existing processes and using them to build out."

What is our primary use case?

This solution is used for the automation of simple processes that are repetitive and very low on decision branching and error handling.

What is most valuable?

It's easy to learn.

What needs improvement?

The barrier to entry is low. The downside is the lack of orchestration and supplemental tools such as capturing existing processes and using them to build out.

For how long have I used the solution?

I worked on a demo side by side with UiPath Automation and Power Automate.

What do I think about the stability of the solution?

I didn't see any issues with the stability of Microsoft Power Automate.

What do I think about the scalability of the solution?

I would say that scalability is probably a weakness.

It's an area that needs improvement.

How are customer service and technical support?

If you have a good enough support plan, it's fantastic, but most businesses don't.

When I was working at a customer site that was a premier customer, we had onsite Microsoft service providers, and we were able to leverage their worldwide support. At that point, you can have round the clock, follow the sun support on a critical problem. 

But in 35 years of working with Microsoft, I've only seen one customer site that had that level of support. If you don't have that level of support then you are basically on your own.

How was the initial setup?

The setup for me was almost non-existent because we already had Office 365. 

When it comes to the admin side of that, I don't know.

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

The price is right. If you have Office 365, it's included.

What other advice do I have?

If you're looking for entry-level, inexpensive, and you're already an O365 customer, then this might be a consideration. But if you're looking for an enterprise tool, you should probably keep looking.

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

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
reviewer1225296 - PeerSpot reviewer
Practice Principal - Cloud and Automation at a tech services company with 51-200 employees
Real User
Integrates well with other Microsoft products but there are many features lacking and it is not scalable
Pros and Cons
  • "The integrations that are built into Power Automate for those different Microsoft functions are good."
  • "When compared to other workflow automation tools out there, it's just not as mature."

What is our primary use case?

Internally, we're doing a lot of workflow automation. This includes creating documents inside of SharePoint, updating SharePoint lists, taking templates in Microsoft Word, and then pulling data from SharePoint to populate different fields in the Word doc using the approval workflows.

When somebody is done reviewing a document, they click a button, and then it goes to the next person in the workflow. It sends me emails, sends notifications, posting from an email, stripping out all of the extra content in the text message, manipulating it, and then posting it to Microsoft teams, channels.

What is most valuable?

The most valuable feature of this solution is the native integrations with other Microsoft products. These include SharePoint, Office 365, and Microsoft Teams. 

The integrations that are built into Power Automate for those different Microsoft functions are good.

What needs improvement?

This solution has many areas that have room for improvement.

There are many features that are lacking compared to other Automation tools.

There is an inability to group different variables. When you have to establish all of your variables, you can't group them all.

The notifications when there are failures need improvement, as well as being able to start a process midstream.

The licensing is convoluted in understanding what license is needed.

There's just not enough error handling natively, so you have to build in a lot of workarounds for error handling. 

When compared to other workflow automation tools out there, it's just not as mature.

For how long have I used the solution?

I have been using Power Automate for one year.

We are using the latest version, it's a cloud solution.

What do I think about the stability of the solution?

For the most part, it is pretty stable. We made one change that created a licensing error just out of the blue that stopped all of the processes that were in progress.

It created a problem, where we had to restart all of them and do a lot of manual cleanups, and backtrack to the ones that were canceled.

If there's a licensing issue, there should be some notification versus saying, "your licenses are out of compliance," and shutting down that process. When we checked the licenses, there was no issue.

I don't know if it was a bug or what that was, but that happened one time. Luckily it was when we started the rollout, and we didn't have as many processes in flight.

If we had hundreds of different processes in flight and that canceled my flow, that would not be acceptable for a production-type solution.

What do I think about the scalability of the solution?

It's not scalable.

For some of the processes that we're building right now, we are asked to add a button for this additional piece, and it adds so much more complexity with the way that I have to build it out. It doesn't allow me to break up a process into multiple processes, and then call sub-processes, which would make it a lot easier to scale. When I break up these different processes, I have to redefine every variable. 

I can't take information from one process and then pass those variables to the next process.

Your workflow then becomes this very long, single process, that can't be started from the middle. It has to be long and convoluted, and it doesn't make it simple to scale and have sub-processes to make it more complex.

Currently, we are limiting the number of additional features and functionality. 

We don't want to add to it because it adds complexity and doesn't give us the ability to call a sub-process.

How are customer service and technical support?

The couple of times that we have called, they haven't been able to solve anything.

In many cases, we try to figure it out ourselves or rebuild the workflow, if we can't reproduce the issue. 

How was the initial setup?

The initial setup is pretty straightforward.

We built out the workflow, completed the testing, the user testing, and completed a production rollout. 

I would say part of the challenges was with the production rollout. The tool is not as easy to work with because it's a hundred percent cloud-based.

A lot of the error handling and some of the things you would normally have aren't built-in, and so we ended up finding a lot of bugs and issues and things after the fact.

For example, it was set up where we needed to send an email, and if you put the two email addresses, but you don't put a semicolon between it, then it was just killing the process, saying, "that it couldn't send the email," so it just failed. The entire process failed.

It didn't send a notification and we had to find out two days later.

Those are the types of things where it just needs to have better handling for those types of situations to be able to say, "this is an error that happened," or let me kick off that same process from that point, and then restart the process from there; whereas, right now I have to restart the entire process.

All the steps that happened before, need to be able to go manually and clean up. It eliminates the point of automation.

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

The price depends on the features that we are using.

The licensing cost for us at this time is between $8 and $20 per user, per month.

It's a monthly cost for every user that touches one of the flows or is kicking off a workflow.

Licensing can get expensive.

There are premium connectors, where if you want to connect to external data sources, there is an additional cost for that.

I think one of the big issues was for an Azure SQL database or for SQL databases that used to be part of the standard connectors, and then they converted those to premium connectors, which increases the cost and limits the functionality for what you would be paying for it.

What other advice do I have?

Use it for basic workflows, but I wouldn't recommend it for anything that is mission-critical. I don't think that it is ready for mission-critical type processing. 

It's a good product. They just have a lot of functionality they need to add.

People have posted on their feature request board, and on their community board.

The vast population that is using it asks for the same features. They are either very slow to implement those features or they are not interested.

I would rate this solution a six out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
AsfandyarKhan - PeerSpot reviewer
Process Automation Engineer at Automation Catalyst
Consultant
Top 20
Easy to set up, but its AI features for data and process mining need improvement
Pros and Cons
  • "It works best to build cloud flows."
  • "It is challenging to scale the solution across multiple branches."

What is our primary use case?

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

What is most valuable?

The solution's most valuable feature is cloud flows.

What needs improvement?

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

For how long have I used the solution?

We have been using the solution for a year.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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

How are customer service and support?

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

How would you rate customer service and support?

Neutral

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

We use our in-house software as well.

How was the initial setup?

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

Which other solutions did I evaluate?

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

What other advice do I have?

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

I rate Microsoft Power Automate seven out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
IT consultant at Secoptrial
Real User
Helps to process documents without spending much time on them
Pros and Cons
  • "From my personal experience of using Microsoft Power Automate, I think that the automatic document processing feature is helpful for many organizations in streamlining administrative processes. It is a very good feature. It has helped many enterprises to process documents without spending much time on them."
  • "I would recommend removing the AI Builder feature from the automatic document processing functionality. The tool can serve even better with free automatic document processing features, it shouldn’t only be available in the trial version."

What is our primary use case?

The primary use case for this solution includes automating process work with optical character recognition. Companies can also automate document processing with Microsoft Power Automate.

How has it helped my organization?

From my personal experience of using Microsoft Power Automate, I think that the automatic document processing feature is helpful for many organizations in streamlining administrative processes. It is a very good feature. It has helped many enterprises to process documents without spending much time on them.

What needs improvement?

I would recommend removing the AI Builder feature from the automatic document processing functionality. The tool can serve even better with free automatic document processing features, it shouldn’t only be available in the trial version.

For how long have I used the solution?

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

What do I think about the stability of the solution?

I have found Microsoft Power Automate to be a stable solution.

What do I think about the scalability of the solution?

It is a scalable solution but I also think that the scalability of this solution depends on the type of organizations that are using it. For instance, public enterprises like government organizations can make very good use of this solution. I plan to propose the tool to my organization. It’s still in the loading phase and I have not got any feedback on it.

How are customer service and support?

I have not felt the need to contact the customer service and support team since most of my doubts were resolved through the tutorials and tech instructions available on the website, which are very helpful.

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

I have previously used Power BI. I came across Power Automate while looking for other Power platforms. I saw the different features that Power Automate offers and so I chose it.

How was the initial setup?

It was easy to set up. Once you have access to the portal, navigate to the automatic document processing feature where you can see many examples. There are a total of just two or three steps that you need to follow for completing the entire setup process.

The setup took a couple of months. It requires much concentration like when you are training your model to analyze the documents. For example, when you are setting up the automatic process document, the tool will ask you to try with five documents. Also, we will have to look into the different fields from which we are going to extract the information from the documents.

Once the document upload is done and the training is finished, you will need to locate the locations where other documents are located. It’s recommended to use either the OneDrive or Sharepoint locations. Power Automate will locate the schema of the document, connect with it and the document upload will be done. When the upload is done, the AI Builder will apply the OCR. After the completion of the OCR, the information will be extracted and put on other documents like Excel. 

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

I am not sure about the setup cost, pricing or licensing since I use the trial version.

What other advice do I have?

I would rate this tool a nine out of ten. 

Which deployment model are you using for this solution?

Hybrid Cloud
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: March 2025
Buyer's Guide
Download our free Microsoft Power Automate Report and get advice and tips from experienced pros sharing their opinions.