What is your primary use case for Microsoft Power Automate?

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.

We use the solution in insurance and pharma.

The uses cases are fairly basic for my clients in the IT industry.

Microsoft Power Automate has helped one of my clients to update a SharePoint list automatically. There was no need to open the SharePoint list every time and update it. Instead, a flow that runs and updates it.

We use the product to automate tasks and reduce manual work in our organization. It helps set up a workflow to send a daily email reminder at a specific time, eliminating the need for manual intervention and ensuring timely reminders. It integrates Outlook as well.

I use the product for automation.

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.

We can automate cloud flows using the product. We can use desktop flows in the product as an RPA tool. If we are working on any enterprise application like SAP, we can automate it using the tool. Power Automate Desktop is a relatively newer solution compared to UiPath.

I have different use cases for Microsoft Power Automate. I was automating one of the refund processes in my previous company. This involved getting data from an Excel spreadsheet and iterating all its entries. For each entry, the solution checked a particular website to verify values and released payments to the client if everything was okay. This eliminated the need for me to perform the same task repeatedly.

We help clients integrate Power Automate into their processes.

We are using Microsoft Power Automate for RPA.

Microsoft Power Automate is deployed in the Azure cloud. Microsoft has a version of Power Automate Desktop to develop desktop flows and that's also saved in the cloud. We use Microsoft Power Automate on the project site. We have done a few projects on the site and the solution is used for video processing automation.

The 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.

We use Power Automate to build applications for businesses uses such as workflow applications and process applications. We copy the data or get the data from other systems and use Power Automate to do some lightweight RPA tasks. The Power platform has several features and Power Automate has two features. One is Flow and the other is UI Flow. Flow is used for workflow automation and UI Flow is the RPA solution.

We use Power Automate to build applications for business users. Examples of this are workflow applications and business process applications. Sometimes, we need to copy data or get data from other systems and we try to use Power Automate to do some lightweight RPA work.

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.

I use Microsoft Power Automate as part of my job as an RPA developer. The solution is part of everyone's Office 365 account at our organization. The solution is used as a primary tool for providing RPA solutions. We've created an automated desktop flow for the whole process. It includes three platforms. We use the solution as an extension of Power Apps. We create files and SharePoint using flow by converting HTML code into PDF.

I'm using Microsoft Power Automate to automate some of my processes. Before using this solution it took me sometimes one day to complete tasks and now I can perform them much faster.

We are using it for automating legacy systems as well as email verifications. I haven't touched on the APIs yet, but the use case is for user accessibility to and from data sources.

We use Microsoft Power Automate to automate everything, such as mailing, gathering data from a web scraping, and scheduling time.

I use both the on-premise version and web versions because they both have different tools. I use them both for different use cases and different scenarios. I use Microsoft Power Automate to make reports and web scraping. I automate the reports with the desktop version because it works well. I use Microsoft Windows, to do some commands in the CMD, also known as the line assistant. When it comes to the web version, I mostly do reminders, scraping, extracting data from emails, and creating ticket systems. I take that data and put it in a list or create a table in Excel to extract information and automate that part.

Our 1st use is automating large amounts of report-data collection from various sites where Power BI doesn’t have a connector. This data is automatically sent to a SharePoint list that updates our Power BI reports daily.

It’s cutting our reporting times from once a month to once a day.

See my tutorial on this: 

https://youtu.be/ONl7B9-9lPU

The use cases include Power Apps and Power Automate. We have had use cases for scheduling meetings. We have also used it for HR onboarding solutions where document verification was done by using Power Apps and Power Automate. I have sold both cloud-based and on-premises solutions.

It is currently being used by our customer service department. They're using it for tracking overtime, and they're also using it for reporting and automating their various service quality reports. So, automation of service quality reports and overtime management are basically two major use cases.

We use it for processing a stream of incoming invoices. It is a cloud solution, but you install the client on your computer, so it is a hybrid deployment.

We held a hiring event specifically for veterans. All the people who were registering were external to our organization, so we had them fill out a Microsoft form, which then triggered an email, took all their information, and stored it into a SharePoint list. This list fed a Power App, and we were able to: * Check members in whenever they arrived. * Capture extra details about them. * Pass the information onto hiring managers whenever a hiring manager was interested in an individual applicant or somebody who showed up. In another use case, we used it to track the vaccination status of all employees. There were about 90,000 employees. If they scheduled it, it would trigger reminders whenever an employee's vaccination was coming up.

I use it for robotic process automation.

The solution can be primarily used small process automation of day-to-day activities, such as routing of emails, Excel sheet manipulation, and more.

In our organization, the solution is popular where there is a need for attended automation or user. That "human in the loop," as we call it. There it is more popular than the other tools.

We use the solution as a business process automation tool. It allows one to automate an application in his organization.

Our use cases are everything from replacing Excel macros to replacing WINAutomate to larger initiatives to use RPAbox to fill in different back-office systems and so on. We have a huge range of solutions.

We implemented this solution for our clients and the primary aim was to create a chatbot that would provide service answers to customers. If the chatbot wasn't able to help, the query moved to a ticketing tool like ServiceNow, which creates the ticket and assigns it to the appropriate team. For logging purposes, the ticket is logged with ServiceNow and it provides the solution to the end-user through the chatbot. I'm a senior manager and we are Microsoft gold partners.

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

We have the latest version installed.

We primarily use the product for credit card operation customer complaints.

The most common use is for digitizing Excel forms or Excel spreadsheets. We use Power Automate to digitalize all Excel-based processes on a SharePoint page and link the libraries with the transactional data from the client. It is cloud-based. It can be deployed on a public, private, or hybrid cloud. It depends on the client. It is linked with the Microsoft license that a client has. If the license is hybrid, then Automate is hybrid as well.

We are system integrators so we provide this solution and deal with the automation for our clients. Power Automate is mainly suitable for small and medium size companies.

We have been using Power Automate specifically for the COVID situation. The use case is mainly to automatically fire an e-mail every Monday morning requesting the employees of our firm to provide a response regarding their well-being. After the data is captured by using an MS form, the subsequent workflows get triggered through Power Automate. If somebody has mentioned that they have a fever or shortness of breath, we send this person's entry to our health and safety officer and our plan manager. All this is automated. We also have another use case related to procurement where an automated flow was required for invoice processing for an external vendor.

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.

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).

I'm using it for internal purposes at the moment. We are a consulting company and we are exploring goals with the option of implementing automation for our clients. Currently, I am assessing Microsoft Power Automate, comparing it with UiPath to see if it's good enough for our clients and for our purpose. We plan to use this solution for getting information from one application to another, for producing sheets and text files for Power BI, and also for integration and displaying dashboards and business intelligence for the business. It will also be used for invoicing and notifications — mainly business processes in general.

We are using Power Automate to send notifications when working with items in SharePoint. It is used to send notifications when a document is moved or needs to be approved. When a document needs to be approved in SharePoint, we send a notification to the user who needs to approve that document. I also use Power Automate to create a work item in another system, such as Azure DevOps.

It's a pretty big learning curve with Microsoft Power Automate and I'm trying to do a couple of other things. But I really have made some progress. I've actually started creating some bots. I've run into some snags. I haven't found my way out of the snags as yet. That's kind of why I'm not quite ready to publish because I'm not an expert yet, but I am actively working on it. Microsoft Power Automate is on-premises because I'm using the Power Automate Desktop. So it's a desktop piece that I'm actually using and that's definitely on-premise. What I'm actually doing is interacting with actual systems. I run a clubby cloud system for moving data back and forth. There are some very long processes that are happening now, where we need to move data from one system to another and do some analysis, and all of that. We're trying to automate some of that process to link the systems together. So some of it is actually reading the webpage, taking information off of the webpage, and doing things with it.

We are using it for simple invoice management processing. We are using it for just storing documents with some workflows attached.

We use it for automating our business processes. We are using it for sending reminders and these sorts of things. Every Excel update also happens through Power Automate. It is still under the review stage. We are not using it in production. Currently, we are waiting until the product is completely stabilized. We are expecting it to happen by September 2021. We are using its latest version. It can be deployed on the cloud and on-premises.

Power Automate is a quite powerful tool. It helps you automate your daily processes. Being an RPA tool, it allows you to define certain logic and execute certain tasks at a scheduled time or for a certain event. I use it in conjunction with our SharePoint site to let our stakeholders know that something has been done or updated, and it kicks off another flow. We use it quite regularly.

We are resellers and sometimes we implement solutions. It's a component of Microsoft 365. We use this solution to match some documents or spreadsheets, to match data from one spreadsheet with another, and to download and load invoices. We also use it for an approval flow.

I use the solution to not only automate processes but also to be an intermediary or a glue among the applications of Azure in the Microsoft universe.

We used it internally to automate certain workflows for our daily business and validate our commercial proposal. We used its latest version.

We're currently exploring the solution. We're doing some planning and testing. We're looking at data transformation and flows.

We primarily use the solution for automation purposes. It can offer an alternative desktop option, and therefore it can automate a lot of stuff. It's part of the application. It also can connect us to a number of data sources and that helps us a lot. However, it's difficult to get into specifics due to client privacy.

I primarily use the solution for automation. I also use it for invoicing.

We use Microsoft Power Automate for various personal initiatives of people to automate their own work. It is used in a laboratory environment to connect the laboratory systems and to automate the connections between them.

Currently, we are in an active search with a provider for on-premise, and therefore we use it to automate our process of moving our permits to electric housing and preparations.

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.

We carried out a successful POC on Power Automate Desktop. It was right after they launched and we were the first to demo it. We used it in a project for one of our clients. We used the desktop version but it's stored in Power Automate cloud. The solution is used for banking processes such as credit and debit transactions. We are partners with Microsoft and I'm the CTO.

We use it to monitor the net flow of all the emails. It is really helpful.

I'm a strategy consultant and we are partners and resellers/integrators of Microsoft.

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.

I was using this product to create a basic workflow and trying to integrate it with Outlook. We use it along with Microsoft Power Apps to help identify and automate tasks. We have many tasks in Outlook, SharePoint, Calendar, and Teams, and we use Apps to manage the tasks. We are also using a feature in Microsoft Power Apps, which is the productivity backup

We are using it for approvals and flow history. We are using the latest version.

We have clients in a number of different industries. We were evaluating Power Automate for a hospital in Kansas City. We were looking at a couple of different use cases with regards to their vendor onboarding and some of the back-office processes.

We use SharePoint to collect information from tests, exams, and similar things that we do in our office. When people complete the tests, we use Microsoft Power Automate to collect the results and email them to appropriate people. We are currently using the latest version of Microsoft Power Automate.

Microsoft Power Automate is a part of the Office 365 environment. Currently, 5% to 7% of our 19,000 employees use Microsoft Power Automate. It has already been connected to all the applications that our employees use, such as Outlook, SharePoint, OneDrive, and the ecosystem of applications that come with Microsoft Office. This is one of the primary reasons for using this solution. We are also using it for workflow approval and automated signature use cases to deploy a digital signature solution for some documents. It is all automated, from the client all the way to signing and storing the documents.

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

The use cases for the solution would be banking related, typically, and specifically surrounding BFS, Banking Financial Services.

We primarily use the solution for testing. For example, we made a website solution and we're open to trying new things because it's not on production yet. We use your flows in order to make some data automation. We fill our flows with some data and test to see if it's all correct.

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.

We are being forced to look at Power Automate as our clients are using it and asking for us to extend the footprint of automation in their business's. We were pretty happy with our primary RPA offering but when Microsoft gets involved you have to listen.

Our primary use case is the automation of tasks.

Our primary use for this product is actually for a variety of reasons in conjunction with a few different products. We use it mostly for our accounting and invoicing purposes.

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.