Microsoft Power Apps Reviews

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.

It is easy to use.

Most of my training for what I do has been by watching or learning in the community. There needs to be better training on either one of these. 

We started implementing it in February 2020.

It is stable.

It is scalable. About 150 to 200 people are using it. 

In terms of our plans to increase its usage, I'm moving to a different department and starting over. We might be scaling up in my new department. In the current department, they still need to figure out what they're trying to do.

If I'm dealing with the community, technical support is incredible.

We were paper-based before switching to PowerApps.

It was easy. We started in February, and everything had to be up and running in March because of the pandemic of 2020.

I did it, and there was no reseller. We're a university, and the university was not going to pay for us to have this deployed by an outside partner.

I also take care of its maintenance.

I don't have that information. We work with a procurement office that deploys it for our university.

We looked at ServiceNow because some of the departments in our organization were using ServiceNow.

Deployment has to be supported from the top down because if you're trying to get things supported from the bottom up, you run into a lot of interference. This has not been the easiest.

PowerApps is incredible, so I would give it a nine out of 10.

We use the product for sales and customer service features.

The platform has valuable features for opportunity and finance management. It has all the essential features for customer service.

Sometimes, the opportunity includes two products, and the outcome for each product is different. It would be beneficial to have a feature that allows users to split the opportunity into separate logs for each product.

We have been using Microsoft Power Apps for more than 15 years.

We never encountered system downtime issues.

It is a scalable platform.

We contacted the technical support services in case of functionality unavailability during the trial version phases.

Positive

We used Microsoft 365 Dynamics CRM earlier. Later, we switched to Microsoft Power Apps for faster speed and availability of on-cloud infrastructure.

The initial process is simple. We need to create a trial and start working. It takes half an hour to complete. Later, we can purchase the licenses further.

The product is inexpensive. I rate its pricing a three to four out of ten.

We evaluated ServiceNow. We decided to use Microsoft Power Apps, as we already used the Microsoft platform. It was easier to onboard the product into a trial environment, and premium support was also available.

I rate Microsoft Power Apps a nine out of ten.

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

This solution has allowed us to offer our customers to integrate with our platform platform to send documents, and for them to be processed with a digital key network solution, without having to use the platform directly.

We like that this solution allows us to fully define our test environments, and link them using different code. This means we can do different tests, but with one basic structure, and then export the data and use it in other platforms.

We would like to see the period for viewing executions within this solution to be extended beyond its current limit of 28 days.  We would prefer to be able to offer our customers an infinite amount of history to search.

We have been using this solution for nearly a year.

We have found this to be a generally stable solution, and have only experienced issues when there are a large amount of registers involved.

This is a very scalable solution.

We did not previously have a single solution, but instead we used a component that worked using Java.  We switched to this software because it was less complex to maintain.

The initial set up of this solution is fairly straightforward.

We implemented this solution using our in-house team.

We would advise organizations that this solution has a high-price point. However, the cost is justified for how comprehensive the package is, and all components of the solution are available under the standard license plan; there are no hidden costs involved.

We would rate this solution an eight out of ten.

We use this solution for workflow automation.

Power Automate has been the most valuable feature. 

The set up of the solution could be simpler. 

We have been using this solution for three years. 

I would rate the stability of this solution an eight out of ten. 

The customer support for this solution could be faster. 

Positive

The initial setup is fairly straightforward. I would rate it a seven out of ten. 

The whole life cycle takes two months to develop, test, implement and deploy.

It is possible to make use of free licences for the sake of a POC. 

Overall, I would rate this solution an eight out of ten. 

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

The most valuable feature is the completeness of the concept. It is not restricted by where you are allowed to use it and that is its greatest strength.

There is room for improvement in error handling and debugging. I would appreciate it if Microsoft created something like the social network graphs Facebook sometimes shows you (potential connections). It would be great for Microsoft to take a similar point of view regarding the data and data flow in Power Apps. It would help us see which field is changing and which is influencing the follow-up field or display or workflow, etc.

As a chief financial officer, I would like to see the mark of chain retracement and where the money flows. Imagine dropping a little drop of ink onto a handkerchief and seeing the ink sucked into the fibers of the handkerchief and distributing itself. Similar things happen to money if you put it into a small market and a chief financial officer needs to have that information. 

I have been working with Microsoft Power Apps since 2018. 

Microsoft Power Apps is definitely stable. It is as stable as SharePoint and this app model has been in place since 2013. Essentially, it requires you to put code onto a SharePoint site which is not executed there, but rather on a client or on specific workflow codes, which are client. If code executions are well work-flowed, it is capable of saving your script and of the global resources. That capability to take off where you left off, including external resources, is a great strength.

Microsoft Power Apps is scalable. SharePoint is a farm. It is a big forest of machines interconnected by a messaging system, Windows Azure Service Bus. It can be understood as a telepathic network between the machines. As long as one machine is running, the system's running and as soon as more machines are adding the capabilities, the load is distributed automatically.

Microsoft's technical support is at a high level. 

We did previously use a different Microsoft workflow operating system, but it was complicated to program and difficult to provide interactions with the users. All of that is much easier now that we use SharePoint platforms like Teams. Microsoft has the best of all worlds. I am confident that it will rock the market.

I have an MSD end subscription; it's a flat rate subscription.

My advice for anyone looking to implement Microsoft Power Apps is: please have a closer look at the Azure infrastructure and do not underestimate the complexity of Azure Active Directory and SharePoint. I recommend spending a week or so letting someone informed like me introduce you to the complexity of Azure Active Directory, SharePoint, and Windows Azure. Not having this information is like driving a car without having put oil into the motor and air into the tires. In other words, it would not be wise.

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.

Most of the people in our organization using this solution are business people. They are not experts in technology and are not familiar with how to use the application. They use Excel and other documents to collaborate. Moving Excel to the application helps them access different data sources. It allows us to provide all the information in one single place. Everyone can view the data based on their role or access level.

The most valuable feature of Microsoft PowerApps is the ease of use to create an application. For example, if you use the Canvas app, there is a feature that you can upload an image, and it will easily identify it and convert it into the application.

The solution is convenient for using Power Effects so we can write customized business logic.

Microsoft PowerApps is not responsive in nature. For us to make an application responsive, it requires some effort. We need to work with CSS, HTML5, or JavaScript.

I would also like to see improvements made to the integration with other data sources, including Azure Databricks or Spark. When we connect from DataWorks, CDS, SharePoint, or OneDrive where the actual Excel file is kept, it is easy. However, if we connect with other data sources, we need to do a no-data filter, particularly when there are in-built integrations available. 

Out-of-the-box connectors, like dataflow, would help to load the data from those data sources into CDS.

For future releases, Microsoft PowerApps should add more templates that help bring more experiences to the websites.

I work as an IT analyst. I have been using Microsoft PowerApps for two years.

In our organization, PowerApps is used by program managers, IT engineers, IT analysts, assistant consultants, and delivery partners.

The initial setup of Microsoft PowerApps is straightforward. 

For deployment, we use the ALM CoE kit, and GitHub through the pipeline. It is done through the team, creating a Dev environment for each pre-Dev and production environment. When we have completed testing and validation, we proceed with staging and then production.

We have not implemented using an automatic deployment through Azure Pipeline as there are a lot of bugs. We are still doing the implementation manually.

Deployment is done by our customers' teams. They are handling the pipeline activities.

The ROI is always positive. Our customers who use this solution can quickly create and circulate through a group. For example, for an innovative idea, you can create an idea zone, QC, or something similar. You can create a form and circulate it via email through PowerApps.

PowerApps has been adopted by all major partners and Microsoft is widely used. We use Microsoft Teams to collaborate. You need to have licenses. E1 plus Intune or E1 plus licenses is enough for everyone to use PowerApps as it's free, even if you are using data sources like SharePoint.

If you want to deploy something with RPA or Power Virtual Agents, you will need to think about the licensing model and the capabilities of the AI builder. AI can deploy the AML model, so you can use the capabilities, meaning you need the licensing.

For an organization looking to implement Microsoft PowerApps, they should consider the timeframe required and the experience they would like. 

Responsiveness is a concern with PowerApps. If you want to build an application for your desktop, tablet, or mobile, the application needs to be responsive on all screens. PowerApps is not responsive to these requirements. If responsiveness is not a concern, then I recommend this solution.

I would rate this solution a seven out of ten.

We have a partnership with Microsoft. 

The flows are good and probably the best component of this product because they can be used in a variety of situations and we're using it all the time. We're also using a lot of portal and canvas too. This is a simple solution and user friendly.  

The product has a few issues. The portal and canvas apps are the main things that need to be improved. Bringing the UI of a model-driven app to something closer to what Salesforce has will definitely be a game changer.

I've been using this solution for three years. 

The solution is stable if the load is not too high. If it is, then we have issues and need Microsoft to help us sort things out. In the low to medium load, it's very stable.

Our implementation wasn't huge but the solution is scalable.  

The technical support was good. They provided us with first-rate architects and good support.

Positive

The initial setup was relatively straightforward. 

I recommend this solution because of the type of connectors that they have, the cost is reasonable, and it's easy to learn. 

I rate this solution seven out of 10. 

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 am from the sales side, so I really do not know the technical aspect of it.

It's my understanding that it has been issue-free.

We have pretty easy integration options.

Technical support is great.

The solution is stable and reliable.

The scalability is good. 

I don't have any notes for improvement. It does what it says it does. 

We'd like to see more integration capabilities in the future. 

We've been using the solution for about three years. 

The solution works well. It's stable. the performance is good. there aren't bugs or glitches and it doesn't crash or freeze. 

We use it for a very specific purpose, and therefore scalability is not really a factor for us.

We have about ten clients using the solution currently.

Technical support has been fine. We are satisfied with their level of service. 

We use the cloud version of the solution. There isn't an in-depth deployment process. 

We handle the projects and the implementation for our clients. 

I don't have any comments on the cost or licensing. It's fine. It's cheap compared to other RPA tools. It was about $40. There are people that are lower than that, however, they don't give you the features.

We use a lot of Microsoft products. We use Microsoft Power BI, Power Platform, and Azure Patch Solutions.

I'm not sure which version of the solution we're using. 

I'd recommend the solution to others. 

I would rate the solution eight out of ten.