Microsoft Power Automate Reviews

We use Power Automate for applicant tracking. We automated around 80 percent of the process. 

Power Automate's out-of-the-box integration is nice. 

Microsoft could offer more AI education and training.

I have used Power Automate for a few years.

I rate Power Automate seven out of 10 for stability. 

I rate Power Automate seven out of 10 for scalability.

I rate Power Automate eight out of 10 for ease of setup. We did it in-house.

I rate Microsoft Power Automate four out of 10 for affordability. It's a little more expensive than average.

I rate Microsoft Power Automate six out of 10 overall. It has a lot of integration capabilities out of the box, but it isn't always accurate. 

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.

We started using it just three months ago. These three months also include doing the proof of concept. We use it for IT operations where users can request for a software push by using a Microsoft Office 365 form. Using Forward Automate, I initiate the process. I have another department that is using it for requests for the PC team or for a contractor's visit to the main plant here in Panama.

It is basically free for me because it comes with my Office 365 subscription. The main feature is that there is abundant learning material on platforms like YouTube. You can find information about whatever you want to be done in Spanish or English without a problem. 

It is very easy to learn. Users can start using it on their own without any former training, which is something I like about this solution. 

It would be good to have some kind of on-premises solution for BPMN users, but I don't think Microsoft will ever go back to the on-premises solution. They all train their clients to use their online services.

It is easy, but it doesn't follow the industry-wide standards. I can only use the processes that Microsoft gives us. I can't map a business process by using other standards or notations, such as Business Process Management (BPM). I have to use whatever Microsoft gives us. I would like to have support for some standards because if we decide to use another BPM tomorrow, we will have to remap everything in notation to transfer from this solution. This is the only block or obstacle that I see in using this solution. It is closed in its infrastructure.

I have been using Microsoft Power Automate for three months.

I can't evaluate their technical support because I haven't had any issues. We have an enterprise license and subscription from Microsoft, which gives us 24/7 support in case we have any problem with the solution.

The most complex thing was setting up Microsoft Exchange Online. Our email solution was Google G Suite Email. Switching over to Microsoft was very difficult, and it took at least one week. We are a small company. We did everything in one day, but we had issues for at least one week after the migration because we transferred all mailboxes from Google to Microsoft. 

It is free with Office 365 subscription.

We have just started to use this solution. The next step is to have a dashboard to polish the KPIs from the data stored through this application.

I would suggest using this solution if you don't have any budget restrictions for automating processes. If you are a subscriber of Microsoft and you use Microsoft Office 365, I will advise using it right away. If you have a budget and you want a solution that designs specifically for business profits, I will suggest implementing some other solution such as the one from Pega systems.

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

More scripting capabilities could be included in Microsoft Power Automate.

The product could be more stable. I rate the stability as seven out of ten.

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

There needs to be direct contact for the technical support team. The users need to submit a maintenance request and then wait for a callback or update from the support team.

Neutral

The initial setup process was relatively simple, with additional modules that could be imported during the setup.

Only some individuals typically handle maintenance, as Microsoft automatically manages most updates. Additional maintenance tasks are required only when necessary, such as for critical updates or multi-case scenarios.

The platform is averagely priced. I rate the pricing a five out of ten.

I have used Microsoft Power Automate to develop mobile apps and other applications. Additionally, we have implemented workflows and automated solutions for various processes.

It helps with the feedback mechanism, where we need to determine the relevant team and obtain their email addresses.

Microsoft could enhance the learning experience by offering more video resources.

I rate it a nine out of ten.

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.

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.

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.

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

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

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.

I also work with Power Apps.

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.

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. 

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.

We use this solution to automate small parts of procedures in our workflows. Particularly, linking when emails are received, as well as picking out documents and loading them into SharePoint folders. From there, it feeds things like Power BI dashboards.

In general, they are specific things that we automate in order to reduce manual tasks. We have not applied it to any sort of more sophisticate process, like an approval process, or a supplier engagement process.

Implementing Microsoft Power Automate has made our development team more efficient. They are the ones who tend to have used it and applied it to help automate micro-tasks. It has made their life easier. We have not deployed it beyond our development teams.

The most valuable feature is that it is pretty low-code, so you don't need much coding expertise to use it.

I like that Power Automate is bundled with Office 365 and that it integrates with it pretty well.

The user access level and user account part of this product needs to be developed.  For example, if I'm a line manager and I have multiple approvals that are automated then I can't log into a dashboard and see all of my requests. I would like to have a user account so that the staff can see all of their requests, including the status and other details for each one, on the dashboard.

This solution does not work well with external people who are outside of the organization, like suppliers. It needs support for external email addresses. It would be difficult to do a supplier onboarding with Power Automate, whereas you could do it with Nintex, and this is a big drawback.

I would like to be able to set security and permissions on who can see request-specific details.

I have been using Microsoft Power Automate for less than six months.

In terms of stability, I think that it is going to be fine. We use Power Automate on a daily basis.

I think scalability is kind of limited by its features. If you're doing lots of little bits and pieces then it's fine. However, if you want to scale it to engage external suppliers or vendors then you can't really do that.

The security aspects and lack of user accounts in the interface are challenges for scalability. For what it can do is fine, but if you want to scale out across a business then I think it will struggle to have that breadth of features that enable you to scale it properly.

We have fewer than ten people who use Power Automate in the company, and they are all SAP HANA developers.

I have not been in touch with technical support.

We use Nintex, which does the same thing, but better. We have not switches solutions. We are dabbling with Power Automate to see if it can do a better job, or alternatively, be a cheaper solution for the really simple stuff.

The initial setup was very simple. The deployment probably took about half an hour. It isn't deployed as much as you pick a process and automate it.

We did not have a deployment team for this particular tool. Rather, we have business users who just picked it up themselves. They were SAP HANA developers to start with, so they were predisposed to knowing about this technology and having some kind of technology skills.

The number of people required for maintenance depends on how widely you've deployed it. In our case, it is self-maintained because people have automated their own workflows and they just tweak them as they need to. If you have a widespread deployment then it would depend on how many processes were changing that needed to be updated. It really depends on the situation. In general, it is not difficult to maintain, but it does require maintenance.

This solution is bundled with our Office 365, so there is no additional licensing fee.

We did not evaluate other options before using Power Automate.

We suspect that Microsoft is going to invest pretty heavily in this area. It might be strategic to start using Power Automate now because I suspect it will develop a lot of features over the next few years.

The suitability of this solution depends on how complex the processes are. My advice to anybody who is considering Power Automate is to make sure that it has the capabilities to support that, particularly versus a more established player like Nintex or AgilePoint.

I would rate this solution a six out of ten.

We help clients integrate Power Automate into their processes. 

The solution is great for attended or unattended bots. It makes work easier. 

Most clients that use Office 365 find it very easy to use this solution. There are lots of great integration points. It can connect with various Mircosoft products, like Microsoft Dynamics ERP.

It allows clients to existing in one main environment, which is quite useful. 

The setup is very easy.

We use the connector to the cloud, and we have noted that sometimes there are delays. We've seen some scenarios hang. Sometimes there are issues with security policies within the company. Some parts get blacked. There are some drawbacks when we use it connected to the cloud. We need to convince clients to open some parts. This is often an issue that originates from the company itself, not Power Automate. 

Sometimes when we work with Microsoft Excel, the process is not much faster. The automation doesn't speed up as much as we would hope as they go through cells one by one. If it is a time-sensitive activity, that might be an issue and should be improved. 

I've been using the solution for two years. 

It is a stable solution. I'd rate the stability seven out of ten. The issue is that there are some security policies from the company side, or sometimes some updates that happen that can slow things down or stop the process altogether. 

The solution can scale well. I'd rate it seven out of ten. If a product is on a particular machine, if we want to scale up, we need to use another machine or account. 

The product can work for any type of company, from small to large. 

We've contacted technical support in the past, and it has been very good. We haven't had any issues with support and are happy with the level of service. 

I also use UiPath as well. We use either or, depending on the client or the requirement.

The main difference is the price. Microsoft is cheaper than UiPath.

The AI capabilities for Microsoft are very good. With UiPath, sometimes you even have to use modules from Microsoft. 

The initial setup is very simple. It is simple. It's similar to other tools.

We can help implement the solution for clients. 

The pricing is reasonable. I'd rate the affordability eight out of ten.

I'd rate the solution eight out of ten. We've been pretty happy with its capabilities. 

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.