Microsoft Power Apps Reviews

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

What I like about it is that it is coming from Microsoft. It is very easy for us, our techno-functional consultants to spin an application in days, not in months. 

This is easily integrated with native systems including the Microsoft stack. If we have to integrate with other products such as SharePoint, we can leverage any services using Azure or the same platform.

In terms of scalability, it can scale quite well. It's so scalable with forthcoming technologies. We can develop something in PowerApps, and that can easily be scaled to a bot. We can quickly make a bot there and make it work in conjunction with applications.

We had it integrated earlier with voice channels. You can manage an omnichannel kind of scenario between Voice, Teams, WhatsApp, social integration platforms like Twitter, Facebook, et cetera. 

The RPA is very closely integrated onto the same platform and BI as well. It's great.

The initial setup is very easy.

The product is very stable. 

I have found the technical support to be helpful.

When we talk of integrating with external applications, that's one area where, even today, I had to loop in my code developers. If this area can be streamlined so that my techno-functional consultants, who are on-site, can immediately start working on something without the assistance of developers, that would be ideal.

I've used the solution for four and a half or five years. 

The stability has been great. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

It's so scalable. We can scale to all the latest technologies and we can integrate with the social platforms. We can integrate with the document management system (SharePoint). We can integrate with the Active Directory exchange server. It's limitless.

It is so much more scalable once you have everything available over in the Dataverse so that you can write triggers and automate a lot of the BPM. Once you have everything with you, you can spin any dashboards, reports, schedules, and then those can go through mail alerts. You can schedule alerts through WhatsApp messages. You can schedule it through voice IVRs. You name a thing, or you can schedule it. You build it over here and then schedule it over there. 

My experience with technical support has been very, very hood. They've been very supportive. The only thing is that you have to have the right support plan. If you have one, they adhere to the SLA quite well.

The initial setup is not overly complex or difficult. It's pretty simple and straightforward. 

I have done the initial setup multiple times for the various installations. I can handle it on my own and do not need outside assistance. 

The pricing is a subjective thing. Whenever we are positioning PowerApps to an enterprise that is already into Dynamics 365 ER PCRMs, it is very easy to position it as they have already made initial investments there. It is just simply that the number of users that are based on the number of applications and it can be scaled. For them, I've never faced any issues. For example, for a hospital with it, we were already reaching out to, say, 40 units. When they wanted to scale to their smaller units, the 70 of them, it was a cakewalk. Then we had a plan to extend it to their pharmacies, say, 50 of them. That, again, was a cakewalk as they were already on that platform.

However, when I go and reach out to a smaller business SMB segment, the challenge over there is that we are faced with competition - with other software which has been built on PHP. If we host it on-prem, of course, then that discussion of cloud versus on-prem and those fundamental discussions creep in and then there is the minimum unit price per license, meaning per user or per app. When you look at it that way, an SMB will see it as expensive compared with open-source options.

I'd rate the solution at a nine out of ten. If the external integration process was easier, I would give it a perfect ten. 

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

The initial setup should be improved. It could be easier.

Technical support could be faster, and more accurate.

I have been working with Microsoft PowerApps for the last year. My experience is limited but I do use it from time to time.

Most of the time, Microsoft PowerApps is stable.

I have no issues with the scalability of Microsoft PowerApps. For our purposes, it is quite scalable.

At this time, I don't have any issues with technical support. It can however take some time if you launch a service request, but most of the time, it is resolved within the expected time.

We also work with Microsoft 365.

The initial setup is moderately complex.

Microsoft PowerApps is expensive, but there are many features included.

They think about how they will set it up before beginning to ensure they select suitable use cases.

I would rate Microsoft PowerApps a seven out of ten.

The usability, in terms of low-code applications, is a feature we have found most valuable. We just do development and then distribution.

Improvements to the capturing of geographic locations and integration with maps would raise my score of the product from seven point five to its maximum of ten.

We have been using Microsoft PowerApps for around two years.

So far, the product has shown stability.

The product is scalable.

I am making use of the product in my own company.

I would rate it an eight out of ten. 

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.

It's very easy to build an app using this solution. It's easier than with other tools. 

I think installation and integration could be improved. It's tricky compared to other tools. 

I've been using this solution for a month or so.

We are a small company and only have four or five people using this solution. 

When it comes to installation, we need to install a gateway and integrate between two tools, for example, PowerApps and Power Virtual Agents, Deployment is a little complicated. The data is available in Google but it's a little difficult.

Licensing is on a monthly basis. 

We tried a lot of other products before choosing PowerApps and we found Microsoft to be easier to use. 

I would recommend this solution. Microsoft is a large company and the product has good features. We plan to migrate all our tools to Microsoft in the future. 

I rate this solution an eight out of 10. 

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've been pleased with it. I would say that it has improved the way our organization functions. It makes app-building faster and easier.

The solution is excellent at figuring how to build an application in three months. It makes it very quick and easy.

The pricing is very reasonable. it's not overly expensive.

I can't recall any missing features. Currently, the solution is doing a good job of meeting my needs.

My target is to have an application that I can use for clients. I don't see Power Apps as being the long-term solution. They get expensive when you start to go to non-internal users. If there were to be external users, the solution would get expensive.

The documentation isn't great. It's only 75% of what you need to know. If you go beyond that and run into issues, it's really not going to help you.

For example, the software is almost guilty of being too powerful. The particular problem I had was that they recommended that I use Azure to do the login, to do the user authentication. Therefore, I set it up. However, it didn't work. I could not find the solution via documentation or online at all. Without knowing I could access technical support, I paid someone a couple of hundred dollars to try and figure it out for me and they couldn't figure it out. Eventually, I was just looking around and I came across one setting hidden away and it was set to false. I instinctively realized that it looked like it might be related and so I set it to true and all of a sudden everything worked. However, that whole issue could have been mitigated if the documentation just took that extra step and got into the nuances of the product.

What I'd love to see them do is to sit down and clean up the interfaces. There are three different ways that you can program. I'm particular to using a Power Apps portal. There are three different ways I can edit my Power Apps portal website. Each of them kind of does a better job of doing some things than the other ones do. Therefore you're kind of in this in-between realm of having to choose between certain things if you decide to go with a specific approach. They really need to clean up the development environment so that t's straightforward and predictable across the different ways to program. 

It does things, such as, if you want to delete a particular field or table, you get this message that says you can't due to the fact that it has dependencies. It's really hard to find what those dependencies are. Items like that need to be clarified. 

The application is working great now, however, every once in a while it gets complicated and it's hard to navigate.

I've recently delved into using the product. I've been using the solution for at least the last seven or eight months or so. It's been less than a year. I haven't used it that long just yet.

The solution is very stable. There are no bugs or glitches. It doesn't crash or freeze. its performance is reliable.

The scalability is limited if you want to scale externally. A company needs to keep that in mind.

I only launched my first application sometime around Christmas, or just after. It's still quite new. I have about a dozen or so people that move in and out of it. It's just a small app.

As a company, we are quite small. All of our users would be external. And, due to the fact that the solution gets expensive for external users, it's not a solution we plan to expand upon or use for the long term. 

The technical support is not easy to find. It's a bit of a well-kept secret. However, once you locate them, they are quite helpful and responsive. 

Truthfully, they are hard to find due to the fact that you just don't realize they're there. I had spent a month, six weeks phoning around trying to find internet solutions to problems and resources and paying people to help me, and nobody knew the answer. 

This was done without ever realizing that there was a very capable tech support resource available in Power Apps through the subscription. Once we found them, they were able to fix all of the issues we were struggling with very quickly.

The initial setup is quite straightforward. A company shouldn't have any issues with the setup process. It's not overly complex. 

The pricing is excellent. It's not too expensive.

However, once you get into adding non-internal users, the solution can get pricey. It's only reasonable if you are trying to create internal team-based apps.

I haven't looked at any other low-code development platform.

We're just customers and end-users.

We are using the latest version of the solution.

From a perspective of me doing a full test of the application and how I want it to run, it just met all of my needs and there are other storage locations for data. That said, the data is sitting in the CDS.

From my perspective, it was a great place to start and a great place to sit and test the waters. I'm looking to migrate it into something else in a little while. I won't stay with it forever. That's not the plan.

I'd rate the solution at a seven out of ten.

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

I like the containerization of Azure. We are trying other architectural options that they offer.

There is always room for improvement and with PowerApps, there is a long way to go. 

The flexibility and the user interface need improvement. 

The speed, as in how fast things can be done, needs to be improved.

The workflow needs improvement and should be included in the platform.

We have been working with Microsoft Azure for the past year.

The support is good.

Here in Greece, we have enough support for Microsoft. There are some government-level agreements and county-level agreements. 

It is easy to deploy, although we have some experience.

It seems pretty straightforward.

You have to be careful with pricing.

It might be too complicated to continuously monitor the business consumption and what to pay.

It's not something you can easily rate, as you have to rate according to specifications and characteristics.

It is a good product but I would like to see the flexibility issues improved, and there are issues with the user interface. You have to use the interface in a specific way.

I would rate this solution a seven out of ten.

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.

The model that allows you to establish flow automation is getting a lot of traction from the customer side. It offers a lot of flexibility.

The availability of templates needs to be improved. I understand that the ecosystem around it is still developing, but we need more templates. I would like the entire ecosystem around it to improve.

I would recommend adding AI components. Even though we can always connect to Azure for AI components, they should slowly start looking at adding some AI components to PowerApps so that out-of-the-box learning can be applied to process flows. Salesforce has the Einstein layer that works along with license platforms. PowerApps should also have something similar.

We have been using PowerApps for the last six months in our organization.

I haven't come across any issues. I have not faced any issues with my existing deployment.

It is quite straightforward.

We have our own team for the maintenance side.

One of the main things about this solution is the price. The cost for Salesforce is $35, $25, or $10 per user per month. PowerApps costs much less than that. It is at a good price point. It may change in the future, but at this point, its price is pretty fine.

I would recommend this solution for people who are looking for flexibility. PowerApps offers more flexibility than SalesForce. I would advise others to use a local platform to build and test first and fail fast. 

We are still exploring a few features, but based on what I have learned and seen, I would rate PowerApps an eight out of ten.

The most valuable feature is the compatibility with other Microsoft components, the connectivity to Microsoft databases, the connectivity to other components on the Microsoft Azure environment, the connectivity to Office 365 and the connectivity to teams and the overall environment.

Microsoft should combine both the web and the mobile environment with all of the layers of development into one package. Currently, it's separated because Microsoft Power Apps does not cover all of these issues, so you have to connect to two different solutions. With Mendix for example, with one environment, the developers can create either a mobile app or a web app — it's an all-in-one environment. Microsoft Power Apps is not a service. For instance, if you want to connect to a database, it will be done via a database platform. 

Microsoft PowerApps is both scalable and stable. 

Microsoft PowerApps has a good support community.

The initial setup is no more complicated than similar solutions. I'd say it's pretty straightforward. 

Overall, on a scale from one to ten, I would give this solution a rating of eight.