The one that we currently have is only to SharePoint Online as we want to be able to have analysts be able to maintain data, and we want a graphical user interface, a GUI front end, to do that. Especially if it's interfaced with PowerBI, it allows analysts to have a research tool to identify what data needs to be updated right there, and to then be able to do that through PowerApps is a huge benefit. Right now, we're only able to write back to SharePoint Online.

The solution is used internally in my company.

Power Automate is like process automation.

Any task which you do on a recurring basis or a daily basis, you can simply automate. For example, if you have a use case where every day when you go home you need to book a cab. What I can do is I can automate that task through Power Apps at a scheduled time every day. If I'm leaving at about four o'clock in the evening, by 3:30 I can run that Power task and book a cab every day.

We use the solution to integrate with enterprise solutions like SAP and other enterprise solutions. It's highly integrated and highly secured. 

We use Microsoft PowerApps for internal business solutions that eliminate the need for Excel workbooks.

Power Apps is a tool to create forms and solutions for collecting information from the floor. We have 10 or 15 users at the moment, but we expect to add more.

Right now, our primary use case is very easy to explain. I push applications for applications and supply applications on mobiles because a lot of my customers need to have to access certain data from an iPad or iPhone.

We use the solution to create applications. We were getting ideas, fine-tuning, and putting them in different queues that are available to the whole organization.

I'm working for a company that provides services and develops projects for our clients. I am a solution architect and I use Microsoft PowerApps.

We primarily use the solution as a general business process improvement. We use it as more of a digital transformation to eliminate some archaic manual processes that the business has built up over time. We're working to make everything more streamlined.

We are a big global company that is involved in a large volume of setups involving Microsoft solutions like Power Apps, Power BI, and Power Automate for different environments across departments in organizations functioning at a global level. So we are involved in delivering services while focusing on the setup processes for different environments and departments. It helps the people at work since solutions like Power Apps and Power Automate function excellently.

We had a new requirement from a business in the clinical domain and the business wanted to identify risk at a study or site level. We created an application using PowerApps, which works well as we usually interact with the SQL Server on Azure.

With Power Apps, we create some of the collaboration forms for our employees to use during the pandemic. We can record our employees' status health daily, and start a database of the information. After that, we can track using Power BI if there are any symptoms or if the risk is low, high, or medium. We use it basically for self-declaration forms.

We have built a couple of apps ourselves, but mainly, we are building the apps for our customers.

We predominantly use the product for a lot of intake forms. There is a lot of data collection and a lot of intake forms. We use Power Application for validation rather than using spreadsheets. It's good for automation, where we need a data repository of the input, which we get from the resource.

I use the solution to build customized platforms for clients and provide data-driven, focused statistics on threat attacks. I collect data and import it into Power Platform or Power BI to generate statistics. My clients use that information to apply new methodologies for implementing security in their environment. 

The solution is for rapid application development software.

There is a specific environment, in part a platform of PowerApps, in which you can just deploy the solutions and then you share the link with the users and they are able to open them using iPads or mobile devices, or even a computer.

We have been working to build a maintenance events app for assets, it's an app to manage and show all the assets that have been working or down for maintenance in an operation, inside one bigger mining company. They have many trucks and many other, let's say, machines in the operation and sometimes they have to put these machines just through a maintenance mode, to see what's happening, or to change some part specifically, or even if the machine is having some kind of issue. That's due to the fact that if it's down, they have to manage how long it's down and what was the part that was the issue, the cause of the issue. They have to change the parts and everything's very costly in terms of money for the company when we have one specific asset that's down.

Previously, they were using a board in a room, just to manage all these statuses.  Instead of this, now we have one specific app that is working in live modes in almost real-time. Just getting the data from the services and showing it on a big board in PowerApps can show what's happened, what's the status, and what's the reason for the issue. This app allows for adding some comments. It's a collaborative app where many people can just go there and add comments and notes about what's happening with the machine.

We are user integrators and partners with Microsoft. 

We are using Microsoft Power Apps for data collection and processing for small intergroup business applications for our internal needs. 

We use Microsoft PowerApps for very small use cases. For example, conducting internal surveys, or say some of the key business stakeholders want day-to-day reporting. Using PowerApps, we are creating such reports for those executives.

We connected PowerApps to the relational database, which generates the report. 

Also for contract review and approval of these types of use cases. Those are, in my opinion, very simple use cases. There are no complex rules or decision-making processes, which is why PowerApps was designed.

Microsoft Power Automate is primarily used to update some legacy systems for our client, as well as government compliance systems and web-based reporting systems that don't have APIs. Microsoft PowerApps has the same use case. It's the front end and is the part that is interacting with the client and interacting with the collected data.

We use the solution as part of Dynamics 365 Online. Within that, we use Power Apps and we've integrated something on the on-prem database.

The app is located within Dynamics 365 Online. It draws data from an on-prem data source. We use it to perform certain actions in Teams, so we have Dynamics 365 and Teams integration.

We've created an email reader using Power Apps.

This is a low-code solution that I am using for making applications.

We use this solution for workflow automation.

The primary use case for this solution for us is building in-house applications rather than having to purchase them. We build fairly basic applications and we would rather use Power Apps to deploy them or create them in-house.

I am not a PowerApps user, but recently I have been evaluating and scoring no-code to low-code platforms (for developing mobile apps). The score chart is divided into sections, such as usability and features like the ability to test and multi-platform. Due to these evaluations, I learned the systems well enough to be able to build a sample application on all of these platforms and then fill in my evaluation.

We use this solution to provide a cloud-based platform for our clients to develop, connect, and store data from across the full Microsoft suite.

We're using it for our business processes. We have applications for expenditure requests, travel requests, and accident reporting.

I am using the latest version of the solution.

We use the product for sales and customer service features.

I had to upload a form, an invoice, specifically, and then using an Azure function, I had to get that form from the Dataverse database and feed it to an Azure form recognizer and write the data back to the Azure Power App.

We use Microsoft PowerApps for the typical use cases including website creation and a work portal, covering all the operations involving the manufacturing side of my customers.

There are three app-building interfaces available in PowerApps. Canvas is model-driven. Power Pages, which was Power Portal, which has more low-code, no-code capabilities and makes web design easy for the everyday user to create a website. Lastly, Power BI reports, or Microsoft DataWorks, which we have integrated with our data provide us the option to work collaboratively.

My organization deals with the implementation of PowerApps and Salesforce. We are currently scaling up our capacity in low-code, no-code platforms. Essentially, this solution is for building forms from a front-end loan application and quickly rate a particular application.

In the complete Microsoft Power platform, there are four components: PowerApps, Power Automate, Power Virtual Agents, and Power BI. We use all these four so we can make a complete solution, e.g. a visualization dashboard, automated chat bots, and the rest we can achieve using PowerApps.

Microsoft PowerApps has three types of applications. One is the canvas app. Another one is the model-driven app that is business specific and data specific. Another type of app we can use is open source, e.g. open projects that are called "portals". We can achieve the same thing when developing a website and when doing it in the portal. These are what we can achieve using Microsoft PowerApps and the Power Platform.

Microsoft PowerApps provide the user interface and functionality, e.g. we can create a normal app that is used on web or mobile. Microsoft PowerApps is similar to a form where you perform whatever you want to do. Some look and feel controls are also found in this solution.

Power Automate, on the other hand, is where we automate the backend processes, e.g. the notifications, data extractions, etc. For something that needs calculation, we use Power Automate, while building the user interface and user experience, we use Microsoft PowerApps.  

We're not in production yet. We're still very much in the early stages of this solution.

We use it as part of our analytics offering. We are basically into analytics. Maybe sometimes we use it to build small apps to instrument the research process. That's what we do.

I belong to a consulting company that develops applications using PowerApps.

Our primary use case is for the three locations in our company. We use it mainly for setting up meetings in our various conference rooms. Numerous choices need to be made - size of room, number of phones and projectors, date, time, number of participants. It's a great way to keep track of everything. We have 200 users. We're gold partners and I'm a lead consultant in our company. 

I use it for internal purposes and also to advise our customers. 

We are an IT consulting company. We provide IT solutions to other companies.

We have had a few different requirements, one requirement was to create a simple online form that can be used by the clinics. When patients arrive, they will be given a TAB, to complete the form, which will be printed directly to the receptionist, once they complete the form.

Another application was supply chain management. Using PowerApps, we replicated the entire supply chain management. The corporate users will send the requisition to the purchasing department for review and approval, after which it will be distributed to prospective vendors.

Vendors will then submit their quotes for review. Multiple quotes can also be reviewed concurrently. This is all done with PowerApps. After they have reviewed them, they can select a vendor and process the PO.

In the third scenario, we developed a public relations system that you would find here in the UAE.

PROs must manage and obtain visa permissions in the United Arab Emirates. We have documentation with a two-year expiration date. As a result, we've developed a document management system that uses a Power Automated workflow system to view the alert and process the documents for all employees.

These are the workflows that we have worked on recently and have been created using Microsoft PowerApps and Power Automate.

We migrated all the applications to the PowerApps Server and are sending some to other users.

We have a partnership with Microsoft. 

We primarily use the solution to create apps for business users which navigates them from within our platforms.

Our sales reps use it in the field on a daily basis. I get the data from there and then analyze it for my needs. We are also developing an application to start using Microsoft PowerApps. I would assume we have the latest version. 

We use this solution to integrate our apps, and send processed data via the different connectors it provides.

Our primary use case for the solution is collecting business data and checking for initiative ideas to collect information.

The primary use case of this solution is for developing Proof of concepts and for preparing some use cases to present or to showcase them to the customers. Nothing related to production. It's only for presentations and for showing the merchandise to the customers.

The deployment model we are using is cloud-based.

I primarily use the solution for its business application. My business needed an application and so that's what we're using Power Apps for.

We use the Microsoft PowerApps platform to create low-code applications that are used for optimizing internal business processes.

We primarily use the solution to create and arrange a number of requests, including requests for expenses, requests for leave, requests for documents, etc. Depending on the type of business, we can customize the request application.

My primary use case for Microsoft Power Apps are mostly demos for my customers and in trainings. I am a Microsoft Registered Trainer.

We primarily use the solution for in-house management.  For example, for human resources and warehouse management. 

We are into software consulting. We have been developing various solutions and leveraging PowerApps to do it.

I'm a developer and we use the product for in-house development and finding in-house solutions. We have a developer relationship with Microsoft. I'm currently working on a smart parking app for a college here in Kuwait. It would be a big time saver and enable drivers to know where there are available parking spots when it's a busy time and would maximize free space usage. It would make things easier for everyone.

We're working on B2E applications and therefore we can't really get into specific use cases.

Our primary use for Microsoft PowerApps is to develop production-ready applications.

We are customers and resellers. We mainly collaborate with Microsoft and supplemental applications.

PowerApps is mostly a front end. It's a form where users can input information, and it gets goes into a database.

We use the solution for making forms for Office 365.

Once you have a cloud solution, for instance, and you work within a Microsoft suite, such as Dynamics CRM, ERP, or another dynamic platform and you want to extend it with a mobile app, Microsoft PowerApps is the right solution.

Main limits will be the "vendor lock-in" concept, pricing for mass external users, and the training could be better. It is not intend to serve ex-Azur assets or on-prem. 

We use the solution for, production orders, and for statement classification expenses for a family company. 

We use this solution for process authorization in our company.

The primary use case of this solution is to automate the interaction between documents and departments. For example, it's a flow for someone who has to validate a request, a file, or to review another file. A flow is put in place to avoid email communication.

Microsoft has come at the right time. To come out with a RAD (Rapid Application Development) tool where you can develop your apps on the cloud much faster, and deploy them for multiple devices, whether it is mobile, cloud, laptops, or desktops. It is similar to Oracle APEX or Oracle developer tools where you just drag and drop into your application within minutes.

The primary use case of this solution is case management reporting. If, for example, you have a set of engineers who have been assigned a particular case or project they will need to record all of their activities and their visits. Using the application created in PowerApps, they report everything, then it goes through a workflow. 

The workflow goes from recording the daily activities of the team for the specific project. The project then goes through a series of approvals and gets logged, completed, and the report is generated. 

Expenses are also being logged. 

We have Power BI as well, and it moves the data from the source to the data warehouse then generates a report.

This is quite a short term, six-week engagement. We wanted to create an application and have it up and running within four to six weeks, rather than spending three to six months on bigger projects on the platform. We wanted it to be quick and fast.

PowerApps is best suited for those cases where you have a small scenario and an application to support that project or scenario. You can call these departmental applications, which are needed on the fly. We create a much shorter development lifecycle and then deploy, and then people start using it.

Take an example of the COVID-19 situation. We wanted all of our branches to log their COVID cases or what exactly are they doing daily to manage the COVID cases and to know what the process is. All of those details are logged into the COVID folder and then the reports are generated daily or weekly.

We did a POF with Microsoft PowerApps and we used it for simple automation tasks.

It was used to collect or gather information from the requests, assess requests, and evaluate the requests for a new potential project. 

I am a consultant for developers and architects. People to whom I give consultation use it.

It is a cloud solution. Data can be cloud-based or on-premises, but it is mostly cloud-based.

I am using Microsoft PowerApps for small apps for internal company management. I have been working only on small and simple apps. I haven't used it for making complex apps. 

I am using the latest version of Microsoft PowerApps.

We use this product to develop small apps that are used internally. Nothing major.

Our primary use case of this solution is for when we're integrating something and need to extract some data. We use PowerApps to extract the data and create our own module inside PowerApps and create our own app. We extract data and integrate it with PowerApps.

We are currently piloting the solution, we are checking it with our workflow.

We use Microsoft PowerApps to get insight into the business. We use it for BI.