Microsoft Power Automate Reviews and Ratings

Use Cases and Deployment Scope

Mostly as the name suggests Power Automate helped me manage my clients tasks by automating them. One such scenario of i define would be automating a email and message trigger if a report takes longer than usual to refresh. Automate helped me creates those scenarios woth least coding and best results with all process working seamlessly automatically as programmed.

Likelihood to Recommend

Highly recommend service to whosoever is willing to automate tasks with least amount of coding required and easy creation through drag and drop services. Since it is a Microsoft product it not only provides security but also provides number of integrations with vast available connectors. It can be suited for beginners as well.

Use Cases and Deployment Scope

Microsoft Power Automate had been used in the integration of our Survey feedback into Ms Teams. where users now directly receive the survey as workflows in Ms Teams

Likelihood to Recommend

Microsoft Power Automate is highly suited in all organizations because there is little use of codes with provides easy understanding for users without background in codes to easily automate.

Use Cases and Deployment Scope

I use Microsoft Power Automate to automate some data task. An example for this is to automate storing of CSV and JSON files to database that is sent via email. Another is to use this in sending email or notification to our end users. And lastly is sending of Power BI report in form of PDF with different applied filters per recipient. This really helps a lot and powerful to manage basic data automation.

Likelihood to Recommend

Microsoft Power Automate is best suited for automating basic task that is in Microsoft D365 ecosystem. Like auto-response to email, creating automation when there is a new file is sharepoint page, storing email attachment to certain repository, accessing and storing REST API endpoint and more. A lot of potential with this tool. We have a analytics solutions that is fully powered by this tool.

Use Cases and Deployment Scope

We use Microsoft Power Automate to automate some processes wich require data transfer from one application to another. This automation saves us time and improves the quality, because there are no errors made in the data transfer. We mainly use Microsoft Power Automate to automate processes between webapps, although we also use Microsoft Power Automate Desktop for one process with an on-premise app.

Likelihood to Recommend

Microsoft Power Automate works well if you want to process much within the Microsoft architecture.Within this architecture there's a lot possible within the Microsoft Apps. When you are looking for an automation on desktop apps or with third parties, Microsoft Power Automate is less suited. There are a lot of integrations possible, but there are also quite a lot of integrations missing, that's a pity.

Use Cases and Deployment Scope

We thought Microsoft Power Automate would meet our needs for workflow automation. We manage a large project for our client with about 1,500 projects we have to track from start to finish in a 12-month cycle. our SharePoint tracker has over 100 fields. We wanted to use Microsoft Power Automate to monitor the tracker and start workflows when dates were added to certain fields. Think review and approval before the project goes to the next step. Our team is in the sharepoint list every day making updates. Our experience was that Microsoft Power Automate failed us. It would often throttle the workflows and when someone was supposed to get an email to review something it would be delayed.

Likelihood to Recommend

In my experience, it's well suited for a list with few fields and few rows. Not good for our team with 1,500 rows and 100 fields of data. We switched to Nintex as they were able to not have the throttling issue. In my opinion, throttling is a deal killer for Microsoft Power Automate. I think if you cannot do work flow real time it's not worth the effort to use Microsoft Power Automate.

Use Cases and Deployment Scope

To automate manual processes within my company. Many processes involve a Word document form or Excel spreadsheet. By using Power Automate, we can streamline the processes by creating MS forms and SharePoint lists with responses automatically populating for us by Power Automate. The service also allows us to send email reminders for some processes.

Likelihood to Recommend

Our end goal is to automate processes as much as possible. Using Power Admin, we can automate where our data goes, where it is read from, and how our data is inputted/outputted. Power Admin has lots of connectors that help us, e.g., read and populate from/to file shares.

Use Cases and Deployment Scope

Power Automate fills a vital gap where teams can develop various workflows between systems that our technology team hasn't integrated, and we need automation. This is most useful with HR and L&D processes such as onboarding, induction, and employee exit. It helps us automate repetitive tasks, like updating a database of employee records, sending data to webhooks based on a set trigger, moving data from one system to another, and automating enrolment actions in our LEARN365, our LMS platform. Power Automate stands out for its ability to integrate with multiple systems, close gaps in our existing technology configuration, and give more flexibility to people's data.

Likelihood to Recommend

If you are in a team that needs to develop automated solutions but have no coding experience and no access to a developer, Power Automate is one of the best places to start. It is incredibly flexible and likely has triggers and actions that can connect with your platforms, especially if you use the Microsoft stack. Additionally, using webhooks, you can connect to many different endpoints to get systems working together.

Use Cases and Deployment Scope

We use Power Automate to build workflows and business process management-based processes. We have categorized development into two models: the Citizen development model and the IT Pro model. Citizen developers can only create Automated cloud flows, Instant cloud flows, and Scheduled cloud flows and can only use standard connectors, whereas IT Pro developers can use standard flows, desktop flows, and premium connectors.

Likelihood to Recommend

We replaced all the classic SharePoint and Nintex-based workflows with Power Automate. This saved extra licensing costs and getaways from managing legacy workflows. Power Automate Designer is very user-friendly and requires no additional learning curve. We also use it to replace RPA solutions created with other platforms using the Power Automate Desktop application.

Use Cases and Deployment Scope

We use Power Automate to join different business systems together which otherwise wouldn't have worked together. For example, when we receive emails from certain parties, we're able to notify the entire team via our chat software, with attachments automically saved to our data storage.

Likelihood to Recommend

<div>We've found it works brilliantly when the trigger is an email received. The actions that can flow from that trigger are numerous.</div><div>

</div><div>Additionally, we have timed automations for regular actions which are reliable and ensure nothing is missed.

</div>

Use Cases and Deployment Scope

We utilize a custom SharePoint list and Power App form for system and network Change Requests, and we use Microsoft Power Automate to track requests and approvals.

We also use Microsoft Power Automate to copy data between systems to keep data matching and up to date.

We also have a corporate Thank You system, that allows anyone to "submit" a Thank You or kudos to others in the company for a job well done.

Likelihood to Recommend

Approval workflows are a no-brainer. The notifications to Teams or email are easy to set up. And the built-in approval buttons within an email make responding simple.

Really, the workflow engine is very powerful. As long as you can logically define and map out the process, Microsoft Power Automate can help.

Troubleshooting a flow when building it isn't always the simplest, but I will say it has gotten better over time.